Public bug reported:
gpu no to supporter
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13
s.
I've got to the desktop in 640x480! Using:
Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
I'm out of ideas now. I'll enquire on the forum.
Regards,
Mani.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-304 (not installed)
ProcVersionSignature: Ubuntu 4.2.
sorry I meant 3.8 headers not 3.5 headers
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1176429
Title:
fglrx-updates 2:9.000-0ubuntu0.3: fglrx-updates kernel module failed
It happend after I installed linux-image-generic-lts-raring and after that
linux-headers-3.5.0-28-generic which tried to compile the fglrx .
I had no such a problem with linux-image-generic-lts-quantal and kernel 3.5
headers are installed and everything was compiled ok. (and I'm using it now) I
Public bug reported:
Here are some log file, virtualbox 4.1.2 fails to compile too but I think its
not relevant here
/var/lib/dkms/fglrx-updates/9.000/build/make.log
DKMS make.log for fglrx-updates-9.000 for kernel 3.8.0-19-generic (x86_64)
Sat May 4 21:43:57 BST 2013
/usr/sbin/dkms: line 73: cd
/var/lib/dkms/fglrx-updates/9.000/build/make.log
DKMS make.log for fglrx-updates-9.000 for kernel 3.8.0-19-generic (x86_64)
Sat May 4 21:43:57 BST 2013
/usr/sbin/dkms: line 73: cd: /var/lib/dkms/fglrx/9.000/build: No such file or
directory
AMD kernel module generator version 2.1
doing Makefile b
** Attachment added: "Example video"
https://bugs.launchpad.net/bugs/686592/+attachment/1758528/+files/out.ogv
--
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/686592
Title:
Tooltips/me
Public bug reported:
It happens quite often that tooltips / menus are not displayed until the cursor
is moved over the area where they should appear.
Following observations:
- This does not appear to be a bug in a specific driver, can reproduce it with
xorg-intel, xorg-ati and fglrx
- This does
get home.
> Did anyone have issues installing on lucid64?
>
> On Sat, May 22, 2010 at 10:52 AM, Sandro Mani
> wrote:
>
>
>> In karmic it should be no problem:
>> - Uninstall any nvidia packages installed from the ubuntu repos
>> - Download the beta driver and
In karmic it should be no problem:
- Uninstall any nvidia packages installed from the ubuntu repos
- Download the beta driver and make it executable (chmod +x
/path/to/NVIDIA-Linux-(x86|x86_64)-256.25.run)
- Switch to a virtual terminal (i.e. ctrl+alt+f2), login
- Stop X: sudo service gdm
Status updates:
- The cause of the issue is not X anymore
- The issue has been fixed in the latest nvidia beta driver, see
http://www.nvnews.net/vbulletin/showthread.php?p=2255561
- The issue does still affect fglrx with unknown status
** Changed in: xorg-server (Ubuntu)
Status: Incompl
For all those affected with nVidia hardware, nvidias Aaron Plattner has
just announced that the issue will be investigated, see
http://www.nvnews.net/vbulletin/showthread.php?p=2239566 .
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://
The problem is fixed as far as all open drivers are concerned. The issue
with the binary driver remains and will probably remain as long as no-
one with hardware that is affected cares to report the issue to the
respective places (i.e. nvnews for nvidia, virtualbox bug tracker for
virtualbox, and h
Look: software evolves, and sometimes API breaks and things like that
are necessary. While you may be unhappy about the situation, there is
indeed nothing the open community can do if the developers behind the
closed source drivers do not want to react on the issue. That is, if
they really do n
>From what I can see the issue has never been brought up at nvnews, which
is apparently one of the only ways to report problems with the binary
nvidia driver to their developers. I'd suggest someone who is affected
might want to try to point out the issue there (any maybe there is some
similar foru
May I point out that the last person actually stating that it had the
problem with intel graphics was back in september 2009, in comment 144?
Since then, the issue has only been confirmed on binary drivers (except
lunix which still needs to verify), while there are several reports of
things wor
First of all do a sudo apt-get autoremove to remove all those packages.
A side of that, you appear to have some residuals from the
xorg-driver-fglrx package which no longer exists. Try to sudo apt-get
purge xorg-driver-fglrx. If that does not work, your package database
may be messed up from so
wild.ideas: "That being the case, perhaps someone ought to prove it out
by installing the Nvidia drivers from the 8.04 era into a fresh install
of 9.10 and demonstrating that binary nvidia + compiz + xdamage enabled
= no problem.
Or has this been done already?"
That cannot be done since those dri
"The remote desktop solution in Ubuntu uses the VNC backend which can't
read from hardware accelerated display"
That's hardly true, testing on a few xserver 7.5 machines (running fedora 12
but that should not make any difference)
* intel + compiz + xdamage enabled = no problem
* open source radeo
@mattrenfer
The open-source driver has yet to mature especially in the 3D area, currently
you won't get full performance. Since AMD decided to ditch support for older
graphic-cards in their binary driver, you'll have to wait a while until the
open driver gets optimized.
--
Does not support cur
The drivers available from the official AMD/ATI website do not yet
support the lucid kernel / xserver - use the packages that just got
pushed to the lucid repositories (which basically is a unreleased
catalyst) - you may have to wait a few hours until all mirrors are up-
to-date, or you can take a
Go ahead and create one, quickly post back the link to the topic here.
--
[GM45] 3D applications fail to run in WINE
https://bugs.launchpad.net/bugs/406865
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
Have you change or set some custom xorg parameters with previous
attempts? Otherwise it can very well be that the build of the driver you
got is indeed broken, which is not that unlikely to happen with daily
builds. You can wait a few days for the next few builds to see if they
fix the issue, but I
Well concerning at least 9.04, it was in the middle of the EXA -> UXA
transition with new stuff coming in like KMS and GEM, therefore things were not
really stable back then (and as far as I recall also fedora had plenty of
problems at that stage). If you want to stick with ubuntu you'll need to
Hi,
it is not that fedora has figured out something that ubuntu has not, it is just
that it is more a bleeding edge distribution than ubuntu is, which means that
you often get upstream fixes faster than in ubuntu, but also that you might
have to deal with upstream regressions in a more unplesant
Concerning the X crash, yes - but it won't help much concerning the
other issue (unless maybe you try bleeding edge packages from the X
crack pushers PPA, but I haven't tried them myself and cannot guarantee
they fix the issue - keep in mind that they also might make your system
unusable).
--
[GM
Concerning the X crash: this should have been fixed a while ago (see bug
#401067), if you have this issue with an up-to-date system would you
please collect a backtrace (see http://wiki.ubuntu.com/X/Backtracing)
and open a new bug?
For the rest from what I can see the problem is fixed in newer x a
Okay, it was the disable keyboard while typing setting which seems to
have been enabled by default in karmic. Just a notice: it makes many
games totally unplayable which might confuse some users.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New => Invalid
--
Touchpad freez
I tested with a live cd of karmic release and still have this issue. As
opposed with what I wrote in the description this actually seems to
affect any keyboard key / hotkey: when pressing one of them about 2
times out of 3 the touchpad will freeze for about 1 second. This does
not happen with an ex
*** This bug is a duplicate of bug 392544 ***
https://bugs.launchpad.net/bugs/392544
Tried on the machine were I was seeing the issue and indeed the 2.6.32
mainline kernel from kernel ppa fixes the problem, as described in bug
#392544. Marking as dupe.
** This bug has been marked a duplicate
Could be a good idea, if without KMS you do not have the issue then we
could mark this bug a dup of the other one. As stated in the comments of
the other report, also using newer mainline kernels (latest 2.6.32 rc)
should fix the issue. (Unfortunately I don't currently have access to
the pc I encou
That would only be to disable KMS in which case the issue should not
appear. But are you also seeing the issue with an intel graphicscard?
--
Incorrect monitor detection by Ubuntu in Karmic beta
https://bugs.launchpad.net/bugs/455235
You received this bug notification because you are a member of
Related with #392544 ?
--
Incorrect monitor detection by Ubuntu in Karmic beta
https://bugs.launchpad.net/bugs/455235
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
Mailing lis
Same problem here, only detecting up to 800x600 instead of 1024x768. Can
sucessfully override as described here:
http://ubuntuforums.org/showthread.php?t=945465
--
Incorrect monitor detection by Ubuntu in Karmic beta
https://bugs.launchpad.net/bugs/455235
You received this bug notification becaus
I am also experiencing this issue, backtrace of X crash attached.
** Attachment added: "xcrash.log"
http://launchpadlibrarian.net/33973899/xcrash.log
--
gnusound crashes X session immediately on launch (Affects Intrepid, Jaunty,
Karmic)
https://bugs.launchpad.net/bugs/282939
You received thi
** Attachment added: "out.ogv"
http://launchpadlibrarian.net/33944329/out.ogv
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/33944337/BootDmesg.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/33944339/CurrentDmesg.txt
** Attachment added: "De
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
Using up-to-date karmic as of 19.10.09, hardware is a Lenovo T400.
Problem: when pressing certain keyboard shortcuts / hotkeys, the mouse cursor
hangs for about one second before resuming normal motion. I attached a video
sh
Just a side curiosity, why are shadows of those applets treated
differently than the shadows of other objects in the first place? Note
for instance that while windows / menus drop shadows on whatever is
behind them, the clock applet seems to only drop a shadow if the desktop
is behind it (but not i
Just a notice: this bug is now also present with stock karmic packages,
I suspect since the latest mesa update
(7.6.0~git20090817.7c422387-0ubuntu2)
--
[GM45] 3D application fail to run through Wine and often crash X
https://bugs.launchpad.net/bugs/401067
You received this bug notification becaus
Okay!
--
[GM45] 3D application fail to run through Wine and often crash X
https://bugs.launchpad.net/bugs/401067
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
___
Mailing list: ht
*** This bug is a duplicate of bug 386017 ***
https://bugs.launchpad.net/bugs/386017
Indeed, now that you pointed it is exactely what I am experiencing.
Marking as duplicate, thanks.
** This bug has been marked a duplicate of bug 386017
Brushing right-edge of trackpad causes clipboard to p
Uhm I never experienced the issue described there, the issue here is
more general, i.e. the touchpad driver misreports events and then the
program executes actions as if the reported button was pressed.
--
Touchpad randomly fires incorrect events when scrolling
https://bugs.launchpad.net/bugs/414
** Description changed:
Using up-to-date karmic as of 15.08.2009
Problem:
- When using the "virtual scroll" on the touchpad (i.e. only moving the finger
on the right side of the pad, not pressing any button!), occasionally
(apparently randomly) incorrect events are generated.
+ When using
I suspect this issue could be related with the one I described in bug
#414127. Is anyone who is experiencing this issue also experiencing
issues like the one I described there?
--
[regression] rapid pointer movements with touchpad ignored
https://bugs.launchpad.net/bugs/405943
You received this b
Public bug reported:
Using up-to-date karmic as of 15.08.2009
Problem:
When using the "virtual scroll" on the touchpad (i.e. only moving the finger on
the right side of the pad, not pressing any button!), occasionally (apparently
randomly) incorrect events are generated.
I can easily reproduce
(The "and often" should not be there..)
--
[GM45] 3D application fail to run through Wine and often crash X
https://bugs.launchpad.net/bugs/401067
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
_
Just a short notice: as Bryce and often said above, this bug focuses on
the occasional X crash. For the failure that only crashes / hangs wine
(including GLXBadDrawable) I have opened a new bug #406865.
--
[GM45] 3D application fail to run through Wine and often crash X
https://bugs.launchpad.net
I indeed forgot the cont via ssh... Anyway, backtrace attached.
** Attachment added: "gdb-xorg.txt"
http://launchpadlibrarian.net/29826019/gdb-xorg.txt
--
[GM45] 3D application fail to run through Wine and often crash X
https://bugs.launchpad.net/bugs/401067
You received this bug notification
Just an update from my part: I am still trying to get a backtrace via gdb, but
as before, as soon as I attach gdb to X, X hangs until I terminate it, no
matter if I start gdb from a VT, via ssh or within the gdm session itself. I
also tried to launch gdm via gdb, but I had some difficulties to p
Thanks for the background info!
I tried to obtain some backtraces with the xorg edgers packages, at the moment
the only one I managed to get was the one appended at the end of the gdm log of
the crashed session, which is attached.
Unfortunately gdb seems to hang X as soon as I attach it to the ru
Okay, so I did some testing, and it looks like one of the updates in the past
few days fixed the X crashing. Also, I did not experience any crashing or
hanging anymore after testing some native Linux 3D applications.
What however remains is wine failing on any attempt to run a non-native 3D
appl
Concerning the statement "The problem is very likely caused by a problem with
the intel graphics driver.", I had a look at different setups and got the
following results:
- Both Jaunty and Karmic, GM45 (the Lenovo T400 I am experiencing the problem
on): crash as described
- Jaunty, proprietary A
Also native linux applications seem to have problems: I tried compiling
and running vdrift, and X froze as soon as a track finished loading.
Soundplayback did continue for a while though, which seems to indicate
that only X froze and not the whole system... Again, I did not find any
helpful informa
Hello,
Xorg.0.log is attached. Additionally I did some other testing, and I forgot to
mention that the attempts often end with messages like
X Error of failed request: GLXBadDrawable
Major opcode of failed request: 153 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial num
** Description changed:
- Running an up-to-date Ubuntu Karmik x86_64, hardware details attached.
+ Running an up-to-date Ubuntu Karmic x86_64, hardware details attached.
Problem:
3D applications fail to run through wine without any exception. Furthermore,
there is a 80% chance that the X s
55 matches
Mail list logo
