This bug was fixed in the package xserver-xorg-video-cirrus -
1:1.5.1-0ubuntu2
---
xserver-xorg-video-cirrus (1:1.5.1-0ubuntu2) quantal; urgency=low
* Add fix-fallback.diff from upstream git, if a kernel driver is found
don't try to claim the pci device. (LP: #1039648)
-- Timo
Same problem on nforce2 motherboard, AGP Radeon HD 4650.
My config:
- Graphics: Radeon HD 4650 AGP
- CPU: AMD Athlon 2400+ (2.0 GHz, 32 bits)
- Chipset: nForce 2
- RAM: 1 GB DDR-SDRAM
- Version kernel-3.2.0-29
- Ubuntu version: XUbuntu 12.04 (32 bits)
--
You received this bug notification
Seems with the introduction of LLVMpipe support in Ubuntu 12.10, this
bug is now happening to a lot more people than it was in 12.04.
--
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/927168
Title:
Same bug in archlinux :
https://bugs.archlinux.org/task/31034?string=openclproject=1type%5B0%5D=sev%5B0%5D=pri%5B0%5D=due%5B0%5D=reported%5B0%5D=cat%5B0%5D=status%5B0%5D=openpercent%5B0%5D=opened=dev=closed=duedatefrom=duedateto=changedfrom=changedto=openedfrom=openedto=closedfrom=closedto=
--
The SIGSEGV is being tracked in bug #1039916 Nvidia driver causing
SIGSEGV in nvclock and smartdimmer.
That bug affects the Fix released status of this bug since this work-
around no longer functions. I've nominated this bug for Precise and
Quantal, but any fix of the SIGSEGV issue will be done
Public bug reported:
since one version before xserver-xorg-video-intel -
2:2.20.4+git20120821.4ee2e227-0ubuntu0sarvatt I obtain glitches in the
kde panel having blur effect enabled during scrolling through a website
in firefox.
I am using Kubuntu Quantal with xorg-edgers ppa enabled. After a
Has anyone any hints on this? It is really obnoxious.
I *think* it happens when using nautilus, but I cannot be sure.
Some hints on how to debug?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
You have been subscribed to a public bug:
Build : quantal alternate amd64 | i386 20120822
Link to the test:
https://jenkins.qa.ubuntu.com/view/Quantal/view/ISO%20Testing%20Dashboard/job/quantal-alternate-amd64_default/
https://jenkins.qa.ubuntu.com/view/Quantal/view/ISO%20Testing
Not an installer bug. xserver-xorg-video-modesettings needs to be moved
to main; I don't know whether it needs an MIR since I haven't been
keeping track of that.
** Package changed: debian-installer (Ubuntu) = xorg (Ubuntu)
--
You received this bug notification because you are a member of
Moved to main (see #ubuntu-release).
** Changed in: xorg (Ubuntu)
Status: New = Fix Released
--
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/1039970
Title:
failed to install quantal
I can't figure out how to run openbve using the deb packages. I see a
screen with empty lists for choosing a route and train add-on, and a
grayed-out start button.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
Can't reproduce on my G45 system. Can you try again with a current
stack?
(Also, does just opening mean no farther than the first menu screen?)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Changed in: xserver-xorg-video-intel
Status: Confirmed = Incomplete
--
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/982010
Title:
[gm45] GPU lockup render.IPEHR:
The correct DPI is needed for legibility when the same user uses the
same font size settings on multiple monitors. When the user sets the
base font size to be legible in on 1 monitor and then goes to another
which has a higher (true) DPI he will get poorly legible fonts.
The correct DPI is needed
Please use the correct dpi by default.
--
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/521877
Title:
[gm45] wrong screen size detected on X200s
To manage notifications about
Is this bug fixed in a newer release? A fix would be using the original
behaviour or providing an option to revert to the original behaviour.
I got a new monitor with 109 DPI yesterday and started to struggle with
too small font sizes. I was not aware of this bug because my old monitor
had
(In reply to comment #55)
Please use the correct dpi by default.
If it doesn't, it's usually:
1-your distro's fault, or
2-your hardware's fault, or
3-your use of unequal DPI multiple displays, which is a complicated problem for
X to deal with
X automagic configuration will fall back to 96 if
(In reply to comment #56)
(In reply to comment #55)
Please use the correct dpi by default.
If it doesn't, it's usually:
1-your distro's fault, or
2-your hardware's fault, or
3-your use of unequal DPI multiple displays, which is a complicated problem
for
X to deal with
X automagic
Created attachment 43316
Xorg.0.log from server 1.9.3 using 86x86 DPI on i845G
(In reply to comment #57)
Isn't this bug precisely about X.org *always ignoring* the hardware DPI value
from the EDID?
There may have been a time when that was the case, but this was filed by
an Intel video user
(In reply to comment #58)
There may have been a time when that was the case, but this was filed by an
Intel video user long before KMS was required by the Intel driver. Obviously
from the attachment, using no xorg.conf, xrandr, xorg.conf.d/ or anything else
to force DPI, always is not the
Created attachment 43320
86 DPI screenshot
What do I win? :-)
--
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/521877
Title:
[gm45] wrong screen size detected on X200s
To
(In reply to comment #60)
Created an attachment (id=43320) [details]
86 DPI screenshot
What do I win? :-)
AFAIK this issue affects RandR 1.2 capable drivers only, and unless I'm
mistaken MGA is not such a driver.
--
You received this bug notification because you are a member of Ubuntu-X,
(In reply to comment #60)
Created an attachment (id=43320) [details]
86 DPI screenshot
What do I win? :-)
You posted a log with intel, but your screenshot says mga...
Regards,
Andrei
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The bug is marked general, not Intel. Various comments spoke of at least
one other chip prior to my MGA comment 58. Before your comment 58
reached my eyes, I had to put that Intel host aside to work on the MGA
host, so I used that to demonstrate what I wrote in comment 58, that
always is
(In reply to comment #63)
The bug is marked general, not Intel. Various comments spoke of at least one
other chip prior to my MGA comment 58. Before your comment 58 reached my eyes,
I had to put that Intel host aside to work on the MGA host, so I used that to
demonstrate what I wrote in
Guess this is an invite to leave for Wayland or whatever. My current
screen is 96 dpi (give or take a pixel) so I could care less but the
moment I switch to a display with different resolution I will have to
put up with this Xorg's insanity as well.
If Xorg is going to be bug-compatible with
Okay, I meant to post this a while ago and forgot, but the recent churn has
reminded me to do so. I'll start with the tl;dr:
I don't think this bug matters anymore.
It's been over a year since this bug was opened, and during that time I've
come to the conclusion that one should simply *always*
Let me disagree: I keep using my laptop either on a 17 monitor, or on a
21 monitor, or on the internal LVDS.
In both 17 and 21 monitor cases, I do want 100% zoom to really mean
100% zoom, so I need correct DPI.
Your reasoning leads to having to modify xorg.conf each time I switch,
which means
--- Comment #67 from Samuel Thibault samuel.thiba...@ens-lyon.org
2011-02-13 14:27:50 PST ---
In both 17 and 21 monitor cases, I do want 100% zoom to really mean 100%
zoom, so I need correct DPI.
No, you need whatever app you're using to get the info about screen size
from somewhere it has
(In reply to comment #67)
Let me disagree: I keep using my laptop either on a 17 monitor, or on a 21
monitor, or on the internal LVDS.
In both 17 and 21 monitor cases, I do want 100% zoom to really mean 100%
zoom, so I need correct DPI.
I don't understand what you mean by 100% zoom, but I
Why should it have to care about screen size? 100% zoom is supposed to
be app DPI matches screen DPI, it has nothing to do with the whole
screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
(In reply to comment #66)
Okay, I meant to post this a while ago and forgot, but the recent churn has
reminded me to do so. I'll start with the tl;dr:
I don't think this bug matters anymore.
It's been over a year since this bug was opened, and during that time I've
come to the conclusion
(In reply to comment #50)
We need an xorg.conf flag -- for example, NVIDIA has UseEDIDDpi.
Definitely. Is it that hard to implement?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
(In reply to comment #72)
(In reply to comment #50)
We need an xorg.conf flag -- for example, NVIDIA has UseEDIDDpi.
Definitely. Is it that hard to implement?
No. A patch was attached to this report a year ago.
--
You received this bug notification because you are a member of Ubuntu-X,
Created attachment 45751
120 DPI full 1600x1200 desktop screenshot
This demonstrates the current state of elevated actual DTE DPI affairs,
as of the release of openSUSE 11.4 about 5 weeks ago. Video chip is
rv380. Driver is radeon. 120 DPI is achieved exclusively via DisplaySize
in xorg.conf.
Created attachment 45875
setting DisplaySize
--
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/521877
Title:
[gm45] wrong screen size detected on X200s
To manage notifications
(In reply to comment #74)
Created an attachment (id=45751) [details]
120 DPI full 1600x1200 desktop screenshot
This demonstrates the current state of elevated actual DTE DPI affairs, as of
the release of openSUSE 11.4 about 5 weeks ago. Video chip is rv380. Driver is
radeon. 120 DPI is
Retitling this bug, since it affects current X servers as well, though
possibly only randr-1.2-capable drivers as mentioned in comment 63 and
the immediately preceding comments.
This needs fixing. Each time I set up a new system, I end up with
incredibly tiny fonts, and I end up having to
(In reply to comment #77)
(Chrome already does so, in a misguided attempt to force a constant ratio
between px and pt across all websites.
Chrome does because it's built on WebKit, where 96 as the only
possibility is the traditional Macintosh way, which became also the
Internet Explorer
Take it from a typographer
http://www.alistapart.com/articles/realfontsontheweb
We have a world of display devices that have standardized to report their
exact resolution, the space it occupies, and thus the pixels per inch, a key to
moving text typography forward.
Who wants to break the news to
(In reply to comment #27)
On Tue, Feb 16, 2010 at 10:58:07PM -0800, bugzilla-dae...@freedesktop.org
wrote:
--- Comment #26 from Andrey Rahmatullin w...@altlinux.org 2010-02-16
22:58:04 PST ---
(In reply to comment #20)
It was chosen in order to make display of web pages using Xorg
Please add an option (command-line or config file) to make the X server
stop lying about the physical DPI of the display device. I understand
all the arguments for pegging DPI at 96, but *I* still want my X server
to report the actual DPI as read from the EDID.
Maybe add an -autodpi command-line
I'm seeing this bug too with nouveau driver. I've set DisplaySize to 474
296.
At first it looks okay:
[ 45437.510] (**) NOUVEAU(0): Display dimensions: (474, 296) mm
[ 45437.510] (**) NOUVEAU(0): DPI set to (90, 90)
and sets it to 96 dpi...
[ 45437.530] (II) NOUVEAU(0): Setting screen physical
Created attachment 51062
X log from 1.11.0
--
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/521877
Title:
[gm45] wrong screen size detected on X200s
To manage notifications
I'm seeing this bug too with the nouveau driver:
[ 745.858] (**) NOUVEAU(0): Display dimensions: (330, 210) mm
[ 745.858] (**) NOUVEAU(0): DPI set to (129, 127)
...
[ 745.892] (II) NOUVEAU(0): Setting screen physical size to 444 x 277
I noticed this after switching from the proprietary
Was it really fixed??? I can't find any related fixed in git's master.
--
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/521877
Title:
[gm45] wrong screen size detected on
PLEASE stop reopening or discussing this in here. This is not a proper
place for such discussion - this is not a forum or mailing list but bug
reporting software and xorg developers concluded this is NOT A BUG.
If you really want some changes in DPI area then please discuss it
through proper
I've created feature request to add patch from comment 17:
https://bugs.freedesktop.org/show_bug.cgi?id=41115
--
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/521877
Title:
However you look at it this is a bug.
Xorg changed from working to bogus and broken behaviour.
--
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/521877
Title:
[gm45] wrong
(In reply to comment #20)
It was chosen in order to make display of web pages using Xorg more consistent
with the way they get displayed on Windows, which by default assumes 96.
It's called bug compatibility, and there's a knob in a browser for that already.
--
1400x1050@122,
sorry, still can't reproduce this and I can't see any change between 902
and 1.6.2 that could have introduced this bug. Are you still on server
1.12.1.902 or have you updated the server as well?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I have upgraded xorg server quite a while ago and it had not resolved
the issue at that time. Just for the completness:
/var/log/dpkg.log.1:2012-07-03 09:53:04 status installed xserver-xorg:amd64
1:7.6+13
/var/log/dpkg.log.1:2012-07-03 09:53:04 status installed xorg:amd64 1:7.6+13
PLEASE stop reopening or discussing this in here. This is not a proper place
for such discussion - this is not a forum or mailing list but bug reporting
software and xorg developers concluded this is NOT A BUG.
If you really want some changes in DPI area then please discuss it through
proper
*** Bug 53686 has been marked as a duplicate of this bug. ***
--
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/956071
Title:
Xorg crashed with SIGSEGV in
This patch breaks the keyboard layout switcher from KDE3 and Trinity. It
works correctly with the layout switcher in KDE4. Have other people
tested this patch with other layout switchers? What are the results?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Bug watch added: Mozilla Bugzilla #537890
https://bugzilla.mozilla.org/show_bug.cgi?id=537890
** Bug watch added: freedesktop.org Bugzilla #41115
https://bugs.freedesktop.org/show_bug.cgi?id=41115
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Created attachment 63378
xorg-server-1.12.2-xkb-switch-on-release.patch
Some code style modifications.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/36812
Title:
Keyboard layout change on
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=51983.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Well I see a bunch of people have this problem as well, I run KDE (with
effects) and it logs me out from time to time. Mainly just running Opera
and irssi. Suspect it must be some flash via Opera than which cause the
logoff.
Running Kubuntu 12.04, nVidia 295.40, and KDE 4.9
I had 240GTS card
I also can see some random text rendering issues in firefox when marking
text passages with the mouse or writing in formular fields.
And here you can see the flickering: http://www.file-
upload.net/download-4701050/panel-flickering.ogg.ogv.html
--
You received this bug notification because you
Fix is committed in upstream kernel and in nouveau ddx for all cards including
kepler.
However, due to the drastic changes in upstream kernel it wouldn't be possible
to backport to 3.5, unless it's decided to use a backported version of 3.7 drm
there. It's not a typo, the changes are too big
*** This bug is a duplicate of bug 1033533 ***
https://bugs.launchpad.net/bugs/1033533
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1033533, so is being marked as such.
I'm attaching the kern.log when running the 3.5.0-11 kernel.
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1039125/+attachment/3271727/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
*** This bug is a duplicate of bug 1030165 ***
https://bugs.launchpad.net/bugs/1030165
It seems to fail to load nouveau correctly..
[ 9.772] (EE) [drm] failed to open device
[16.622] (EE) [drm] failed to open device
I would say you have had the nvidia module loaded previously and
There has been a new version of libxrandr 1.4.0 for some time now, is
still still an issue or can the bug be closed?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxrandr in Ubuntu.
https://bugs.launchpad.net/bugs/1012149
Title:
package
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
Committed as
http://cgit.freedesktop.org/xorg/xserver/commit/?id=863d528a9f76d0e8f122aebf19f8564a4c67a938
--
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/416421
Title:
[gm45]
Can you start the Xorg server with -verbose 10, then plug in the device
and paste the log?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/1033783
Title:
Wacom stylus and touch not
I applied Mr. Bagwell's patch to Fedora 17 after receiving some guidance
from Mr. Weir. I thank all who have posted for their contribution in
resolving this long term regression.
My specific steps were...
1. Obtain the source: yumdownloader --source xorg-x11-server-
common.i686
2. Extract
I applied Mr. Bagwell's patch to Fedora 17 after receiving some guidance
from Mr. Weir. I thank all who have posted for their contribution in
resolving this long term regression.
My specific steps were...
1. Obtain the source: yumdownloader --source xorg-x11-server-
common.i686
2. Extract
May the so called developers with I know better attitude be treated by
physicists with the same attitude!
They broke the thing for BUG compatibility with an obsolete piece of
crap for a single use case already handled in corresponding application
(a web browser), they told us to go sink in the
** Changed in: xserver-xorg-video-intel
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/bugs/416421
Title:
[gm45] X crash on X200s with
Both xorg logs show traces of nvidia, so I can't say for sure what's
going on, other than that those logs are useless and you want to make
sure all traces of nvidia are removed before you create a Xorg log :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is
It's the built in device (embedded in the screen). Is there something
equivalent I can do?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/1033783
Title:
Wacom stylus and touch not
Approving based on doko's the package itself looks ok for main
comment.
** Changed in: xserver-xorg-video-dummy (Ubuntu)
Status: New = Fix Committed
** Changed in: xserver-xorg-video-dummy (Ubuntu)
Assignee: Matthias Klose (doko) = (unassigned)
--
You received this bug notification
xserver-xorg-video-dummy promoted (needed by xorg-gtest)
** Changed in: xserver-xorg-video-dummy (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: xserver-xorg-video-dummy (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a
That's odd, the only thing I changed is a configuration file
/lib/udev/keymaps/module-lenovo . If you want, you can install the old
udev and just modify that file and you _should_ have it working. What
distro/version are you using? I can help out by debugging on the same
platform.
Here's the
Here's some output from my dmesg regarding Xorg as well; not sure if
that helps at all...
[3.576578] Pid: 1127, comm: Xorg Tainted: P O 3.5.0-11-generic
#11-Ubuntu
[3.576579] Call Trace:
[3.576583] [81051c4f] warn_slowpath_common+0x7f/0xc0
[3.576585]
Here's some output from my dmesg regarding Xorg as well; not sure if
that helps at all...
[3.576578] Pid: 1127, comm: Xorg Tainted: P O 3.5.0-11-generic
#11-Ubuntu
[3.576579] Call Trace:
[3.576583] [81051c4f] warn_slowpath_common+0x7f/0xc0
[3.576585]
Is this still an issue on 3.6-rc kernels?
--
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/745112
Title:
[arrandale] desktop is messed up with external monitors (x86_64)
To
I can also confirm that downgrading to xserver-xorg-input-
synaptics=1.5.99.902 appears to have solved the problem.
--
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/956071
I'm available to assist with any debugging or testing for this issue. I
have different hardware, but it is my understanding that I am running
into the same issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
As a *workaround*, you can enable the nouveau driver in
/etc/X11/xorg:
Unless you happen to own a GTX 560/GF114 card like some of us, as there
is a curent Nouveau bug that causes it to throw PFIFO - playist update
failed, and failed to idle channel... messages while repeatedly
restarting
Hi Timo,
so I've purged the ppa and connected the intuos 5 after a restart...
same behavior as before - The tablet works, but still the nasty bug with
the left buttons on the tablet...how can I help to supply information
about this issue? We have to be a bit quick because it could be a
hardware
Public bug reported:
Hi,
The nvidia binary graphics drivers shipped with Ubuntu 12.04 LTS do no
support XRandR 1.2/1.3. Consequently it is not possible to create or use
display colour management profiles using the colour tool, as this tool
relies on XRandR 1.2.
nvidia released an updated
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
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/1040206
Title:
nvidia binary driver doesn't support
--
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/1040206
Title:
nvidia binary driver doesn't support XRandR 1.2/1.3
To manage notifications about this bug go to:
And as an addition: Even when I put the stylus in relative mode and hold
it above the tablet causes touching the left buttons almost every time a
jump in the left corner and back
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom
You say the issue here is not to do with the questions themselves but
that the user needs to be given more information prior to seeing these
questions. Could you elaborate on what that information should
comprise?
For example, would it be sufficient to simply say, Compiz has crashed?
Or would
With the new Retina displays and the trend that they impose we are
shortly going to have displays dpi values from 90 (old large monitors)
to over 300 (newer laptops and tablets). Assuming 96 dpi for everything
will surely lead to interesting times.
--
You received this bug notification because
I tried something different to generate more meaningful output.
-- Logged in from the command-line and ran startx. The session
started just fine, however there was no Gnome Panel loaded whatsoever.
-- Pressed F12 to launch Guake terminal and typed unity --replace
and hit enter. This dropped me
** Attachment removed: IMG_0855.JPG
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272142/+files/IMG_0855.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Attachment added: IMG_0854.JPG
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272147/+files/IMG_0854.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Attachment added: IMG_0855.JPG
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272152/+files/IMG_0855.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I tried something different to generate more meaningful output.
-- Logged in from the command-line and ran startx. The session started
just fine, however there was no Gnome Panel loaded whatsoever.
-- Pressed F12 to launch Guake terminal and typed unity --replace
and hit enter. This dropped me
** Attachment added: IMG_0855.JPG
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+attachment/3272169/+files/IMG_0855.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
This happens on Quantal alpha 3, installed on an Asus G75VW, with a
dedicated GeForce 660M GTX.
On my previous Dell XPS 15z, running a descrete nVidia Optimus card, it
worked just fine when running apps with optirun.
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
I'm not sure this is an xorg bug or kernel driver / other.
Sometimes, when I resume the computer from a suspend, the screen stays
black. Very black. It's now just happened on turning on the computer as
well. This happens about once out of every 4 or 5 times (as far as I
--
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/1040239
Title:
Black screen on startup or resume (only sometimes)
To manage notifications about this bug go to:
** Tags added: compiz
--
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/1039148
Title:
When logging in to Unity, the Desktop session crashes
To manage notifications about this
1 - 100 of 140 matches
Mail list logo
