Public bug reported:
Some single letters in Firefox are scattered. (one - two letters on screen)
When taking a printscreen letters refresh and becomes normal.
Also when selecting text letters becomes normal
also when scrolling contents out of look and scrolling it back - letters become
normal
Sc
Public bug reported:
sometimes after startup and always after suspend polish diactric letters stops
working.
When using standard combination [RIGHT-ALT] + [letterkey] instead polish
letter some menus in program are displayed.
Switching keyboard settings to "Angielski (USA)" and back to "Polski
Public bug reported:
Ok I've reported this bug before but without uploading info.
System has been freezing randomly for a year now or more. Since I first
upgraded from 11.10 to 12.04.
Random freezes, sometimes with lockedup screen,keyboard and mouse snd sometimes
just screen and keyboard. I ca
Which driver did you get working in the end? My experience was having 3
monitors work fine in raring 13.04, until the driver that is in Saucy
13.10 at which point it started pulling the "only two monitors at a
time" stunt. Bug 1242180
--
You received this bug notification because you are a memb
*** This bug is a duplicate of bug 1098334 ***
https://bugs.launchpad.net/bugs/1098334
** This bug has been marked a duplicate of bug 1098334
[gen4 sna] Font corruption in Chromium tab bar
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x
xrandr output running command line from comment 2. Raring:
crtc 0:1920x1200 60.0 +1920+0 "DP2"
crtc 1:1920x1080 60.0 +3840+0 "HDMI1"
crtc 2:1920x1080 60.0 +0+0 "HDMI3"
Saucy livecd:
xrandr: Configure crtc 2 failed
crtc 0:1920x1080 60.0 +3840+0 "HDMI1"
crtc 1:1920x108
Update: bug also present after upgrade to Saucy.
** Tags added: saucy
--
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/1183882
Title:
Resolution changes automatically when switching TV fro
Public bug reported:
System graphics are too slow. Alt+Tab takes a lot of time (seconds).
Laptop heats up a lot.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
.tmp.unity.support.t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fglrx-installer (Ubuntu)
Status: New => Confirmed
--
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/b
Exact same bahaviour here. Don't know if it helps (or is another bug) that
connecting to a DSL network crashes the network-manager as well, sometimes with
lightdm.
If it seems to be another bug, please ignore my comment.
--
You received this bug notification because you are a member of Ubuntu-X
Public bug reported:
I have seen this issue before as it was in the 13.10 betas. When I try
any setting and method to change the brigtness it fails and remains at
100%. PLease feel free to contact me to get more information
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu6
I believe this issue exists with my Ativ Book 9 lite. The 13.10 usb boot
starts with blank screen. But 13.04 boots and installes perfectly.
I believe the issue is with kabini graphics.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubu
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Here is the Xorg log file for the erroneous behavior
** Attachment added: "Xorg.0.log_nvidia-error"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1244498/+attachment/3891168/+files/Xorg.0.log_nvidia-error
--
You received this bug notification because you are a membe
Here is the Xorg log file for the normal behavior
** Attachment added: "Xorg.0.log_intel-ok"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1244498/+attachment/3891167/+files/Xorg.0.log_intel-ok
--
You received this bug notification because you are a member of Ubunt
As another datapoint, I get the same problem on Debian Unstable, running
a vanilla Linux kernel 3.11, xorg wacom driver version 0.22.99.1-1+b1
(if that matters at all...)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu
Re #19:
I'm using kernel 3.11.0-8-generic and the Intel Xorg driver
2:2.99.903+git20131001.c724098f-0ubuntu0sarvatt2
I installed saucy alpha a few months ago, and then the xorg-edgers PPA.
That works fine, though I haven't updated it in about4 weeks. The trick
for me was to use one DVI/VGA adapt
FYI, this is an easy way you can test the latest Xorg nightlies:
http://www.ubuntuupdates.org/ppa/xorg-edgers
--
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/1242180
Title:
s
It's falling back to generic VESA driver:
(EE) open /dev/dri/card0: No such file or directory
--
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/1244617
Title:
Graphics too slow after upgrading to
@RichardNeill - already did all that as mentioned in comment 4 which
also has the advantage of working on the livecd.
--
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/1242180
Ti
*** This bug is a duplicate of bug 1098334 ***
https://bugs.launchpad.net/bugs/1098334
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
I've installed Ubuntu 12.04 on a very old computer that has a
touchscreen (it's not a notebook, it's an almost-square one-block heavy-
as-shit computer with a built-in touchscreen and no keyboard). The
touchscreen is not working or enabled by default. It should, as it
should o
Public bug reported:
Brightness settings reset after reboot - Mac air 2011.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
Then I followed the guide from the wiki at
https://wiki.ubuntu.com/Touchscreen
(a shame in the first place that you have to do all that manually, even if it
worked) and all I got is a machine that won't boot any more. It shows a black
screen with this error:
could not write bytes: broken pipe
I have played around with this issue some more. For as far as I can
determine the problem only appears to affect RDP sessions; VNC sessions
do not seem to have the problem.
FWIW...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
this issue seems still to be present in ubuntu 13.10 xfce...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/615892
Title:
Madcatz Cyborg R.A.T. 7 focus issues
To manage noti
Public bug reported:
appeared right after updating my xubuntu
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: nvidia-304
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2
Architectur
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1244817
Title:
nvidia-304 304.88-0ubuntu1: nvidia-304 kernel module failed to build
T
Ok - the problem seems to be related to the fact that I had two monitors
set up - split over two graphics cards (the onboard and a second card).
As soon as I disabled one of the two monitors the effect disappeared.
I've installed a different graphics card that allows me to run both
monitors from
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
[Expired for nvidia-graphics-drivers (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-d
Public bug reported:
After upgrading to 13.10 from 13.04, I started having a problem where
after restart or on log out/log in the resolution of one my monitors
always changes. I have a CRT monitor running 1600x1200@75 and a LCD
monitor running 1600x1200@60. On restart, the CRT monitor resolution
c
32 matches
Mail list logo