Yes an ideal world ,sounds like windoze ?.nvidia's binary wont support it ?,if
they back ported ( cough) or allowed the windows port ( developed on nux -with
emacs closed source) for use in linux it all would make sense and the X server
would need an update to support more than the current
Great Stoo,
So I'm closing this bug report and if you feel like that the bug has again
encountered please feel free to open the bug report again by setting the status
to New again.
Keep filing bugs!!
Cheers
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed = Invalid
@juliobahar
Actually the problem of the original bug reporter Max was quite different of
yours and Alan's. So in that regard I was requesting you to file another bug
report that mentions yours and Alan's issue so I can close this bug report.
Still, no problem I will do that for you..
--
@ julio @ Alan
Still it will be good you can file the bug report and subscribe me there so we
can continue there by
Just type this in your terminal
$ ubuntu-bug linux
--
Scroll region at bottom edge of pad inoperable in maverick
https://bugs.launchpad.net/bugs/660887
You received this bug
@ Max
As you cannot provide us with data with your bug report, so I'm closing this
bug report and if in future you feel like you can somehow provide us with data.
Please open this bug report again by putting the status to New again.
Keep filing bugs..
Cheers!!
** Changed in:
Flashed my MSI K9N2GM-FIH to the latest v.3.8 BIOS and booted to
2.6.32-25 on 10.04 x86_64 and the mouse stopped responding after less
then 10min (No audio or video files playing or any programs running this
time). I'm back to 2.6.31-11-rt and all is well again.
My Acer Aspire 6920G Laptop (Intel
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: (unassigned) = Robert Hooker (sarvatt)
--
[i965gme] GPU lockup c472ca4a
https://bugs.launchpad.net/bugs/668270
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel
Hi Adam Spiers,
Thanks for reporting the bugs. I see that the bug has changed overtime and is
now very different from what you intended to file at beginning. To avoid
confusion, I request you to file another bug that mentions your new issues
right from start against the kernel instead.
Please subscribe me there after filing the bug report.
--
touchpad detected as ImPS/2 even though multi-touch works
https://bugs.launchpad.net/bugs/658017
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
Hi bve,
Thanks for reporting bug and helping us to make ubuntu, even better.
Unfortunately, the information you liked with the bug report is not
sufficient for us to probe into the bug. For developers to work on this
bug we want to have additional information from you, regarding the bug.
I hope
This is our first official natty GPU freeze bug.
@Robert, could you please investigate if there are any similar bug
reports from maverick, in which case dupe them to this bug report for
further analysis. Don't forget to tell me what analysis apport should
do for isolating dupes.
@kingr4t - you
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete = Invalid
--
touch-pad multi-finger features do not work
https://bugs.launchpad.net/bugs/575445
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Not getting any response from the original bug reporter, I'm closing
this bug report. If anybody facing the bug feel like they can provide us
with information regarding this bug. Please feel free to reopen this bug
by setting the status to new again.
Keep on filing bugs
Cheers!!
** Changed in:
I feel pretty strongly that this fix should be pushed out *immediately*,
even in its currently incomplete state. This one would make most users
downgrade or even switch back to Windows immediately.
When I was experiencing this bug every 5 minutes, I really felt like I
was using alpha-quality
Just to confirm before closing the bug report, as the fix has been
released in upstream kernel. Can anybody confirm that the problem exists
or not on Maverick?
--
touchpad randomly failing
https://bugs.launchpad.net/bugs/365968
You received this bug notification because you are a member of
Hi Bug reporter,
Thanks for reporting bug and helping us to make ubuntu, even better.
Unfortunately, the information you liked with the bug report is not
sufficient for us to probe into the bug. For developers to work on this
bug we want to have additional information from you, regarding the bug.
Hi kanethornwyrd
Thanks you for taking your time to file the bug report. Does the bug
still exist in maverick?
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided = Low
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Incomplete
--
[Toshiba
*** This bug is a duplicate of bug 27541 ***
https://bugs.launchpad.net/bugs/27541
Yes mike,
I'm new here and my mother tongue is not English, so be patient with me!
Any help is welcome.
Thanks
--
Touch-pad crazy with Ubuntu 10.04 on laptop Aspire 8530
@ Alan
Are you willing to do that or should I proceed? if you did please subscribe me
too.
--
Scroll region at bottom edge of pad inoperable in maverick
https://bugs.launchpad.net/bugs/660887
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
While waiting for clear step by step instructions (my mother tongue is
not English and I'm not expert) to modify delay parameter -i to help
on solving the issue with results from my tests, I inform that the
solution reported on comment #21 (thick paper on the palm rest) seems to
work at moment
Public bug reported:
Binary package hint: xorg
In my xorg.conf file I have:
Virtual 4800 1200
I can set back to 3200 1200 I get X working again, but now I lose one of
my screens. Note: in the attached xorg.conf file all 3200 1200 entries
are 4800 1200 when I get the crash.
My
--
Xorg crash due to Virtual 4800 1200
https://bugs.launchpad.net/bugs/669365
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post
** Description changed:
Binary package hint: xorg
In my xorg.conf file I have:
-Virtual 4800 1200
+ Virtual 4800 1200
- When I set back to 3200 1200 I get X working again, but now I lose one
- of my screens.
+ I can set back to 3200 1200 I get X working
Maybe it is related with this bug. When I try to see taskbar thumbnails,
they appear empty (screenshot1).
** Attachment added: Screenshot1
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/601530/+attachment/1719195/+files/screenshot1.png
--
[965gm]
And when I show all apps using Showing Windows, they dissapear
suddenly, showing their name only (screenshot 2)
** Attachment added: Screenshot2
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/601530/+attachment/1719196/+files/screenshot2.png
--
[965gm]
James: I, too, found it very annoying to contend with. However, I think
the reasoning is that the original bug only affects a small slice of
Ubuntu users. If the fix isn't behaving properly, there's a risk that it
will break things for other users. That said, I hope it gets sorted
soon.
--
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
The lower 1/4 - 1/3 part of the my touchpad doesn't not produce cursor
movement, nor events in xev evtest.
Horizontal scrolling is not functional and can NOT be enable in
gpointing-device-settings.
This is on a Lenovo
--
Touchpad bottom edge unresponsive in ubuntu 10.10 64-bit
https://bugs.launchpad.net/bugs/669399
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
___
Mailing
Never mind my question I've already open a new bug report and subscribed you
guys Gursimran Alan
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/669399
--
Scroll region at bottom edge of pad inoperable in maverick
https://bugs.launchpad.net/bugs/660887
You received
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Confirmed
--
Touchpad bottom edge unresponsive in ubuntu 10.10 64-bit
https://bugs.launchpad.net/bugs/669399
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
it's impossibile to remove proprietary ATI driver
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: fglrx
--
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: subprocess
installed post-removal script returned error exit status 2
https://bugs.launchpad.net/bugs/669416
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
Excellent! My suspicions after doing some reading was a regression in
the kernel due to some other bug reports I've read related to the kernel
and other distros.
Hopefully some of the other people who have been having this problem
reports back, and the Ubuntu devs can get off easy on this one.
Can someone summarize the actual real fix (not any workarounds) and/or
highlight the changeset to whichever Debian/Ubuntu package to
601...@bugs.debian.org so that Debian Squeeze can have the problem
resolved as well?
--
[Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave
** Description changed:
Binary package hint: xserver-xorg-video-intel
using java
+ ---
+ PCI ID: 0x2a12
+ EIR: 0x
+ PGTBL_ER: 0x
+ INSTPM: 0x
+ IPEIR: 0x
+ IPEHR: 0x0182
+ INSTDONE: 0xffe5fafd
+ busy: Projection and LOD
+ busy:
I have successfully come back from 3 or 4 suspends this morning, so
looking hopeful.
--
computer freezes on suspend/hibernate
https://bugs.launchpad.net/bugs/660405
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
Laptop : Thinkpad T410, Intel core i5 520 M.
With a Lucid Lynx 10.04 LTS, 2.6.32.15 from package (linux-
source-2.6.32_2.6.32-24.43_all), there is no problem, no warnings at
boot time.
With a Lucid Lynx 10.04 LTS, 2.6.36 from kernel.org, at boot time,
kernel warns: failed to get i915 symbols,
Still present in up-to-date Lucid.
Please see
https://bugzilla.redhat.com/show_bug.cgi?id=533066
This is *very* annoying and I'm having it on very different setups. Also
heard others in my vicinity complaining about it...
** Bug watch added: Red Hat Bugzilla #533066
** Visibility changed to: Public
--
Xorg assert failure: X: /usr/include/xorg/privates.h:122: dixGetPrivateAddr:
Assertion `key-initialized' failed.
https://bugs.launchpad.net/bugs/635362
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server
Same problem and noticed this weekend while working in Google Chrome
browser that after scrolling down page several times, seemed to cause
the lock up as well.
Ubuntu 10.10 x86_64
HP Elitebook 8530W
Nvidia Quadro
--
System freezes when running on battery
https://bugs.launchpad.net/bugs/662998
** Changed in: xorg (Ubuntu)
Status: Incomplete = Confirmed
--
xorg wrong window selected when clicking title bar
https://bugs.launchpad.net/bugs/559202
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
I am seeing the identical symptoms reported above after upgrading from
Lucid - Maverick.
Output of lspci -vv is attached.
** Attachment added: output of lspci -vv
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/601530/+attachment/1719381/+files/lspci.txt
--
[965gm]
** Summary changed:
- Unity crashes on ATI radeon
+ Unity crashes on ATI Radeon
--
Unity crashes on ATI Radeon
https://bugs.launchpad.net/bugs/630315
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
From the DKMS log:
DKMS make.log for fglrx-8.723.1 for kernel 2.6.32-25-generic (x86_64)
Sun Oct 31 17:56:22 GMT 2010
AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
Makefile:99: *** mixed implicit and normal rules. Stop.
Makefile:99: *** mixed
More info. My left monitor is attached to the DVI output, and the right
monitor is attached to the VGA output. I use the following commands
after I login to disable then enable the monitor attached to the VGA
output:
xrandr --output VGA0 --off
xrandr --output VGA0 --auto --right-of DVI0
--
The problem I can confirm also.
--
xorg wrong window selected when clicking title bar
https://bugs.launchpad.net/bugs/559202
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailing
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete = Confirmed
--
Touchpad bottom edge unresponsive in ubuntu 10.10 64-bit
https://bugs.launchpad.net/bugs/669399
You received
The bug, if it is that, is that the new nvidia drivers are not
compatible with the X server.
--
Boot quits, sends the monitor into powersave
https://bugs.launchpad.net/bugs/665646
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
Cannot boot from hard drive
https://bugs.launchpad.net/bugs/595352
You received this bug notification because you are a member of
I think the following patch should fix the issues noted here:
http://git.kernel.org/?p=linux/kernel/git/jikos/hid.git;a=commitdiff;h=f51661105c3c8a0afcd69f995a4f4a10e53da153
The patch should be in the 2.6.37-rc1. The kernel will be packaged and
published soon to:
I think the following patch should fix the issues noted here:
http://git.kernel.org/?p=linux/kernel/git/jikos/hid.git;a=commitdiff;h=f51661105c3c8a0afcd69f995a4f4a10e53da153
The patch should be in the 2.6.37-rc1. The kernel will be packaged and
published soon to:
Gursimran, here you are. Really does seem to be a kernel regression.
I ran evtest in a vty and then pressed buttons 1, 2, and 3 above and below the
touchpad.
I'll test in which kernel version from http://kernel.ubuntu.com/~kernel-
ppa/mainline/ the regression was introduced...
** Attachment
** Attachment added: maverick kernel
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/666968/+attachment/1719545/+files/evtest_kernel2.6.35-23-generic.txt
--
Button 2 (middle) on touchpad works as button 1 (left)
https://bugs.launchpad.net/bugs/666968
You received
You dont need to go into recovery mode to do that just add nomodeset to
the Kernel your trying to boot.
--
Ubuntu 10.10 wont start strange image
https://bugs.launchpad.net/bugs/654178
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
-proposed added to sources, update/upgrade'd, libdrm2 is installed, the
problem is still very much present.
How is this not fixed yet? Surely this must be affecting a lot of people.
Most budget netbooks will have intel chips, and a fair amount of these users
must enjoy using an external monitor
I think the flickering displays is a different issue. This bug is about
only seeing a narrow window on the second monitor, the total image width
being limited to 2048 pixels. That bug is fixed I believe. I think
those seeing flickering windows had better look for a different existing
bug or
Flickering is a different issue. File a new ticket (or find another one
which matches your problem). This is about not rendering widths 2048
pixels.
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug
I do have the TV plugged into the HDMI connector but it is disabled on the
display manager config because I don't use it.
I was unable to reproduce the crash with another app, please note that the bug
is always reproducible with virtualbox, I am unable to use it.
I have assumed it was fgrlx
With all due respect I believe this is just a different manifestation of the
same bug.
The reason I say this is, if the combined width is 2048, the flicker does not
happen and the monitors will actually work. I'm not overly familiar with how
these bug responses work but when I saw others
Hi Alexander Steffen,
i want to write a script like you on a debian testing, can you maybe
send me your rules and the script? (mariuskna...@googlemail.com)
Ty very much,
Marius
--
udev scripts running as root cannot use xrandr
https://bugs.launchpad.net/bugs/660901
You received this bug
** Changed in: xorg (Ubuntu)
Status: New = Invalid
** Changed in: xorg (Ubuntu)
Status: Invalid = New
--
Error message when I start my laptop
https://bugs.launchpad.net/bugs/668720
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
** Description changed:
Binary package hint: xorg
Hello from France,
When I start my computer (Laptop ASUS F5RL) sometimes this message appear and
I can't log it :
- [drm:vs400_gart_adjust_size] *ERROR* Forcing to 32M GART size (because of
ASIC bug?)
+ [drm:vs400_gart_adjust_size]
Public bug reported:
Further information:
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
Uname: Linux 2.6.34-020634-generic i686
Architecture: i386
Date: Mon Nov 1 20:23:41 2010
ErrorMessage: fglrx kernel module failed to build
InstallationMedia: Ubuntu 10.04
--
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module
failed to build
https://bugs.launchpad.net/bugs/669577
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.
Situation on Maverick is the same in Lucid, but I had to add Xorg-crackers
repository, because opengl apps crashed in fullscreen. My FPS in openarena is
28-40 FPS and in compiz is 42 FPS. Openarena is playable but some games are too
slow to play, when KMS is enabled, but when KMS is disabled
Ubuntu 10.04 shipped with a 2.6.32 kernel. You upgraded the kernel to
2.6.34. The 8.723 driver doesn't support kernel 2.6.34. Try a current
Catalyst release.
--
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module
failed to build
https://bugs.launchpad.net/bugs/669577
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719716/+files/BootDmesg.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: GdmLog.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719718/+files/GdmLog.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719717/+files/CurrentDmesg.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a
apport information
** Attachment added: GdmLog1.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719719/+files/GdmLog1.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: GdmLog2.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719720/+files/GdmLog2.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719721/+files/Lspci.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719722/+files/Lsusb.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: PciDisplay.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719723/+files/PciDisplay.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719724/+files/ProcCpuinfo.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719725/+files/ProcInterrupts.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719728/+files/UdevDb.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719726/+files/ProcModules.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719727/+files/RelatedPackageVersions.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719729/+files/UdevLog.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: XorgConf.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719730/+files/XorgConf.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: XorgLog.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719731/+files/XorgLog.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: XorgLogOld.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719732/+files/XorgLogOld.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member
apport information
** Attachment added: Xrandr.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719733/+files/Xrandr.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: nvidia-installer.log.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719735/+files/nvidia-installer.log.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification
apport information
** Tags added: apport-collected
** Description changed:
I installed a fresh Ubuntu 10.10 and installed the proprietary driver
(nvidia-current) suggested by the system.
Upon reboot it fails while starting GDM, leaving me with a blinking cursor in
tty7.
I'm able to
apport information
** Attachment added: .proc.driver.nvidia.registry.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719715/+files/.proc.driver.nvidia.registry.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug
apport information
** Attachment added: peripherals.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719736/+files/peripherals.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member
apport information
** Attachment added: glxinfo.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719734/+files/glxinfo.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: setxkbmap.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719737/+files/setxkbmap.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: xdpyinfo.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719738/+files/xdpyinfo.txt
--
Nvidia proprietary driver unable to initialize
https://bugs.launchpad.net/bugs/669253
You received this bug notification because you are a member of
apport information
** Attachment added: xkbcomp.txt
https://bugs.edge.launchpad.net/bugs/669253/+attachment/1719739/+files/xkbcomp.txt
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Incomplete = New
--
Nvidia proprietary driver unable to initialize
I've tested latest kernels 33 through 36 from the link above and the
middle button _works_ on all of them!
--
Button 2 (middle) on touchpad works as button 1 (left)
https://bugs.launchpad.net/bugs/666968
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Well personally I've found a fix for this issue, ditched Netbook Remix
theme and just did a clean install of Ubuntu Desktop.
From my experience, as I remember having the narrow display on second
monitor with Netbook Remix and saw it again after reinstalling Desktop,
I think default installs of
*** This bug is a duplicate of bug 635362 ***
https://bugs.launchpad.net/bugs/635362
Daniel, please take a look at /etc/X11/xorg.conf (if you have that file).
I've had the same error message after I upgraded from Kubuntu 10.04 to 10.10
(with updates) yesterday.
After many hours trying bring
II've had the same error message after I upgraded from Kubuntu 10.04 to 10.10
(with updates) yesterday. My PC has two Radeon cards (RV350 and RV370).
After many hours trying bring my system to live I've found that in my case the
cause of problem was:
Load v4l
option in Module section of this
Problem solved as per your instruction of No Sploash
David LaButte
--
Cannot boot from hard drive
https://bugs.launchpad.net/bugs/595352
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
II've had the same error message after I upgraded from Kubuntu 10.04 to 10.10
(with updates) yesterday. My PC has two Radeon cards (RV350 and RV370).
After many hours trying bring my system to live I've found that in my case the
cause of problem was:
Load v4l
option in Module section of this
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Xorg crashes on suspend
https://bugs.launchpad.net/bugs/659405
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) = (unassigned)
--
System unusable after resume from suspend or hibernate [i945]
https://bugs.launchpad.net/bugs/133677
You received this bug notification because you are a member of Ubuntu-X,
which is
1 - 100 of 144 matches
Mail list logo
