Public bug reported:
I have a server machine with an ASPEED BMC (kernel driver `ast`) and a
Radeon Pro WX 4100 (driver `amdgpu`). If I try to log into a KDE
Wayland session or a Gnome Wayland session, it crashes back to the login
screen, with the same innermost level in the traceback.
What I'd
I've been having crashes with the same assertion message, when trying to
run Windows 10 ARM under a VM. But I finally figured out that what's
actually crashing it is not the fact that it's Windows, it's the fact
that I was attaching the virtual drive via virtual USB.
If I do the same thing to an
Same for me: I can use xrandr manually in an Xorg session, but not in
the Wayland sesson.
>From some stuff I read online, it seems like Gnome is trying to prevent
you from making the virtual resolution too low, but if it's already too
low, now you're stuck like that, and it really ought to be up
I managed to add the U7 Echelon to the config file:
"Xonar U7 Echelon Ed_" 1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498129
Title:
Asus Xonar U7 S/PDIF output not recognized by pulseaudio
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537336
Title:
deluged crashed with SIGSEGV (error 4 in _rencode.x86_64-linux-gnu.so)
To manage
I have an Ubuntu 15.10 that's up to date, and I'm still seeing the
"rejected" message.
The seemingly most relevant file is
/etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf, from the
network-manager config file. None of the rules in that file seem to
handle all the "(unset)" fields.
**
I have an Ubuntu 15.10 that's up to date, and I'm still seeing the
"rejected" message.
The seemingly most relevant file is
/etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf, from the
network-manager config file. None of the rules in that file seem to
handle all the "(unset)" fields.
**
** Bug watch added: GNOME Bug Tracker #757714
https://bugzilla.gnome.org/show_bug.cgi?id=757714
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=757714
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I've enabled XDMCP in GDM, and created an xinetd service for VNC via
XDMCP.
Any time I try to connect via VNC, gdm crashes, taking down the local display
as well.
After that, gdm won't start again until I kill the "orphaned" local display.
It looks like the fix is a
** Summary changed:
- Connecting to GDM via XDMCP crashes it
+ Connecting to GDM via XDMCP crashes it (GdmXdmcpDisplay shouldn't be abstract)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525435
More specifically, the critical file from ubuntu-gnome-default-settings is:
/usr/share/glib-2.0/schemas/20_ubuntu-gnome-default-settings.gschema.override
If you remove that file and update schemas (one way is "dpkg-reconfigure
libglib2.0-0"), gdm won't start properly.
If you re-add the file and
Hmm, I've gone on to use git qemu and newer OVMF, and I'm running into
various other hangs that are not necessarily the same. Feel free to
place this bug back in its previous status; I've unmarked affects me
too for now.
--
You received this bug notification because you are a member of Ubuntu
Hmm, I've gone on to use git qemu and newer OVMF, and I'm running into
various other hangs that are not necessarily the same. Feel free to
place this bug back in its previous status; I've unmarked affects me
too for now.
--
You received this bug notification because you are a member of Ubuntu
Er, I mean, I'm using 3.13-rc5 plus Trusty packages on Saucy.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1266746
Title:
x86_64: Fails to start using EFI firmware
To manage
I can confirm this, though in my case, I'm using 3.13-rc5 kernel plus
Trusty's qemu-related packages.
The following command works (though gives no isa-debugcon output):
qemu-system-x86_64 -M pc -m 5120 -boot menu=on -monitor stdio -chardev
stdio,id=seabios -device
I can confirm this, though in my case, I'm using 3.13-rc5 kernel plus
Trusty's qemu-related packages.
The following command works (though gives no isa-debugcon output):
qemu-system-x86_64 -M pc -m 5120 -boot menu=on -monitor stdio -chardev
stdio,id=seabios -device
Er, I mean, I'm using 3.13-rc5 plus Trusty packages on Saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1266746
Title:
x86_64: Fails to start using EFI firmware
To manage notifications about
On my workplace Thinkpad W530 (Quadro K1000M in discrete-only mode),
EnableBrightnessControl=1 does in fact expose a working Backlight property
via xrandr.
Unfortunately, Gnome is looking for a property called BACKLIGHT, and falls
back to /sys/class/backlight when it's not found.
See
*** This bug is a duplicate of bug 947748 ***
https://bugs.launchpad.net/bugs/947748
In my case, I'm using an nvidia card on a Thinkpad, with
EnableBrightnessControl set.
On at least the Intel driver, xrandr --verbose presents both 'BACKLIGHT' and
'Backlight'.
The nvidia driver (with
** This bug is no longer a duplicate of bug 947748
Brightness control not working after latest update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947919
Title:
Can't change brightness with
This bug is still around even in 13.04. I'd imagine psmouse.c needs
code added to detect the Synaptics TouchStyk.
(I couldn't find the TouchStyk interfacing guide that Synaptics'
TouchPad interfacing guide refers to, so I can't say what that code
would need to be.)
** Changed in: linux (Ubuntu)
I'm still affected on byobu 5.21 in Ubuntu Quantal.
Looks like there's a duplicate here, as well:
https://bugs.launchpad.net/byobu/+bug/1045070
My observation:
Byobu uses prefix instead of escape -- see anything wrong in
/usr/bin/byobu-ctrl-a?
Line 35: [ $BYOBU_BACKEND = tmux ]
In a way, this can actually be a data-loss bug!
I installed Ubuntu once using manual partitioning (due to os-prober not
detecting Windows 8).
When I went back to install it again Erase Ubuntu 12.10 (to enable
LUKS this time), it wiped out EVERYTHING on the drive, including Windows
8!
gaah, accidentally clicked remove duplicate button, and it took effect
without confirmation.
** This bug is no longer a duplicate of private bug 1043892
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Check /usr/bin/byobu-ctrl-a, line 40:
grep -qs ^escape $keybindings bind_to=emacs
With byobu-tmux, the option is not called escape at all.
Therefore, it thinks I haven't configured the escape key, and any answer
proceeds to trample all over my working manually-edited configuration.
(I had to
** Information type changed from Private to Private Security
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1116999
Title:
xfreerdp
Same here... crash on most shutdowns.
I'm attaching a full stacktrace, grabbed via amtterm.
Note that I do have an out-of-memory kill due to Dropbox earlier, but I'd
imagine that's a red herring. That out-of-memory didn't kill Xorg.
fglrx issue is at the END of the log file... after that
** Description changed:
- I'm testing out the git version of the fujitsu-tablet driver from here, and X
is crashing when I hit something with the rightmost two buttons (one marked
fn, another marked alt.
+ I'm testing out the git version of the fujitsu-tablet driver from the
following page,
This is not a duplicate.
Unity isn't blocking... unity... from receiving keypresses; in fact, it's quite
the opposite: one plugin SHOULD be blocking the other from firing once it's
claimed the input event.
** This bug is no longer a duplicate of bug 704231
Unity blocks other programs from
I can confirm that it seems to be ConsoleKit killing the session, because it's
taking out both DRI and audio.
This bug should probably renamed -- it's not merely an i915 issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Dash shows if you press another super combo quickly
+ Dash shows if you press ANY super combo quickly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871084
Title:
Dash shows
Public bug reported:
The default for the new switcher is alt-tab, but I wanted to reassign it to
super. When I did so, I found the following issue:
Any time you press a super combo quickly, the other combo will fire but the
dash will still show.
Bind start switcher to super+tab... super-tab
I can confirm: this issue still applies in Ubuntu Natty (64-bit here).
In my case, the song is removed from my library only until I restart Rhythmbox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: rhythmbox (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/677042
Title:
rhythmbox removes song from library when external visualization is
*** This bug is a duplicate of bug 329012 ***
https://bugs.launchpad.net/bugs/329012
** This bug has been marked a duplicate of bug 329012
Add ipmisensors module to ubuntu kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 329012 ***
https://bugs.launchpad.net/bugs/329012
Public bug reported:
This will be a duplicate of another bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/329012
Here's the project's home page:
http://bmcsensors-26.sourceforge.net/
My Microserver
I've added my own apport-collect, and marked it a duplicate myself.
This should probably be wishlist priority.
(somewhat off-topic: I'm also wondering: why doesn't the author try to
get his patches into mainline?)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/329012
Title:
Add ipmisensors module to ubuntu kernel
To manage notifications about this
This issue (wishlist) is still present in Natty.
For example, my HP Microserver offers only a subset of its sensors through
lm_sensors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/329012
Title:
This is still true with the Radeon driver in Natty. There's no
BACKLIGHT property exposed on the LVDS interface.
Gnome Power Manager itself now works around it, with gnome-backlight-helper.
KDE also now somehow works around it, as well.
So, the user-facing portion is fixed, but the original
To be clear: this bug is not about getting multi-finger support on touchpads
that already claim to support it, but were not working properly.
This bug is also not about using width-based emulation to get fake multi-finger
detection.
This bug report is about sniffing out what, precisely, that
I'm having similar issues with my Turtle Beach Audio Advantage SRM (based on
CM106).
Here's a cheap one on Newegg:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/513634
Notably, the device itself is buggy. With Windows 7 default drivers, it
claims only 7.1 channel support. No
Related bug report (same buggy device, different symptoms):
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/535453
I'll also post the comments there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Cross-post from another bug report about the same buggy hardware:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/535453
I'm having similar issues with my Turtle Beach Audio Advantage SRM (based on
CM106).
Here's a cheap one on Newegg:
er, that link was this report. Here's the other report:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/535476
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/535453
Title:
USB-Audio
Public bug reported:
Binary package hint: ubiquity
I just had the Ubuntu Natty installer completly wipe out my Windows
install.
I chose the option to Erase Natty and install 11.04. It gave no
confirmation of exactly what it was going to do to the partitions. I
clicked okay to erase Natty, and
** Description changed:
Binary package hint: ubiquity
I just had the Ubuntu Natty installer completly wipe out my Windows
install.
I chose the option to Erase Natty and install 11.04. It gave no
- confirmation of exactly what partitions it was going to act on. I
+ confirmation of
** This bug is no longer a duplicate of bug 554980
Two finger scroll not working on all old touchPads (emulation approach).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/546697
Title:
enable
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
--
ubuntu-bugs mailing list
Now, why is this other bug, that's talking about getting REAL multitouch
on older touchpads, a duplicate of this bug?
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/546697
If we could get real multi-finger, why should we spend any time getting
FAKE multi-finger?
--
er, we CAN get it... if somebody sniffs out what that Windows driver
does to the touchpad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554980
Title:
Two finger scroll not working on all old
I hope that external attribute can be generalized to more hardware,
such as Silicon Image SATA controllers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/153768
Title:
External SATA (eSATA)
The same is true of my HP EliteBook 8530w: the scroll area is literally
only 5mm wide, and the raised border around the touchpad pushes the
center of my finger outside that tiny area.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'd appreciate it if somebody would figure out the initialization
sequence for that magic driver mentioned in bug 546697 ... there's
absolutely zero activity there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 554980 ***
https://bugs.launchpad.net/bugs/554980
Why does nobody believe that it could EVER be possible for a driver to patch
the firmware?
I've said it before, and I'll say it again: that special driver IS NOT FREAKING
EMULATION. IT IS REAL
*** This bug is a duplicate of bug 554980 ***
https://bugs.launchpad.net/bugs/554980
And before you go saying it IS emulation, try what I described in the
post above, in the debug window, on a real multi-finger touchpad. Then
try it on a non-multifinger touchpad with an ordinary driver.
Another use case for having both: I have both a built-in, single-finger-
except-with-special-windows-driver* touchpad, and a Magic Trackpad. So
I get either edge scrolling on both, or 2-finger on the latter and no
scrolling at all on the former.
*
On my laptop, the keys that are handled by the hp_wmi give no scancodes
at all -- they're hardcoded to specific, too-high keycodes such as
KEY_INFO! You have to edit the module source to change them.
Some of the other keys' mappings are handled by udev, though. If the
keymap creators, as shown
Some new information: I had a chance to try Ubuntu on a laptop that has
ONLY the stick (HP Compaq 2710p), and even on that computer with no
touchpad, I still see the stick as PS/2 Generic Mouse.
--
Cannot configure Synaptics TouchStyk settings (e.g. sensitivity, tapping,
press/select)
Would you mind doing the same sniffing for that special driver I linked
to? That driver really does enable multi-finger detection on touchpads
that have never supported it before, even in Windows!
--
Multitouch support not available for Synaptics touchpads v7.2
No, I am quite absolutely sure that that IS enabling real multi-finger
detection read the comments! It seems to be patching the firmware
of the touchpad, somehow.
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/308191
You received this bug
No, I am quite absolutely sure that that IS enabling real multi-finger
detection read the comments! It seems to be patching the firmware
of the touchpad, somehow.
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/308191
You received this bug
Anyway, that's not the main issue being discussed on this bug... it's just that
the technique you used would be useful for that, too:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/546697
--
Multitouch support not available for Synaptics touchpads v7.2
This is not a duplicate! The parent bug is about touchpads that already
had multi-finger capabilities in Windows; this bug is about using a hack
to get multi-finger capabilities on ALL touchpads.
Just in case anyone thinks the driver is only doing emulation, try this
in Windows: go to Mouse
new bug... there's this one I just linked to above!
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/546697
And with that, I am done with this thread here.
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/308191
You
You should try this with a Tablet PC's pen. It's quite literally
impossible to click on any of the icons -- absolutely every time I try
to click, it drags instead.
It might also be good to tweak the title of this bug -- I searched for
move and click and drag (each separately), and only managed
Issue still occurs with 2.6.35 kernel in Maverick.
New information:
Apparently the old GuestMouse feature has been removed:
http://www.mail-archive.com/xorg-de...@lists.x.org/msg03793.html
Also, NetBSD has an interesting kernel patch:
See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/612591
It looks like the ClickPad support is to blame... it treats the middle button
as a left or a right, depending on where your finger is.
--
[Maverick] Middle buttons do the same as left buttons
** Summary changed:
- [Maverick] Kernel treats 3-button touchpad as 1-button ClickPad
+ Maverick kernel treats touchpad's middle button as ClickPad
** Description changed:
- This seems to be the inverse of bug 582809 (Clickpad buttons Not
+ This seems to be the inverse of bug 582809 (ClickPad
Cool now we just need to do that with THIS driver, and we'll get
multi-finger on ALL Synaptics touchpads:
http://www.engadget.com/2010/03/19/synaptics-driver-enables-multitouch-gestures-on-older-trackpads/
--
Multitouch support not available for Synaptics touchpads v7.2
This other driver is not emulation -- it adds native multitouch to ANY
touchpad, even ones that didn't originally do multitouch even in
Windows! We just need to sniff out the initialization sequence -- it
seems to be patching the firmware on the fly.
--
Multitouch support not available for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625?comments=all
-- that bug has info on how to trace PS/2 activity via VirtualBox.
Hopefully, it'll be enough to just do that trace with the unlocking
driver.
--
enable multitouch support on older touchpads, as supported by driver
** Description changed:
Binary package hint: grub2
As discussed here, when booting with grub-efi-amd64, the system fails to
find the initramfs image:
http://www.mail-archive.com/bug-g...@gnu.org/msg12623.html
It looks like the experimental branch of Grub makes this booting
** Description changed:
Binary package hint: grub2
As discussed here, when booting with grub-efi-amd64, the system fails to
find the initramfs image:
http://www.mail-archive.com/bug-g...@gnu.org/msg12623.html
It looks like the experimental branch of Grub makes this booting
Hmm, I seem to have the exact opposite problem: it detects a non-
ClickPad touchpad as a ClickPad, and thus breaks both my ability to use
my real middle button, and my ability to click and drag with the left
button.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/612591
--
TouchPad buttons
I managed to get the dkms version to install by first uninstalling it:
sudo dkms uninstall -m ndiswrapper -v 1.56
and then reinstalling it with --force:
sudo dkms install --force -m ndiswrapper -v 1.56
The PPA version fixes both the oops and the panic.
--
ndiswrapper can scan for SSIDs but
Architecture: i386
DistroRelease: Ubuntu 10.10
EcryptfsInUse: Yes
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N130
Package:
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541573/+files/BootDmesg.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541574/+files/CurrentDmesg.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541575/+files/Dependencies.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: DevkitPower.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541576/+files/DevkitPower.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: GConfNonDefault.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541577/+files/GConfNonDefault.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541578/+files/Lspci.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if I only
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541579/+files/Lsusb.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if I only
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541580/+files/ProcCpuinfo.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541581/+files/ProcInterrupts.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541582/+files/ProcModules.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541583/+files/UdevDb.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if I
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541584/+files/UdevLog.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if I
apport information
** Attachment added: gnome-power-bugreport.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541585/+files/gnome-power-bugreport.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator
Hmm, not only am I getting failure to connect, I'm also getting an oops
on module load, and a panic on module unload.
** Attachment added: Netconsole log of kernel panic.
https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/613796/+attachment/1538703/+files/ndiswrapper-panic.log
--
Oh, I suppose I should say: that's with kernel-ppa 2.6.35.4 on Samsung
N130 (Atom netbook).
Wireless card is rtl8192e, and needs ndiswrapper because r8192e_pci
merely gives Initialization is failed (complete with Engrish).
--
ndiswrapper can scan for SSIDs but cannot connect on any kernel newer
I can confirm this. When I leave the netbook idle, the brightness
control starts spazzing out, flickering back and forth between two
brightness levels, and eating 100% of one CPU core (at least if notify-
osd is running). On the login screen (no notify-osd), it happens fast
enough that it may be
This same BadAtom also happens for me with the open-source Radeon driver, yet
does not happen with the binary driver.
It looks like the problem most likely lies in the fallback brightness-control
methods used when the xrandr backlight property is not supported.
Note that fglrx supports
Rather, it's a side effect of the patch that FIXES bug 582809 .
--
[Maverick] Kernel treats 3-button touchpad as 1-button ClickPad
https://bugs.launchpad.net/bugs/612591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Unfortunately, this very same patch that fixes the ClickPad breaks my
3-button touchpad -- see bug 612591 .
--
Synaptics Clickpad touchpad buttons are not working
https://bugs.launchpad.net/bugs/582809
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: efi
--
UEFI boot needs Experimental branch of Grub
https://bugs.launchpad.net/bugs/612432
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
This seems to be the inverse of bug 582809 (Clickpad buttons Not
working).
The Maverick kernel treats my 3-button touchpad as if it were a ClickPad
-- and thus treats the middle button as if it were another left button.
In dmesg, I see ClickPad Mode Enabled. This bug is a
** Attachment added: AcpiTables.txt
http://launchpadlibrarian.net/52866309/AcpiTables.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52866310/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52866311/AplayDevices.txt
**
I disagree. Just because something is consistent, that doesn't mean it
is sensible or intuitive.
That may be true, but it's far more likely to find something
INconsistent, confusing and counter-intuitive.
I would likely find it impossible to adapt to your desired behavior.
Every device I've
1 - 100 of 319 matches
Mail list logo
