Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
I'd like to be able to disable the mouse buttons on the touchpad, and
use tap-to-click instead.
xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Click
Action" 8 0 0 0
Did not work; it changed the property, but the
On Fri, 2009-07-17 at 14:49 +, Alberto Milone wrote:
> Something like the following solves the problem: xinput set-button-map
> $YOUR_TOUCHPAD 12 12 12 4 5 6 7 8 9 10 11 12
>
As noted, it doesn't because it breaks tap-to-click
Scott
--
Scott James Remnant
sc...@canonical.c
** Package changed: udev (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)
--
trackpad driver on Asus Eee 701 doesn't accept tap as click
https://bugs.launchpad.net/bugs/413880
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synap
** Description changed:
Nouveau blacklisting fails when /usr is on seperate partition.
cat /etc/modprobe.d/nvidia-graphics-drivers.conf
blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-173
blacklist nvidia-96
alias nvidia nvidia-current
File exists as above and 'updat
If you see mouse pointers, this is not an upstart problem but an X
server issue
** Package changed: upstart (Ubuntu) => xorg-server (Ubuntu)
--
Lucid frequently crashes while starting gdm on Averatec 3280
https://bugs.launchpad.net/bugs/508456
You received this bug notification because you are a
udev does not (and will not ever) enforce module loading orders. The
kernel may do that by dependencies between modules, or other packages
can use blacklists to prevent one from being loaded, etc.
** Package changed: udev (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
--
Radeon 9250 no 3D.
https:/
We shouldn't modprobe like this at all. udev will load that module
automatically anyway (and load the right ATI one instead if they don't
have i915)
my post-α6 usplash changes should address this
--
initramfs scripts hard-coded to load i915; blocks loading non-intel drm modules
https://bugs.laun
Rick, did you intend to steal this bug? I've already said that I'm
working on this
--
initramfs scripts hard-coded to load i915; blocks loading non-intel drm modules
https://bugs.launchpad.net/bugs/392039
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
Things found out so far:
1. The mystery of what loads the fbcon driver on i915 systems without
cryptsetup has been solved, the intel Xorg driver hardcodes a "modprobe
fbcon" into it
2. The fbcon driver needs to be loaded when you have a framebuffer, but
can't just be a "depends" of the modules
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Also affects: usplash (Ubuntu)
Importance: Undecided
Status: New
--
initramfs scripts hard-coded to load i915; blocks loading non-intel drm modules
https://bugs.launchpad.net/bugs/392039
You received this bug
Solved unsolved things:
- have the framebuffer script still handle vga=* video=*, and if
neither are specified have it check for a udev-loaded driver and
otherwise load vesafb
- then we can just load usplash from a hook as before
--
initramfs scripts hard-coded to load i915; blocks loading no
Does X fail to start, or is GDM not started? They would be quite
different bugs
If you login to a console and type "status gdm" what do you see?
Are there any boot messages?
Do you see X try and start, does it fail?
** Changed in: xorg (Ubuntu)
Status: Confirmed => Incomplete
--
X/GDM
mic)
Assignee: Scott James Remnant (scott) => Canonical Desktop Team
(canonical-desktop-team)
--
Karmic Alpha 6 will not boot from Live CD
https://bugs.launchpad.net/bugs/432176
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Reading the further comments, this appears to be describing a regression
with support for ATI graphics hardware from Alpha 5 onwards
--
Karmic Alpha 6 will not boot from Live CD
https://bugs.launchpad.net/bugs/432176
You received this bug notification because you are a member of Ubuntu-X,
which i
What's this got to do with Upstart?
Why *should* X be able to tcflush() ?
** Changed in: upstart (Ubuntu Karmic)
Status: New => Invalid
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you ar
fix the kernel bug too, but this at least
> keeps the idle wakeup count below 1000/sec.
>
But what is meant here by "the console" ?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
Yo
Still nothing to do with Upstart.
I would like to know *what* X is doing with that tcflush() and why it is
apparently unable to cope with it returning an error. What is that
trying to access, why isn't there a graceful fallback for it not
existing, etc.
Let's figure this out, rather than just tr
On Tue, 2009-10-06 at 18:31 +, Rob van Vliet wrote:
> The kdm fix from jsiebold works also for gdm (/etc/init/gdm.conf)
>
This fix is wrong.
Just so you know.
Let's work out what the real fix should be.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[karmic] Xorg 100% CPU
** Package changed: udev (Ubuntu) => xorg (Ubuntu)
--
Super user key shortcut does not work (=get captured) when you try to use it in
System --> Preferences --> Keyboard Shortcuts
https://bugs.launchpad.net/bugs/483113
You received this bug notification because you are a member of Ubuntu-X,
whic
** Package changed: udev (Ubuntu) => xorg (Ubuntu)
--
lenovo-sl-laptop: Hotkeys for volume control doesn't work if there is an open
right-mouse-click-menu
https://bugs.launchpad.net/bugs/485522
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg i
** Package changed: upstart (Ubuntu) => xorg (Ubuntu)
--
upstart failsafe incorrect screen resolution when running with 2.6.31 kernerls
https://bugs.launchpad.net/bugs/492270
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
_
It sounds like X is being started, so...
** Package changed: upstart (Ubuntu) => xorg (Ubuntu)
--
Karmic livecd problem
https://bugs.launchpad.net/bugs/458804
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
--
Plymouth garbles screen (ATI 200M)
https://bugs.launchpad.net/bugs/519891
You received this bug notification because you are a member of Ubuntu-X,
which
On Sun, 2010-03-14 at 16:22 +, Claudio Moretti wrote:
> Still experiencing it:
>
Could you provide "cat /proc/fb" output for me, and confirm whether you
see an Ubuntu logo during boot, or the words "Ubuntu 10.04" in text
Scott
--
Scott James Remnant
sc...@ubuntu.c
disables.
>
>From the sounds of it, Plymouth is actually working great with KMS
disabled (other than the spam of console messages over the top) - and
it's the X server that screws things up when it kicks in.
You'll want to file a bug on the non-KMS X driver, almost certainly.
Thank
On Mon, 2010-03-15 at 01:59 +, Marc A. Donges wrote:
> This problem still exists for me with current versions of lucid:
>
Could you describe the problem you're seeing?
Does plymouth show a graphical logo or do you see "Ubuntu 10.04" written
in text?
Scott
--
S
ooks like as good a place as any to discuss the X issues
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Plymouth garbles screen (ATI 200M)
https://bugs.launchpad.net/bugs/519891
You received this bug notification because you are a member of Ubuntu-X,
whi
On Mon, 2010-03-15 at 14:03 +, Henning Schröder wrote:
> Still experiencing it, too. I have the text boot splash, not the graphical
> logo one.
>
Thanks. This is bug #538213 - which is specifically about the text boot
splash
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Public bug reported:
Binary package hint: xserver-xorg-video-nouveau
Nothing useful is displayed on screen in graphics mode with this laptop,
instead it seems like random data pixels and colours end up on the
panel.
With nouveau.modeset=0, you get an X server and everything, just at the
wrong re
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/41045182/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/41045183/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41045184/Dependencies.txt
** A
** Attachment added: "Picture of screen when X is running"
http://launchpadlibrarian.net/41045449/photo.jpg
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you
I don't think X is hung at all; here's the ps output, everything looks
normal
And here's what X is doing:
r...@mario:~# cat /proc/1000/wchan
poll_schedule_timeout
** Attachment added: "ps output while in that state"
http://launchpadlibrarian.net/41045660/ps.log
--
[G72M] Screen corruption
Here's a photo of what plymouth renders to the framebuffer. This is
supposed to be the ubuntu logo mid-way on a purple screen.
Odd how the explosion of white (which could be the logo) is rotated 90
degrees, then offset midway "up" the screen.
If you applied the same logic to the other photo, the
Bryce asked for the xrandr --verbose output while in -vesa
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 (0x108) normal (normal) 0mm x 0mm
Identifier: 0x107
Timestamp: 15051
Subpixel: unknown
Clones:
This is ssh'd in while the corruption is on screen - not sure if that's
right or not
r...@mario:~# DISPLAY=:0 get-edid | parse-edid
get-edid: get-edid version 2.0.0
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
parse-edid: parse-edid version 2.0.0
Fu
Confirming that switching from the -generic-pae kernel to just -generic
makes no difference
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification because you are a member of Ubun
r...@mario:~# cat /sys/class/drm//card0-LVDS-1/modes
1440x900
1152x864
1024x768
800x600
640x480
720x400
640x400
640x350
r...@mario:~# cat /sys/class/drm//card0-LVDS-1/status
connected
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs
r...@mario:~# parse-edid < /sys/class/drm//card0-LVDS-1/edid
parse-edid: parse-edid version 2.0.0
parse-edid: EDID checksum passed.
# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:fe
# Block type: 2:0 3:fe
Identifier "LPL:e000"
VendorName "
airlied suggested dmesg from a boot with modeset=1 would be useful, here
it is
** Attachment added: "dmesg from boot with mode setting"
http://launchpadlibrarian.net/41056030/dmesg.log
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://b
dmesg without vga16fb joining the party
** Attachment added: "demsg"
http://launchpadlibrarian.net/41056521/dmesg.log
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification be
The gradual whiting out means that the LVDS isn't being driven correctly
Might be worth dumping your video bios as well
He may want the scripts
dd if=/dev/mem of=video.bios bs=65536 count=1 skip=12
** Attachment added: "video.bios"
http://launchpadlibrarian.net/41058076/video.bios
--
[G72
mmiotrace of nvidia-glx
** Attachment added: "nvidia-glx_trace"
http://launchpadlibrarian.net/41072914/nvidia-glx_trace
--
[G72M] Screen corruption when using KMS. Dell Latitude D620 / Quadro NVS
110M/GeForce Go 7300
https://bugs.launchpad.net/bugs/539730
You received this bug notification
Ok, this is definitely not a plymouth issue then. I'm going to reassign
to the X server for now
** Package changed: plymouth (Ubuntu) => xorg-server (Ubuntu)
--
System Freeze/Pause waiting for something
https://bugs.launchpad.net/bugs/539507
You received this bug notification because you are a
On Tue, 2010-03-16 at 20:22 +, Marc A. Donges wrote:
> On Monday, March 15, 2010 at 13:02:30 (-), Scott James Remnant wrote:
> > On Mon, 2010-03-15 at 01:59 +, Marc A. Donges wrote:
> >
> > > This problem still exists for me with current versions of luc
On Wed, 2010-03-17 at 12:26 +, Ivan Katanović wrote:
> System with vesa loaded. The laptop is Acer Extensa 5635G with Nvidia G 105M.
>
Since the card isn't identical, this may be a different bug with the
same symptoms
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
[G
On Wed, 2010-03-17 at 18:39 +, Jeff Lane wrote:
> I am seeing this after installing from today's alternate ISO build...
>
Do you have cryptsetup installed?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Plymouth text-mode splash causes X to crash on first run due to shared
On Fri, 2010-03-19 at 14:14 +, AlainKnaff wrote:
> The full lspci id of the card is:
> 02:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 220]
> (rev a2)
>
You have a different card, so you have a different bug.
Scott
--
Scott James Remnant
sc...@ubuntu.co
Plymouth isn't relevant here, all you're doing there is changing boot
timings, etc.
This is still a driver issue
--
nvidia driver sometime does not load at boot
https://bugs.launchpad.net/bugs/532436
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Moving to the Ubuntu bug tracker.
Note that the proprietary nvidia X drivers load the associated module
themselves, so there's no chance of a race here
** Project changed: upstart => null
** Changed in: null
Status: New => Invalid
** Also affects: linux-restricted-modules-2.6.24 (Ubuntu)
49 matches
Mail list logo
