[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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. On short distances, under mild pressure of the finger, the cursor jumps over too many pixels - which is annoying. Lost sensitivity can't be fixed by changing Pointer acceleration or Pointer threshold in mouse preferences. DELL E6410, Kubuntu Oneiric nightly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/550625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 791548] Re: Oneiric: Never sees NetworkManager connection
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 connection -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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 latest Natty 2.6.38-8-generic kernel. Kernel sources from Ubuntu kernel 2.6.37 were used, because there is no support for this touchpad model included, which makes it possible to apply patch by developed by Andrew Skalski - see comment #154 - which has one great advantage over the patch included in Ubuntu 2.6.38 kernels - it is easy to tweak. Find the following line in the Adrew's patch: alps_ec_write(psmouse, 0x0005, 0x01) and replace it with line: alps_ec_write(psmouse, 0x0005, 0x03) The patch includes comments about what that flags (3rd parameter of alps_ec_write) mean, i.e. writing 0x03 to the 0x0005 registry - see comment #184. Apply the modified patch on the 2.6.37 drivers (input/mouse) directory and compile the mouse drivers against your 2.6.38 kernel headers. This should result in psmouse.ko which supports touchpad vertical scrolling with tap to click disabled. It is clear that in order to fully support this touchpad model under Linux a userspace driver should be written. Everything else is just IMPS emulation which will never support horizontal scrolling or enable synaptics touchpad control panel. Nb. I just rephrased what was already said by other clever people here, so please search previous comments before asking questions about the Andrew's patch. I think that everything has been already said :-) A driver must be developed which is non-trivial without knowing the touchpad internals specs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665891] Re: Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7
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 frequent (but persists) with i7 640M 2.80 CPUs (and probably very rare with i5 CPUs - unconfirmed) 4) probably it is not dependent on GPU chip used in the configuration 5) probably it could be fixed by BIOS and is not a mainboard design flaw, still A06 BIOS update did not fix it IMO all E6410 owners with i7 2.66 CPU are affected if the above assumptions are true. Why they are no massive complaints by customers about these systems could be because: - either most users do not use Sleep and use Hibernate instead - or most of builds were sold with i5 CPUs - people from Windows world are just used to random freezes and don't pay attention to particular circumstances causing the freeze Andrew, either try disabling Speed Step or always remember to resume only when plugged-in to power outlet ;-) I went the way of disabling Speed Step and am waiting for the A07 BIOS (if ever it fixes the issue). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665891 Title: Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665891] Re: Dell Latitude E6410: System freeze on S3 resume with Intel Core i7 CPUs (affects any OS)
** 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. https://bugs.launchpad.net/bugs/665891 Title: Dell Latitude E6410: System freeze on S3 resume with Intel Core i7 CPUs (affects any OS) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656631] Re: resume from suspend does not initialize the display on 2.6.35 kernel
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/656631 Title: resume from suspend does not initialize the display on 2.6.35 kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 wear out the SSD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/578673 Title: [arrandale] Resume doesn't work on a Latitude E6410 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656631] Re: resume from suspend does not initialize the display on 2.6.35 kernel
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 this acpi_sleep=nonvs tweak is no longer necessary. You may try it with 2.6.36 kernel downloadable e.g. from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-maverick/ You would need to download 3 files into a new empty directory: 1) linux-headers-2.6.36-020636_2.6.36-020636.201010210905_all.deb 2) linux-headers-2.6.36-020636-generic_2.6.36-020636.201010210905_ARCH.deb 3) linux-image-2.6.36-020636-generic_2.6.36-020636.201010210905_ARCH.deb where ARCH stands for your OS architecture, either i386 or amd64. Once you have the corresponding 3 files downloaded, run sudo dpkg -i linux* (without quotes) from this directory. Thanks to linux-headers and DKMS support the nVidia kernel module should be compiled and inserted to kernel automatically. If everything installs successfully you may try to reboot into your new kernel and see if it helped. Dirkd: You say it failed at least once a day. Didn't you just change recently your daily habits using your laptop? It took me quite a long time to realize the resume failure occurs only on resume from battery power, so sometimes it made me feel it fails more often than the other day. Usually users don't realize if they're performing resume on batteries or on AC which makes them feel that sometimes it fails and sometimes it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/656631 Title: resume from suspend does not initialize the display on 2.6.35 kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 to be the precondition for the issue to appear. I dare to say that: any E6410 + GPU nVidia NVS 3100M + CPU Core i7-620 @ 2.66GHz = freeze on resume from STR on batteries sooner or later BIOS rev. A04, A05, A06 plays no role as well as amount of installed RAM or its vendor or additional miniPCI devices. I didn't go that far to physically unplug the fingerprint reader or further HW hacking. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/578673 Title: [arrandale] Resume doesn't work on a Latitude E6410 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665891] Re: Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7
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 BIOS revision. The A06 is not yet out, so we'll see once I'll be able to test it. The issue only occurs on resume from S3 suspend while the laptop runs on battery power, using any kernel, including Windows kernels. Derrik for your issues I think you'd better submit a different bug report. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656631] Re: resume from suspend does not initialize the display on 2.6.35 kernel
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, the problem is the same), it's not about Mainboard (Dell replaced my MB), it's not about RAM type (I tested with different modules of different sizes), not even about HDD (i tested with SSD and classical HDD), not about PCI peripherals (i removed all removable PCI peripherals), not about batttery model (I tried with a different models - 6cell and 9cell). It's most probably about the BIOS bug affecting Latitude E6410 with Core i7 620M 2.66Ghz (Dell replaced my CPU for the same model with no improvement); probably a race condition during frequency scaling (SpeedStep) on resume on batteries. Try disabling SpeedStep in BIOS and the problem does not appear; however it is a very unlucky solution. I'm trying to persuade Dell to give me a different nearest model of Core i7 CPU, even though I should pay for the difference in price. I expect that a different resulting CPU frequency helps to avoid the problem. BIOS should resolve it, but who knows when A06 comes out an if it would contain the fix. If one follows the history of E6400 latop overheating issues, it took one year and 10 BIOS revisions to mitigate the problem. I'm not sure whether the GPU is involved in this strange race condition when resuming on batteries. Please paste here your system specifications, especially CPU and GPU specs. -- resume from suspend does not initialize the display on 2.6.35 kernel https://bugs.launchpad.net/bugs/656631 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656631] Re: resume from suspend does not initialize the display on 2.6.35 kernel
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 vendors. -- resume from suspend does not initialize the display on 2.6.35 kernel https://bugs.launchpad.net/bugs/656631 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 nVidia nouveau+proprietary drivers, modifying nVidia card registry, physically unplugging PCI cards, disabling everything possible in BIOS etc., I decided to install Windows 7 (tried both clean install and whole range of Dell drivers stuff) supposing that of course no such issue would appear. The contrary was true! Same problem under Windows. Dell technician is about to bring a replacement CPU, mainboard and battery. I'll report the results when replacements are done. -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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) reboot (instructions above are valid for GRUB 2 which comes by default since Lucid i believe) With 2.6.36 kernels GRUB editing is no longer necessary. Expected result: always resumes on AC; almost always fails on battery-power; always resumes on both AC and batteries with SpeedStep disabled in BIOS. Disabling SpeedStep (CPU Frequency Scaling) by other methods like forcing CPU governor to performance or unloading cpufreq module (which is not possible on standard recent kernels, because it is no more a separately loadable module) does not have the same effect like disabling SpeedStep in BIOS. -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 intel_idle driver which manages C-states. Btw. powertop looks really cute when the upper C-states and P-states monitoring area is empty ;-) The result is still the same - system freezes on S3 resume from batteries. I still confirm that with SpeedStep disabled in BIOS the laptop resumes perfectly with full CPU power management enabled; however this seems to be just a coincidence proving nothing about the real cause of the problem. Same behavior observed with A03, A04 and A05 BIOS. Anyone here with Latitude E6410 can test S3 resume on batteries and post the results including their HW/SW specs? Please try at least 5 successive suspend/resume cycles without AC-power plugged in. It would be nice to know at minimum whether just a certain HW configuration is affected (e.g. models with nVidia card). -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665891] Re: Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7
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 the time. The link between system freeze on S3 resume from batteries and CPU power management has not been strictly proven. Please mark this bug report as invalid. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656279] Re: NVRM: os_raise_smp_barrier(), invalid context!
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 2.6.35 and 2.6.36 kernels (i suspect that for any other kernels as well) resume fails systematically when running on battery power and CPU SpeedStep is enabled in BIOS. This is of course unrelated to this topic. For info and if there is an E6410 owner reading : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578673/comments/135 -- NVRM: os_raise_smp_barrier(), invalid context! https://bugs.launchpad.net/bugs/656279 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 battery (with SpeedStep enabled) fails due to CPU freezing like I already described. -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665891] [NEW] Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7
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 problem disappears. Another, less clean, workaround was to completely disable Intel SpeedStep in BIOS. Same problem confirmed on both Ubuntu 2.6.35 and 2.6.36 series kernels as well as corresponding mainline kernels. Brief testing on 2.6.32, 2.6.33 and 2.6.34 kernels led to same resume freezes; on Lucid 2.6.32 kernel it *seemed* that disabling /usr/lib/pm-utils/sleep.d/94cpufreq script has helped to avoid the race condition on resume. Note: the race condition only appears when resuming the laptop (Dell e6410) on battery power. Thanks to Mario Limonciello from Dell Linux engineering for hinting that Intel Idle Driver might be the element playing the determining role in this S3 resume race condition. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.35-22-generic 2.6.35-22.35 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.36-1.7-generic 2.6.36 Uname: Linux 2.6.36-1-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 5836 F kmix /dev/snd/controlC0: user 5683 F knotify4 user 5836 F kmix CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe966 irq 44' Mixer name : 'IDT 92HD81B1C5' Components : 'HDA:111d76d5,1028040a,00100104' Controls : 15 Simple ctrls : 10 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xe308 irq 17' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 16 Simple ctrls : 4 Date: Sun Oct 24 15:18:38 2010 EcryptfsInUse: Yes InstallationMedia: Kubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100706) MachineType: Dell Inc. Latitude E6410 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.36-1-generic root=UUID=a19d680a-64b5-4ad8-92a5-25ca7051f5a8 ro vdso32=0 acpi_sleep=nonvs intel_idle.max_cstate=0 quiet splash vga=792 elevator=noop ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.39 SourcePackage: linux dmi.bios.date: 08/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0K42JR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/10/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel-power natty needs-upstream-testing regression-potential resume suspend -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665891] Re: Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7
-- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665891] Re: Kernel freeze on S3 resume due to Intel Idle Driver on Intel Core i7
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 set P-states to a fixed value during S3 resume process, in other words something that would cause the system to behave as if SpeedStep was disabled during S3 resume? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594837] Re: Lucid SRU: Intel Core i3/i5/i7 hang on resume from suspend (SCI_EN)
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 resuming on batteries (no matter whether previously suspended on AC or batteries) the system completely hangs - either on first attempt or usually on 2nd or 3rd or at max a 5th attempt of sequential suspend/resume cycles. No success tweaking with /etc/pm/* and /usr/lib/pm-utils/* disabling there actions related to current computer power source. Finally disabling CPU speed-step in BIOS resolved the problem. Tested with success on 20 sequential suspend/resume cycles on battery power. Evidently this a workaround which is killing the battery :/ I'm not sure what *exactly* the script /usr/lib/pm- utils/sleep.d/94cpufreq is about, but disabling it had no effect. I don't have enough knowledge to perform advanced tests with CPU scaling and governors. -- Lucid SRU: Intel Core i3/i5/i7 hang on resume from suspend (SCI_EN) https://bugs.launchpad.net/bugs/594837 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 variable (according to i7z) even with SpeedStep disabled, though the very low frequencies and turbo-boost frequency are never reached in contrast with SpeedStep enabled setup with ondemand governor. Successfully tested on 20 consecutive suspend/resume cycles on battery, same on AC power. Why does resume with SpeedStep enabled *only* fail when the machine is running on battery power remains unknown. Before forcibly disabling SpeedStep in BIOS I did a lot of different tests, disabling any possible PM scripts which either modified CPU governors (as e.g. /usr/lib/pm- utils/sleep.d/94cpufreq seems to do) or report the power state to other scripts (like /usr/lib/pm-utils/functions) forcing it to report that the machine is on AC-power even though it was not. Nothing was reliable enough. Is it a BIOS bug? Someone with Dell Latitude e6410, BIOS rev.A05, Intel i7 M 6...@2.67ghz can report the resume behavior when running on batteries with SpeedStep enabled? Both variants with either nVidia or Intel GFX should suffer from the same problem (if my laptop is not unique...) -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 resuming on battery power) mostly fails -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 260.x beta driver series How-to: 1) installed the kernel headers, headers-generic, image from the above URL 2) make sure that dkms has rebuilt the nvidia.ko for this kernel, otherwise you're out of luck with Xorg 3) sudo chmod -x /usr/lib/pm-utils/sleep.d/94cpufreq(otherwise 2nd resume when running on batteries may fail; please report if this was needed by trying multiple suspend/resume cycles with AC power disconnected) Reboot. No more frozen system stuck on black screen on resume, no matter if resumed while on AC or on battery power. -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659458] Re: blank screen on resume (Dell XPS M1330)
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578673] Re: [arrandale] Resume doesn't work on a Latitude E6410
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 2.6.36 kernel is released, which is expected very soon.. -- [arrandale] Resume doesn't work on a Latitude E6410 https://bugs.launchpad.net/bugs/578673 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49521] Re: Screen locks up black on laptop lid close.
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. https://bugs.launchpad.net/bugs/49521 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620662] Re: nm-applet don't enable wireless automatically
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 https://bugs.launchpad.net/bugs/620662 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159309] Re: Gutsy (k)ubuntu 7.10 on notebook HP nx6110: lid state incorrect after close-reopen
*** 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 lid close. * You can subscribe to bug 49521 by following this link: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/49521/+subscribe -- Gutsy (k)ubuntu 7.10 on notebook HP nx6110: lid state incorrect after close-reopen https://bugs.launchpad.net/bugs/159309 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49521] Re: Screen locks up black on laptop lid close.
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 - display goes off ...touching mouse and keyboard - display backlight comes up, but nothing is shown unless virtual terminal toggled or xset dpms force on command invoked 2) $ xset dpms force standby - mostly produces the same behaviour as scenario 1 - sometimes touching mouse and keyboard does not even turn on backlight and the command xset dpms force on needs to be called twice. Firstly the result of the call is backlight restore, after second call graphics starts to appear on display 3) # vbetool dpms off - display backlight turned off but graphics (barely) visible ...touching mouse and keyboard - nothing happens with display state ...need to invoke # vbetool dpms on or $ xset dpms force on to restore display to a backlit state Note: with Xorg.conf empty, default open-source display driver is used (nv? nouveau?), which results in low-res X without acceleration however dpms on and off works correctly. -- Screen locks up black on laptop lid close. https://bugs.launchpad.net/bugs/49521 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44393] Re: After closing the lid, video does not come back by pressing any key.
*** 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: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/49521/+subscribe -- After closing the lid, video does not come back by pressing any key. https://bugs.launchpad.net/bugs/44393 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22987] Re: lid.sh should use vbetool instead of xset
*** 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: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/49521/+subscribe -- lid.sh should use vbetool instead of xset https://bugs.launchpad.net/bugs/22987 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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. -- 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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 disable. The faulty patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commitdiff;h=bd79df42218fe1db5e683b567791d4bb97b60685 I notified Manoj about the existence of Andrew's patch. So attention, Andrew's patch currently does not apply cleanly since 2.6.35-22. Meanwhile I was able to successfully apply and compile the patch against 2.6.35-22 by patching drivers/input/mouse sources from 2.6.35-21. Andrew's patch also applied cleanly and works correctly on 2.6.36rc4. -- 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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 kernel, it should be made clear how to control the extra bits of IMPS mode settings from a userspace program (synclient?). ** Attachment added: psmouse.ko; 2.6.35-17-generic (x86-64); tapping disabled https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/+attachment/1507816/+files/psmouse.ko -- 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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. Could you please have a look at this kernel? -- 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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 consider this Dell contributed driver being the first step. I consider features like horizontal scrolling and sensitivity settings essential. IMO the touchpad by default is hypersensitive and it happens very often than one accidentally invokes a double-click action. While clicking the mouse button (right above the touchpad surface) the thumb accidentally touches the touchpad surface. The resulting action is two subsequent clicks, first one wanted, second one unwanted. -- 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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 a full touchpad experience, not just a crippled compatibility mode - there's even a web browser in the Latitude ON where standard scrolling touchpad features are used heavily. Once it is confirmed the touchpad really does not work correctly within this environment, I'd suggest to escalate the issue to the Dell support classified as a critical bug subject of a money back guarantee. -- 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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 does work, IMO it would mean a Linux compatible driver is found in the Instant ON image and could be exported. In both cases I assume that Linux kernel driver changes must follow GPL and the patched driver should be made available public. -- 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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: http://latitude-on-flash.com/#tab-buy -- 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 206793] Re: Cisco NAT mode setting ignor ed
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 https://bugs.launchpad.net/bugs/206793 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 206793] Re: Cisco NAT mode setting ignor ed
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 https://bugs.launchpad.net/bugs/206793 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 436088] Re: kmail crashed with SIGSEGV in QString::replace()
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 libkontactinterfaces4_4%3a4.3.1-0ubuntu3_amd64.deb libkpgp4_4%3a4.3.1-0ubuntu3_amd64.deb libksieve4_4%3a4.3.1-0ubuntu3_amd64.deb libmimelib4_4%3a4.3.1-0ubuntu3_amd64.deb kmail_4%3a4.3.1-0ubuntu3_amd64.deb -- kmail crashed with SIGSEGV in QString::replace() https://bugs.launchpad.net/bugs/436088 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 206793] Re: Cisco NAT mode setting ignor ed
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59867] Re: Synaptics touchpad ceases functioning after suspend and resume.
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 resume. https://bugs.launchpad.net/bugs/59867 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189644] Re: Compiz freezes on window resize
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. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 206793] [NEW] Cisco NAT mode setting i gnored
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 anything he does not like/know, so even the manual setting of TunnelingMode=1 in the kvpnc_Profile.pcf file has no effect since it is removed before connecting to the profile. (kvpnc version 0.9.0 on Ubuntu Hardy x64) ** Affects: kvpnc (Ubuntu) Importance: Undecided Status: New -- Cisco NAT mode setting ignored https://bugs.launchpad.net/bugs/206793 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 197959] Re: [Hardy]Recent kernel update to 2.6.24-11 breaks b43 (with bcm4312)
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 any of them. KNetworkManager hangs on message Activation stage: Configuring device.. When booting back the 2.6.24-4 kernel, the wireless works smoothly again. Must be related to kernel updates after 2.6.24-4. Strange thing is that all the network scanning stuff works, just the attempt to establish a connection fails, does not seem to even reach the IP configuration stage. -- [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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 197959] Re: [Hardy]Recent kernel update to 2.6.24-11 breaks b43 (with bcm4312)
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) [ 1092.535774] wlan0: deauthenticated [ 1092.538031] wlan0: Initial auth_alg=0 [ 1092.538037] wlan0: authenticate with AP 00:18:f3:57:f5:3c [ 1092.538061] wlan0: RX deauthentication from 00:18:f3:57:f5:3c (reason=7) [ 1092.538723] wlan0: Initial auth_alg=0 [ 1092.538727] wlan0: authenticate with AP 00:18:f3:57:f5:3c [ 1092.539752] wlan0: RX authentication from 00:18:f3:57:f5:3c (alg=0 transaction=2 status=0) [ 1092.539758] wlan0: authenticated [ 1092.539762] wlan0: associate with AP 00:18:f3:57:f5:3c [ 1092.541529] wlan0: authentication frame received from 00:18:f3:57:f5:3c, but not in authenticate state - ignored [ 1092.971378] wlan0: RX AssocResp from 00:18:f3:57:f5:3c (capab=0x411 status=18 aid=1) [ 1092.971389] wlan0: AP denied association (code=18) [ 1093.136999] wlan0: association with AP 00:18:f3:57:f5:3c timed out -- [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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 197959] Re: [Hardy]Recent kernel update to 2.6.24-11 breaks b43 (with bcm4312)
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 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 197959] Re: [Hardy]Recent kernel update to 2.6.24-11 breaks b43 (with bcm4312)
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183619] Re: [hardy] wlan0: AP denied association
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189644] Re: Compiz freezes on window resize
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189644] Re: Compiz freezes on window resize
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 just fine. Only the resize seems to fail if it is bound to this combination. ** Attachment added: xsession-errors.txt http://launchpadlibrarian.net/11968489/xsession-errors.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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189644] Re: Compiz freezes on window resize
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189644] Re: Compiz freezes on window resize
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 US standard delivered by the distro - especially the line: include level3(ralt_switch). Hardly it helps. If ever, I'll post my results here. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189644] Re: Compiz freezes on window resize
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 desktop can be manipulated neither by mouse nor by keyboard. CTRL+ALT+BKSPC required. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189644] [NEW] Compiz freezes on window resize
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 is OK, AltButton1 binding is OK. In standard KDM there is no such issue, ALT+Right Button combination smoothly resizes the windows. Version: compiz 0.5.5; Linux 2.6.24-4-generic #1 SMP Mon Jan 14 18:19:11 UTC 2008 x86_64 GNU/Linux The following appears when compiz is activated from the shell, but it starts without problems. Checking for Xgl: present. Checking for nVidia: not present. Checking for Xgl: present. Enabling Xgl with nVidia drivers... Starting emerald /usr/bin/compiz.real (core) - Warn: Unable to parse XML metadata from file ccp.xml /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format /usr/bin/compiz.real (dbus) - Error: dbus_bus_get error: Failed to execute dbus-launch to autolaunch D-Bus session /usr/bin/compiz.real (dbus) - Error: InitObject failed /usr/bin/compiz.real (core) - Error: Couldn't activate plugin 'dbus' ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59867] Re: Synaptics touchpad ceases functioning after suspend and resume.
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 causes ACPI to stop providing battery status to Power Manager until next reboot. Surely this is not an XOrg problem as I've read in some discussions. -- Synaptics touchpad ceases functioning after suspend and resume. https://bugs.launchpad.net/bugs/59867 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59867] Re: Synaptics touchpad ceases functioning after suspend and resume.
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 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59867] Re: Synaptics touchpad ceases functioning after suspend and resume.
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 properly after resume. -- Synaptics touchpad ceases functioning after suspend and resume. https://bugs.launchpad.net/bugs/59867 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102659] Re: USB device detection problems in 2.6.20
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 D820. 1) As root open for editing the file /etc/rc.local, e.g. by sudo nano /etc/rc.local 2) Add the following three lines before the last line (which should contain the text exit 0 and must be kept like that). echo -1 /sys/module/usbcore/parameters/autosuspend sleep 1 /usr/sbin/lsusb 3) Restart your machine It will disable autosuspend for all USB devices without having to patch kernel. My attempts to turn off autosuspend for selected devices were not successful. Remember to remove this script once a new kernel comes out having your problematic device in the USB autosuspend blacklist. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102659] Re: USB device detection problems in 2.6.20
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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102659] Re: USB device detection problems in 2.6.20
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 devices in their laptops: SGS Thomson Microelectronics Fingerprint Reader in my Latitude D820 has the problem. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102659] Re: USB device detection problems in 2.6.20
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 https://bugs.launchpad.net/bugs/102659 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133967] Re: broken dependency in kernel upgrade
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133967] Re: broken dependency in kernel upgrade
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133967] Re: broken dependency in kernel upgrade
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 from upgrading. In my case the system boots up, but I had to revert to nv driver since the nvidia-glx new fails to compile (logically) with not existing kernel sources for 2.6.22-10. Same problem for VirtualBox which needs to be recompiled and cannot find non installable kernel sources. Evidently the new kernel has been put into the repos prematurely. I hope the maintainers will fix it soon. I just wonder why in your case the kernel failed to load. It works fine for me, without having to hack anything. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128211] Re: openoffice does not start
*** 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 IA__g_type_init() prior to this function (process:26161): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (process:26161): Gdk-CRITICAL **: gdk_screen_get_font_options: assertion `GDK_IS_SCREEN (screen)' failed I'm running Ubuntu Gutsy x86-64. It must be related to a recent update (about 1 week). At the same time my GLX got broken. Basically graphics works, including desktop effects and transcluency... However starting any GL application (GL screen-saver, glxgears...) crashes my X session, unfortunatelly without any traces in the logs. I've been always using nvidia-glx-new drivers without problems (at least not critical ones), update to latest nVidia beta drviers from NVidia site (100 series) didn't resolve the problem. -- openoffice does not start https://bugs.launchpad.net/bugs/128211 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91910] Re: gnash using 100% CPU
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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114286] Re: systemsettings crash in Gutsy Gibbon
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 during the kdebase-data purge and reinstall. My Gutsy KDE menus are ok now. System-settings do not crash on access anymore. -- systemsettings crash in Gutsy Gibbon https://bugs.launchpad.net/bugs/114286 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kde-systemsettings in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
