One more observation. When using the driver my glidepoint (DualPoint
Stick) lacks sensitivity. It's perfectly sensitive without the driver.
When moving at longer distances the mouse cursor behaves pretty much the
same way like before - it seems it's less sensitive, but it does not
actually matter.
KDE Network Management plasmoid does not see any network interfaces
since the upgrade to NM 0.9.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791548
Title:
Oneiric: Never sees NetworkManager
Suspend/resume issue:
E6410 (maybe E6510 as well) has a BIOS bug which causes system freeze when
resuming on battery power.
More info here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665891/comments/7
Tap to click disable:
I have successfuly disabled tap to click, I am running
After a lot of time wasted with Dell support this is my current experience:
1) issue only appears when the laptop is powered on battery
2) this issue disappears when Speed Step is disabled in BIOS (which disables
Turbo Boost as well)
3) this issue is mostly visible on i7 620M 2.66 CPUs; much less
** Summary changed:
- Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7
+ Dell Latitude E6410: System freeze on S3 resume with Intel Core i7 CPUs
(affects any OS)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Remember to call sudo update-grub after making modifications in
/etc/default/grub. The update-grub script assures that
/boot/grub/grub.cfg is updated with the new information. I assume
you're using GRUB2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Jim, does you E6410 resume from suspend reliably like this even when
unplugged from AC power? E6410 of mine systematically freezes on second
or third resume when running on batteries only. When it runs on AC
adapter, resume is always reliable. I am not using Hibernate because of
not willing to
Latham:
Do you really have an nVidia NVS GPU in your machine? If not, don't read
further and acpi_sleep=nonvs is not for you anyway. Also don't continue
reading unless you're familiar with GRUB boot menu and reverting to stock
kernel if something bad happens.
For Linux kernels above 2.6.35
Gaby: no such problem here with spontaneous resume from suspend. Could
it be a Wake-On-LAN packet that is waking-up your laptop?
Jim: What's exactly your CPU Core i7 model? I tested different DDR3 RAM
sizes from two distinct vendors, no difference. My CPU is Core i7-620 @
2.66 GHz which seems
I think the problems you are encountering are very different. The
problem for which I originally started this bug report was finally
identified as BIOS problem of Dell Latitude E6410 with nVidia GPU and
Core i7 2.66GHz CPU (probably concerns E6510 series with same specs
too) laptops up to A05
Jame Krug: i bet you must have a Dell Latitude E6410 with nVidia and
Intel Core i7 2.66GHz. Maybe the GPU does not matter. I spend over 3
weeks analysing the problem. The result is evident: it's not about
Ubuntu (in Windows, yes being desperate I installed Win7 on a different
HDD to test out,
Oh, SerP6? I just thougt it's kind of typo, when I realized it is a
laptop model, sorry. Anyway it still may be interesting, especially
knowing what kind of CPU and GPU you have. Anyway it's not Dell or
Serval who manufactures BIOSes; they assemble and package them based
on components from their
Oswald, the problem about which I am writing essays here seems to be very
different from anyone elses problem like I realized today.
I suppose the workaround proposed in comment #54 could fix it for you.
-
Being desperate because of trying virtually any possible Linux kernel tweaking,
various
Radko, your feedback is very appreciated. For 2.6.35 and older kernels
you need to apply acpi_sleep option into GRUB like this:
1) $ sudo nano /etc/default/grub
2) Search for GRUB_CMDLINE_LINUX= and make it look like
GRUB_CMDLINE_LINUX=acpi_sleep=nonvs
3) Save and run: $ sudo update-grub2
4)
It has proven incorrect assuming that the problem is caused by linux CPU power
management. With a special kernel, where cpufreq is modularized
(http://www.linux-phc.org/) i was able to completely remove cpufreq thus
finally nothing was managing CPU frequency scaling (P-states), I also disabled
Like i commented here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578673,
by using an experimental kernel which has cpufreq modularized I was able to
disable completely the CPU power management. Cpufreq module did not load (this
no frequency scaling) and C-states sticked to C0 all
I confirm that on Dell Latitude E6410 with nVidia card the GRUB option
acpi_sleep=nonvs resolves the resume issue on standard Maverick kernel
2.6.35-22-generic x86_64.
On kernels 2.6.36 this GRUB option isn't necessary and the machine
resumes very well.
There is one exception, valid for both
When setting GRUB option to acpi_sleep=nonvs described here:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/656279/comments/41
the black screen on resume is fixed on Maverick kernel 2.6.35. With 2.6.36
kernel this GRUB option isn't necessary.
In both cases resume on
Public bug reported:
System freezes on resume (sometimes on 2nd, 3rd... suspend/resume cycle). It
seems to be a race condition related to Intel Idle Driver. Using the boot GRUB
parameter intel_idle.max_cstate=0 which disables the new Intel Idle Driver
and assures fallback to ACPI idle, the
--
Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7
https://bugs.launchpad.net/bugs/665891
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
Apparently my resume problem on batteries is caused by kernel race
condition related to Intel Idle Driver. I filed a separate bug for this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665891
--
[arrandale] Resume doesn't work on a Latitude E6410
https://bugs.launchpad.net/bugs/578673
Update: after more suspend/resume cycles it turned out that Intel Idle
Driver is not to blame. Unless SpeedStep is disabled in BIOS the laptop
does not realiabily resume on battery power. Since SpeedStep is about
P-states rather than C-states; could someone write an experimental patch
which would
Sorry to comment on a fixed bug, but my problem seems to be closely
related. My system is Dell Latitude e6410 with Intel i7.
Resume from suspend to memory was not working for me on kernels prior
2.6.36. Since 2.6.36 it works flawlessly but only when resuming with AC
adapter plugged-in.
When
I think I identified the problem on my system Dell Latitude E6410 with Intel i7
CPU.
Disabling Intel SpeedStep feature in BIOS does the trick. Battery life decrease
seems insignificant thanks to power management assured by CPU C-states. What's
interesting that the CPU multiplier is still
Why marked as invalid? My testing (just using different kernels,
otherwise keeping the same configuration):
- Lucid Kernel 2.6.32-25 - OK
- Mainline 2.6.33 - K.O.
- Mainline 2.6.34 - K.O.
- Maverick 2.6.35 - K.O.
- Mainline since 2.6.36rc8 - OK*
- Natty 2.6.36-0 - OK*
* second resume (only when
I've got success with the latest 2.6.36 mainline kernel dev snapshot:
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-10-13-maverick/
(don't try the rc7 on any older snapshot - just this one worked)
Using the standard Maverick 10.10 x64 installation which includes nVidia
proprietary
You may wish to try the following fix which seems to work on Latitude
e6410 (not yet confirmed by anybody else than myself):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578673/comments/129
--
blank screen on resume (Dell XPS M1330)
https://bugs.launchpad.net/bugs/659458
You received
WARNING : I forgot to remind everyone that using pre-release kernels is
dangerous, using kernel daily snapshots IS VERY DANGEROUS and could lead
to data loss or any kind of irreversible damage to your system.
Users not willing to risk are advised to try the above method once the
final version of
In my case the problem is fixed. It was caused by nvidia proprietary drivers;
with version 260.19.06 this bug has disappeared.
xset dpms force suspend suspends the display, pressing any key or moving
mouse pointer wakes it up.
--
Screen locks up black on laptop lid close.
Your problem may be related to misdetection of Acer rfkill switch.
More info here: http://old.nabble.com/BCM4312-b43-acts-weird-with-
NetworkManager-and-F13-td29366991.html
Try blacklisting the acer_wmi kernel module.
--
nm-applet don't enable wireless automatically
*** This bug is a duplicate of bug 49521 ***
https://bugs.launchpad.net/bugs/49521
** This bug is no longer a duplicate of bug 44393
After closing the lid, video does not come back by pressing any key.
** This bug has been marked a duplicate of bug 49521
Screen locks up black on laptop
Same problem on Dell Latitude E6410 with running Maverick
2.6.35-22-generic; nVidia proprietary drivers 256.53. Tested with
2.6.36 RC kernels and PPA nVidia drivers (260.x series from x-swat) and
Xorg Edgers PPA too with same results.
Results of different scenarios:
1) $ xset dpms force off
-
*** This bug is a duplicate of bug 49521 ***
https://bugs.launchpad.net/bugs/49521
** This bug has been marked a duplicate of bug 49521
Screen locks up black on laptop lid close.
* You can subscribe to bug 49521 by following this link:
*** This bug is a duplicate of bug 49521 ***
https://bugs.launchpad.net/bugs/49521
** This bug has been marked a duplicate of bug 49521
Screen locks up black on laptop lid close.
* You can subscribe to bug 49521 by following this link:
The Dell patch has been reverted in 2.6.35-22.33. As a result Andrew's
patch applies cleanly again. It's already the period of kernel freeze
for Maverick so it's unlikely that Maverick would get the support out of
the box :/ Blame Alps for not willing to publish the new protocol
specifications.
raboof: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
maverick.git;a=commitdiff;h=bd79df42218fe1db5e683b567791d4bb97b60685
--
Alps touchpad is recognized but synaptics clients and scrolling do not work
https://bugs.launchpad.net/bugs/550625
You received this bug notification because you are a
Manoj Iyer from Canonical has recently introduced the original Dell
patch to the Maverick kernel 2.6.35-22. It means there exists the above
discussed issue with erratic mouse behaviour on resume. There are no
extra features implemented which were brought by Andrew to control
things like tapping
Attached psmouse.ko module based on latest patch by Andrew; this
version has tapping disabled via modified extra bits. I suppose mainly
GlidePoint users are negatively impacted by touchpad's hypersensitivity
(#147), so we'd better turn tapping off.
If this patch is going to go to the mainline
Andrew, your patch does not apply cleanly on Ubuntu Maverick kernel
2.6.35. As you wrote in #140 you had to modify the Dell patch, it was
not the case with 2.6.35 where it did apply cleanly right away. The
problem is in alps.c, especially alps_hw_init function which is
significantly different.
Possible workaround is to unload and reload the module on resume. In
Ubuntu create the following new file named e.g. 90-psmouse-reload in
/etc/pm/sleep.d/ with the following content:
#!/bin/sh
case $1 in
thaw|resume)
rmmod psmouse; modprobe psmouse
;;
esac
exit 0
However I still
I suppose most of people would agree a Latitude ON and all the other SplashTop
derivatives is a useless feature, purely a marketing thing. However since the
manufacturer does ship this feature in their flagship Laptops equipped with the
ALPS 0x73, 0x02, 0x64 touchpad, they're obliged to provide
You're mentioning Dells E6410, E6510 suffer from this problem too. Both
these models are equipped with the Instant ON feature which is AFAIK
Linux-kernel based (http://www.splashtop.com/)
If the touchpad scrolling does not work, I'd suggest to contact Dell and insist
on a rapid bugfix.
If it
raboof, you should have it. One can buy it with the image preloaded from
factory or flash it to the system from within the management SW for windows.
More info on this technology for Dell E-series is here:
http://latitude-on-flash.com
E6510 is listed here:
Perhaps it is an option depending on Latitude E-series HW configuration.
It is definitely Linux based.
--
Alps touchpad is recognized but synaptics clients and scrolling do not work
https://bugs.launchpad.net/bugs/550625
You received this bug notification because you are a member of Ubuntu
Bugs,
Manage Profiles - Profile - Connection specific - Cisco
In the bottom left there is a combo box named Cisco NAT mode with
possible choices natt, force-natt, cisco-udp, none.
Changes in this combo are neither saved nor used. Tested in KVpnc 0.9.2.
--
Cisco NAT mode setting ignored
I found out KVpn 0.9.3 was released in August 29 (it has not yet made
it into Karmic Koala)
The changelog confirms this bug has been resolved:
http://home.gna.org/kvpnc/en/changelog.html
* cisco nat mode saving fixed [kde4]
--
Cisco NAT mode setting ignored
Same issue with kmail on karmic x64, when accessing IMAP folders.
Appeared on upgrade to package version *ubuntu4. Downgrading kmail and
dependent packages to *ubuntu3 makes it stable again.
dpkg -i libkleo4_4%3a4.3.1-0ubuntu3_amd64.deb
libkdepim4_4%3a4.3.1-0ubuntu3_amd64.deb
Both Intrepid and Jaunty (so far) have the same kvpnc version bundled
0.9.0. I can retest when an update is released. Is this package included
in the list of KDE 4 migrations/rewrites?
--
Cisco NAT mode setting ignored
https://bugs.launchpad.net/bugs/206793
You received this bug notification
Perhaps a little bit irrelevant, but on my system the mouseemu package
caused a conflict which among other effects caused touchpad malfunction
after resume. I think this package is problematic since Hardy Heron,
kernels 2.6.26 up.
--
Synaptics touchpad ceases functioning after suspend and
Has been resolved in recent compiz releases (included in Hardy final),
which now correctly detects collision in the keyboard mapping, which by
default for Alt + RButton = context menu pop-up; this kind of collision
was previously unhandled and double mapping allowed, which resulted in
freezing.
Public bug reported:
Binary package hint: kvpnc
Cisco proprietary client setting Cisco NAT mode natt/force-natt/cisco-udp is
not saved thus not applied.
In the PCF file this is called TunnelingMode which is equal to 1 for cisco-udp
setting.
Unfortunately KVPNC proactively removes from the PCF
My problem is that until kernel 2.6.24-4 the integrated wireless card
Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
worked smoothly. Since update to 2.6.24-8, then 2.6.24-10, 2.6.24-11
still the same problem which is that wireless networks are visible, but
I cannot connect to
dmesg:
[ 1077.748844] wlan0: RX AssocResp from 00:18:f3:57:f5:3c (capab=0x411
status=18 aid=1)
[ 1077.748852] wlan0: AP denied association (code=18)
[ 1077.882494] wlan0: association with AP 00:18:f3:57:f5:3c timed out
[ 1092.535767] wlan0: RX deauthentication from 00:18:f3:57:f5:3c (reason=7)
[
Connecting to unsecured network passes to IP Configuration Stage, which
fails, but it could be caused by the fact that my MAC address is
rejected. Perhaps my bug could be reevaluted as WPA problem related to
upgrade to Ubuntu Hardy with kernel 2.6.24-8 and newer.
--
[Hardy]Recent kernel update
It seems that the bug I describe here is this one reported here:
https://bugs.launchpad.net/ubuntu/+bug/183619
--
[Hardy]Recent kernel update to 2.6.24-11 breaks b43 (with bcm4312)
https://bugs.launchpad.net/bugs/197959
You received this bug notification because you are a member of Ubuntu
Bugs,
Same problem here. No problem on 2.6.24-4, big problem on later kernels.
However I cannot connect to my WPA network with SSID not hidden.
--
[hardy] wlan0: AP denied association
https://bugs.launchpad.net/bugs/183619
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: lspci_vvnn_0.txt
http://launchpadlibrarian.net/11968371/lspci_vvnn_0.txt
--
Compiz freezes on window resize
https://bugs.launchpad.net/bugs/189644
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
The RALT warning is because I have my keyboard settings changed (by editing
/etc/X11/xkb/symbols/*) for typing intl. characters via RALT+something instead
of having to switch to alternate keyb. layouts all the time.
It should not matter.
p.s.: doing screen zoom in compiz via RALT+Button3 works
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/11968499/Xorg.0.log
--
Compiz freezes on window resize
https://bugs.launchpad.net/bugs/189644
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Sorry, in the PS it was meant to be: LALT + Button 3.I don't suspect
compiz from collisions with the extra keyboard mapping I've done on RALT
and which I've been using for 2 years without any problems in 3
different desktop managers - gnome/kdm/xfce. Anyway I try to revert the
mapping to the
As expected: using original unmodified Xorg keyboard mapping (US) both
ALTs left and right behave indentically - used together with the Button3
both of them cause compiz to freeze in few seconds after I start
resizing any window using this combination. Caret keeps flashing but
nothing on the
Public bug reported:
Resizing of windows in compiz works fine except from the situation when
the key/mouse binding is set do AltButton3 (right mouse button).
Once this combination is used the whole desktop freezes within few
seconds.
Other bindings work smoothly; e.g. AltSuperButton3 binding
Dell Latitude D820, Kubuntu Hardy 2.6.24-2-generic #1 SMP Thu Dec 20
17:58:55 GMT 2007 x86_64 GNU/Linux. Same problem.
The only really working workaround I found out to revive touchpad after
resume is to restart HAL:
sudo /etc/init.d/hal restart
Drawback: restarting HAL on this Ubuntu kernel
Funny since I have read incorrectly the post of Bepcyc and did the
contrary i.e. COMMENTED the line and thus disabled the double console
switch, it fixed the resume problem of the touchpad.
--
Synaptics touchpad ceases functioning after suspend and resume.
https://bugs.launchpad.net/bugs/59867
Bepcyc writes in his post:
http://ubuntuforums.org/showpost.php?p=2507395postcount=8
You need to uncomment the line
DOUBLE_CONSOLE_SWITCH=true
in file /etc/default/acpi-support
And this works! AFAIK DOUBLE_CONSOLE_SWITCH=true was needed e.g. for
some older nVidia card drivers to work
I feel like spamming this thread, however I tried to write this
workaround which could be easily applied even by newbies and which works
fine for me on Gutsy kernel 2.6.22-11 generic. Concretely it made the
0483:2016 SGS Thomson Microelectronics Fingerprint Reader work properly
on my Dell Latitude
Problem still found in latest Gutsy kernel: Linux hostname
2.6.22-11-generic #1 SMP Fri Sep 7 04:31:16 GMT 2007 x86_64 GNU/Linux
--
USB device detection problems in 2.6.20
https://bugs.launchpad.net/bugs/102659
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Oops, it seems to be evident the problem is not in kernel but in devices
which do not comply with the USB specification.
Workaround found here, as mentioned by Danilo Шеган :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/85488
Well, also Dell seems to be shipping such
After having carefully read the complete thread below and tested extensively
the proposed workaround I realized it did not work. Sorry for the confusion.
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/85488
--
USB device detection problems in 2.6.20
** Changed in: linux-meta (Ubuntu)
Status: New = Fix Released
--
broken dependency in kernel upgrade
https://bugs.launchpad.net/bugs/133967
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Closed. No further action needed. 23.8.2007 repositories already
contained all the dependent packages.
--
broken dependency in kernel upgrade
https://bugs.launchpad.net/bugs/133967
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I'm running Gutsy for several months. Today I upgraded to the new kernel
2.6.22-10 and I should have not, since there are broken dependencies as you're
mentioning guys - the crucial one is absence of: linux-ubuntu-modules-2.6.22-10
in the repos, which prevents other 2 kernel related packages
*** This bug is a duplicate of bug 127944 ***
https://bugs.launchpad.net/bugs/127944
I have the same problem when starting OO, which does not start:
(process:26161): GLib-GObject-CRITICAL **:
/build/buildd/glib2.0-2.13.7/gobject/gtype.c:2242: initialization
assertion failed, use
Same problem on Gutsy Gibbon running nvidia proprietary drivers with
Geforce Go 7400, all recent gnash packages including the latest one.
--
gnash using 100% CPU
https://bugs.launchpad.net/bugs/91910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
As mentioned in the bug https://bugs.launchpad.net/ubuntu/+bug/115014
the purge+reinstall of kdebase-data helps. KDM must not be running
during the operation, just feel free to kill it. Afterwards, myself I
had to reinstall kicker, KDE applets and KDE theme manager, since it has
been also removed
75 matches
Mail list logo
