All the same, perhaps vulkaninfo should issue a warning about vestigial
config if it can find a perfectly usable icd somewhere else! Presumably
it looks for the one supplied by Ubuntu.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Got to the bottom of it and post here in case anyone else has this
problem.
In /etc/vulkan/icd.d there was a link: amd_icd64.json ->
/etc/alternatives/amd_icd64.json
Also a link: /etc/alternatives/amd_icd64.json ->
/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json
(a non existant path)
In
That's not quite true, it was assumed and believed until a little while
ago that I had amdgpu-pro installed which I don't and because of that no
one even looked at the problem. Mark it invalid if you like but the
real problem has not even been investigated.
--
You received this bug notification
Thank you. I have that file:
/usr/share/vulkan/icd.d/radeon_icd.x86_64.json. So now I'm back to
figuring out why vulkaninfo errors out:
vulkaninfo reports:
ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file
amd_icd64.json
There must be some config somewhere that tells
Thank you. It does seem to point to that. Even so, vulkan-mesa-drivers
has been installed and has not provided vulkan-icd. Does it go under a
different name? When I installed vulkan-mesa-drivers, has dpkg or apt
seen a remnant of amdgpu-pro and not installed the icd even though by
normal means
→ apt list --installed|grep amdvlk
(just the interface warning otherwise nothing)
→ apt-cache show amdvlk
N: Unable to locate package amdvlk
E: No packages found
→ apropos amdvlk
amdvlk: nothing appropriate.
→ apt-cache search amdvlk
(nothing)
→ apt-cache search amd|grep vlk
(nothing)
So no, I
I don't see amdgpu-pro when I do this:
→ apt list --installed |grep amdgpu
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
libdrm-amdgpu1/bionic-updates,now 2.4.101-2~18.04.1 amd64 [installed]
xserver-xorg-video-amdgpu-hwe-18.04/bionic-updates,now
'if its vulkan driver does not install its icd file in the correct
place, there's nothing we can do about that'
Thank you for your help. I was not aware of that interaction, only of
what the installed package vulkan-mesa-drivers claimed as stated at the
beginning of this report.
'apt-cache show
Ok, so I went back and re-read some of the most recent comments here -
especially #226 and #229.
This is what works for me:
$ alias vmware="xmodmap -e 'remove control = Caps_Lock ' &&
/usr/lib/vmware/bin/vmplayer"
If I start vmware with this alias, the keyboard on the host does not get
Ok I see this issue is closed as its quite old. Is this particular
issue tracked somewhere else?
I just upgraded my Ubuntu 16.04 system to Ubuntu 18.04.5 and this issue
still exists for me.
what I'd like to be able to do is:
1. configure my keyboard on the host laptop to map "Caps Lock as an
I fixed it by adding a few lines in my /etc/default/grub file! (not sure which
exactly which one of the 3 fixed it)
In the line (GRUB_CMDLINE_LINUX_DEFAULT=) I added to the quotes: iommu=soft
processor.max_cstate=5 idle=nomwait
If anyone can explain what they each do/which ones are necessary
Seeing same problem on my xubuntu machine after upgrade to 19.10. I
tried different GDM's (xubuntu, gnome, xfce) and tried different themes
(default, Adwaita, Breeze, DMZ). I have basic Intel graphics card with
minimal capabilities, and machine is used in production so I'm unable to
experiment
** Changed in: weston (Ubuntu)
Status: Confirmed => Fix Released
--
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/1844775
Title:
HDR support for Ubuntu
To manage notifications about this
HDR i915 for Gfx-Gen9 in CFL/CML: Reviewing in upstream
(https://patchwork.kernel.org/patch/11204583/)
[v2,0/6] Enable HDR on MCA LSPCON based Gen9 devices
[v2,1/6] drm/i915/display: Add HDR Capability detection for LSPCON
[v2,2/6] drm/i915/display: Enable HDR on gen9 devices with MCA Lspcon
For #15,
Sorry for causing you confusion, just put related HDR patch of Gemini Lake for
your reference.
The patch for GLK were in i915 upstream.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.4-rc4=44b42ebfccfd9d6ef377a25e99ae0085b071e868
Gary
--
You
For related commits of i915's HDR support with Gemini Lake,
https://github.com/freedesktop/drm-tip/c...85b071e868
https://patchwork.freedesktop.org/series/25091/#rev15
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Hi Timo and Daniel (@vanvugt),
Any plan for enabling HDR in part of X.org? Thanks!
Gary
--
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/1844775
Title:
HDR support for Ubuntu 20.04
To manage
I am getting the same error as Ricardo
--
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/1763648
Title:
[needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04
To
/lock' )
DistroCodename: zesty
DistroVariant: ubuntu
DpkgHistoryLog:
Start-Date: 2017-11-03 17:06:23
Commandline: apt-get install apt-transport-https
Requested-By: gary (1000)
DpkgTerminalLog:
dpkg: error processing package libx11-doc (--configure):
package is in a very bad inconsistent state
I just installed 304.135 on 16.10 (not 16.04) and was able to log in
--
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/1639180
Title:
no login possible after update to
Seems 0ubuntu1 is in Zesty see https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-304/+bug/1634802/comments/32
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
OK I thought I saw that it was 304.134-0ubuntu1 that fixed it in 16.04
Anyway 304.134-0ubuntu0.16.10.1 is causing the login loop on my system
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
Already did, but just tried again. Still get login loop
According to what I've seen it's
304.134-0ubuntu1.16.10.1 not 304.134-0ubuntu0.16.10.1 that fixed the
problem in 16.04
Note the 0ubuntu1 not 0ubuntu0
If i try to load 304.134-0ubuntu1.16.10.1 I get this mesage E: Version
yes the problem is in 16.10 Yakkety
--
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/1639180
Title:
no login possible after update to nvidia 304.132
To manage
I just tried installing Nvidia again and still same login loop problem.
--
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/1639180
Title:
no login possible after update to
Just reread your message it's version 304.134-unbuntu1 that fixed the
problem in 16.104 not 304.132
--
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/1639180
Title:
no login
What is availble in 16.10 is -0ubuntu0 not -0ubuntu1
--
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/1639180
Title:
no login possible after update to nvidia 304.132
To
I have
NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
with 16.10 nvidia-304 304.134-0ubuntu1 isn't available just nvidia-304
304.134-0ubuntu0 which still cause the login loop
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I agree it's not solved on 16.10
I believe there is an open bug about it on 16.10 but I can't find it.
--
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/1639180
Title:
no
Sorry I mis read the report.
I am getting the login loop with nvidea 304 not 340
--
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/1637652
Title:
stucked in a login loop
To manage notifications
I am also getting the login loop with nvidia-304.134
--
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/1637652
Title:
stucked in a login loop
To manage notifications about this bug go to:
I still have the login loop with 4.8.0-32-generic GNU/Linux after
installing 304.134
At https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-304/+bug/1639180
it seems that the bug for 16.04 was fixed in the package nvidia-
graphics-drivers-304 - 304.134-0ubuntu1
However in 16.10
Oleksandr
OK I tried both.
Actually I had already downloaded the 131 package from (I think it was)
launchpad.
So I tried both again.
I can use Nouveau for now. Problem is I never know if it's going to
freeze with horz lines.
Is there a way to know when nvidia get's fixed in 16.10 so I can
Thanks for suggestions - don't know if I will get a chance to try in
next few days.
--
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/1639180
Title:
no login possible after
dino99
If you are referring to doing
sudo add-apt-repository ppa:graphics-drivers/ppa
then
sudo apt-get update
I did that a few times
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
Oleksandr
yes I put = after nvidia-304
Here's the outup
nvidia-304:
Installed: (none)
Candidate: 304.134-0ubuntu0.16.10.1
Version table:
304.134-0ubuntu0.16.10.1 500
500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety/main
amd64 Packages
100
I wonder if it's because I upgraded to 16.10 on Saturday?
--
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/1639180
Title:
no login possible after update to nvidia 304.132
If I do sudo apt-get install nvidia-304=304.131-0ubuntu3
I get
Version '304.131-0ubuntu3' for 'nvidia-304' was not found
If I try sudo apt-get install nvidia-304=304.134-0ubuntu1
I get
Version '304.134-0ubuntu1' for 'nvidia-304' was not found
--
You received this bug notification because you
Correction
I have
I don't have
nvidia-304 304.134-0ubuntu0 available
I don't have
nvidia-304 304.134-0ubuntu1
--
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/1639180
OK I did
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update.
Now I have nvidia-304 304.1343-0ubuntu0 showing up in Synaptic
I don't have
nvidia-304 304.1343-0ubuntu1
nor is version 131 showing up
In Software and Updates I selected Main Server and reloaded
Maybe I just have
nvidia-304.134 didn't work for me with gforce 7025/mForce 630A (rev a2)
Also I can't get apt-get to find 304.131 any suggestions on that?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-lts-quantal in Ubuntu.
https://bugs.launchpad.net/bugs/1132736
Title:
Xorg fails to start after installing the hardware enablement stack on
precise due to
** Tags added: xorg-server
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-lts-quantal in Ubuntu.
https://bugs.launchpad.net/bugs/1132736
Title:
Xorg fails to start after installing the hardware enablement stack on
precise due to
** Also affects: xorg-lts-trusty (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-lts-trusty (Ubuntu)
Status: New = Confirmed
** Tags removed: hw-specific
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-lts-quantal in Ubuntu.
https://bugs.launchpad.net/bugs/1132736
Title:
Xorg fails to start after installing the hardware enablement stack on
precise due to missing
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/744468
Title:
Can't see second
This happened to me also in Precise Penguin.
I've moved the xorg.conf file out of the way, and it is now using the
xorg.conf.failsafe. Works better for my current configuration.
It resolves the message. It allows me to make configuration changes via
the System Settings utility. That is all
By the way, my xorg.conf file was a custom multi-head configuration that
I had been building over the years.
Right now, I am not using multi-head. So, a default configuration makes
more sense.
The biggest conflict seems to be from trying to use a Matrox G450 (or
G550 - whatever it is), which
If you can grope around on the launcher and find system
settings/display/resolution you can change resolution to restore the screen.
Then you change the resolution back. But you have to close libreoffice while
the screen is still bad. Isn't this bug similar to Bug #676166? Jason Smith
Public bug reported:
Corel AfterShot Pro-tried the suggested:
suod apt-get -f install and still get same error, unable to load new
software from software center now.
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: libdrm-radeon1 2.4.39-0ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
followed suggestion of apt-get -f install, have nvidia card installed
with nvidia drivers also see in Corel install referring to noveau(?)
drivers
package error afterwards libgl1-mesa-dri:i386 error of gcc1 doesn't
recognize 4.4.3-1:ubuntu1-will try again
ProblemType:
I no longer have this issue as a result of some system modifications. I
changed my laptop disk arrangement so that I have two SSDs configured as
RAID0. This has had the sum effect of slightly slowing down boot time
from my previous configuration of just the one SSD. I do not use the
proprietary
I'm getting the same error after using the 32bit mini.iso to install
xbmc following a guide at
http://forum.xbmc.org/showthread.php?tid=116996
GFX card is HD3650 AGP
I have attached a copy of the atisysteminfo-report.txt.
** Attachment added: ati system info report
Also affecting me. The following points may be of interest:
1. Graphics: NVIDIA GeForce G210M with 512MB DDR Dedicated Memory.
2. Machine: Lenovo G550 NTDF3UK (Laptop)
3. Previously I upgraded (on the standard driver) from 11.10 to 12.04 and
this issue did not occur.
4. I erased and
Public bug reported:
It crashes my system. Went through the automatic bug reporting and this
is what I got. Not sure what else to report.
when I run ubuntu-bug nvidia-graphics-drivers-173, it says that the
package nvidia-graphics-drivers-173 does not exist.
ProblemType: Package
DistroRelease:
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/920997
Title:
package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade:
nvidia-173 kernel module failed to build
I see this same problem on with Oneiric on a Dell e6500 laptop with
nVidia Quadro NVS 160M1 graphics. I had no problems in Natty. It goes
away with Unity 2D. It renders terminal and emacs almost unusable.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/507062
Title:
synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
Public bug reported:
package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade
during install of linux-image-3.0.0-11-lowlatency version
3.0.0-11.18ppa1~natty1 from Alessio Igor Bogani ppa:abogani/ppa
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: nvidia-current
--
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/850667
Title:
package nvidia-current 270.41.06-0ubuntu1 failed to install/upgrade:
nvidia-current kernel module failed to
*** This bug is a duplicate of bug 651322 ***
https://bugs.launchpad.net/bugs/651322
** This bug is no longer a duplicate of bug 651935
[STAGING] kernel-oops following wireless problems (rt3090)
** This bug has been marked a duplicate of bug 651322
Ubuntu Kernel Panics on Eee Pc 1001ha
As per other posters I see the comment No proprietary drivers are in
use on this system. Later in the 'Additional Drivers' dialog it states:
This driver is activated but not currently in use. I don't see the
version it recommends, it simply says: NVIDIA accelerated graphics
driver (version
Public bug reported:
Binary package hint: xserver-xorg-video-nouveau
I've upgraded to natty. I now cannot see the my second monitor plugged
into the vga port in then gnome monitors dialog, nor in xrandr. My
laptop is a Dell Vostro 1500
lspci row:
01:00.0 VGA compatible controller: nVidia
** Tags added: macbook
--
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/416516
Title:
Touchpad isn't sensitive enough on MacBook 5,2
I verified that updating to libgl1-mesa-glx 7.10.1-0ubuntu2 fixes the
Software Center SIGSEGV on my machine (amd64).
Thank you for your great work on this, Chris!!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
Set Fix Released for the Software Center task as well. \o/ Thanks
again Chris, you rock!!
** Changed in: software-center (Ubuntu Natty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
Hi Joe, thanks for your comment.
I see this bug on my Natty Alpha install. I have to do the LD_PRELOAD
every time though (the work around suggests it only has to be done once).
Hmm, ok, I may have to remove that statement as it appears it may not
always apply. Thanks for letting us know.
** Description changed:
Binary package hint: libgl1-mesa-dri
+
+ ---
+ WORKAROUND for the software-center crash:
+
+ Launch Software Center from the command line as:
+
+ LD_PRELOAD=/usr/lib/libstdc++.so.6 software-center
+
+ This should only be needed the first time; after this
** Description changed:
Binary package hint: libgl1-mesa-dri
---
+ Software Center error description from apport is: software-center crashed
with SIGSEGV in __cxa_allocate_exception()
WORKAROUND for the software-center crash:
- Launch Software Center from the command line as:
+
** Also affects: software-center (Ubuntu)
Importance: Undecided
Status: New
** Changed in: software-center (Ubuntu)
Importance: Undecided = High
** Changed in: software-center (Ubuntu)
Assignee: (unassigned) = Gary Lasker (gary-lasker)
--
You received this bug notification
Set as also affects software-center, please see bug 731724 for details.
--
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/259219
Title:
Broken TLS support in libGL.so
Confirming issue is shown:
- in terminator and gnome-terminal
- during gnome classic session and during unity session
- with metacity and with compiz
- on an up-to-date natty installation (i.e. maverick upgrade not needed)
--
You received this bug notification because you are a member of
** Tags added: regression-release
--
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/717114
Title:
[i945gm] Screen Corruption with new Xorg stack with terminal programs
Public bug reported:
Binary package hint: xserver-xorg-video-intel
0
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel 2:2.14.0-1ubuntu11
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
Chipset:
--
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/727205
Title:
[i915g] GPU lockup a44d7ed5 (ESR: 0x0001 IPEHR: 0x7f9c0012)
___
** Visibility changed to: Public
--
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/722913
Title:
Xorg assert failure: *** glibc detected *** /usr/bin/X: double free or
corruption (!prev):
I've done that now Phillip, what next?
--
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/656241
Title:
Mixxx with ATI graphics card (using FGLRX) crashes Ubuntu
It ran, it opened Mixxx but then as usual Mixxx just went off after
about 3 seconds.
Phillip have you seen Bill Good's posts where he thinks my problem maybe
different then other peoples as I'm not using FGLRX? Are you able to
help with is?
--
You received this bug notification because you are
@jus
g...@gary-hp-nx9005-dj260t:~$ '/home/gary/Desktop/mixxx'
Debug: [Main]: Mixxx mixxx-1.9 (bzr r2679; built on: Jan 10 2011 @ 02:33:57;
flags: hifieq midiscript qdebug vinylcontrol) is starting...
Debug: [Main]: Qt version is: 4.7.0
Debug: [Main]: Configuration file is at the current
Sorry Guys, with me being a novice with Linux you've completely lost me,
Could someone explain step by step what I need to do?
Any help is greatly appreciated.
Thanks
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
** Tags added: macbook
** Tags removed: ubuntu
--
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/700282
Title:
[i945gm] GPU lockup 585b0b66 (PGTBL_ER: 0x0102)
Can someone explain what or how I do with the patch???
Thanks
--
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/656241
Title:
Mixxx with ATI graphics card (using FGLRX) crashes Ubuntu
g...@gary-hp-nx9005-dj260t:~$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
GLX_EXT_visual_info
g...@gary-hp-nx9005-dj260t:~$ lsmod
Module Size Used by
snd_seq_dummy 1350 0
nls_iso8859_1 3261 0
nls_cp437 4931 0
vfat9201 0
fat48240 1 vfat
usb_storage40172 0
binfmt_misc
Hi RJ,
I'm not to sure on the QT4, got it installed but couldn't work out how
to run the 'textures'.
As for the 'fglrx' I'm not running it. See screendump
Not sure if this is going to help.
Sorry
** Attachment added: fglrx in Synaptic Package Manager
If I enable the waveforms after loading and playing the first track, it
still shuts down when the next track is then played in the other
channel.
--
Mixxx with ATI graphics card (using FGLRX) crashes Ubuntu
https://bugs.launchpad.net/bugs/656241
You received this bug notification because you are
Does anyone know if we are any closer to fixing this bug?
--
Mixxx with ATI graphics card (using FGLRX) crashes Ubuntu
https://bugs.launchpad.net/bugs/656241
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
*** This bug is a duplicate of bug 651935 ***
https://bugs.launchpad.net/bugs/651935
** This bug is no longer a duplicate of bug 651322
Ubuntu Kernel Panics on Eee Pc 1001ha due to wireless
** This bug has been marked a duplicate of bug 651935
[STAGING] kernel-oops following wireless
Hi RJ
Not sure what 'fglrx' is or does but attached is the search for it in my
Synapic Package Manager. Not to sure about the last one in the list it
seems to have an '!' on the left.
Regards
Gary
** Attachment added: Synapic Package Manager Screen Dump
https://bugs.launchpad.net/mixxx
** Changed in: nvidia-graphics-drivers (Ubuntu Maverick)
Status: New = Invalid
** Changed in: qt4-x11 (Ubuntu Maverick)
Status: New = Invalid
--
Launching QT apps under Xinerama crashes Xorg : affects SpeedCrunch, KeePassX,
Lucky Backup, Pencil, Stellarium, Skype, Google Earth,
** Changed in: xorg (Ubuntu)
Status: New = Confirmed
** Also affects: xorg-server via
http://bugs.freedesktop.org/show_bug.cgi?id=30943
Importance: Unknown
Status: Unknown
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Invalid
** Tags added:
Seems to be similar to 610285, and present in 10.04
I have noticed that behaviour is different when booting with the AC
adapter connected. It seems to be more flakey when booting on battery
power.
--
touchpad lockup/drag and lost scroll
https://bugs.launchpad.net/bugs/34501
You received this
Joshua, if you think it may have something to do with the RT3090 driver
from Marcus, try uninstalling it and instead use the rt3090 staging
driver built in to the Lucid kernel. You'll need to run a command first
to create an empty missing config file -- see comments near the top of
bug #541620.
Hi! I am having the same problem on 10.04. Has a resolution been made?
Cheers!
--
unlocking screen leads to window manager not working
https://bugs.launchpad.net/bugs/290288
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Control Center, if I try to
rotate the screen again it gives the following error:
Current settings can not be applied. Possible issues include:
Display(s) cannot be enabled
Setting(s) cannot be applied due to insufficient video memory
Thanks and regards,
Gary
On Sep 20, 2010 11:02 AM
Public bug reported:
Set desktop to multi-display and rotated one to right using ATI Catalyst
Control Center.
Rebooted and all worked well with no errors.
Used update manager to update system and accepted all 200+ updates (it's a new
install).
Upon completion, rebooted and received error about
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/643174/+attachment/1611096/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/643174/+attachment/1611097/+files/CurrentDmesg.txt
** Attachment added: DKMSBuildLog.txt
Public bug reported:
crashed on update / install
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.24-0ubuntu1~10.04
ProcVersionSignature: Ubuntu 2.6.32-24.43-generic-pae 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic-pae i686
NonfreeKernelModules: nvidia
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/642186/+attachment/1603746/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/642186/+attachment/1603747/+files/CurrentDmesg.txt
** Attachment added: DKMSBuildLog.txt
** Tags added: lucid
--
[P4M900] Laptop TFT flickers after wake up from S3 sleep
https://bugs.launchpad.net/bugs/422202
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
1 - 100 of 145 matches
Mail list logo
