On Friday 02 January 2015 11:56:09 Christopher M. Penalver wrote: > Rob: > >"So what I'm doing is more purposeful than nagging people > >about opening a new bug report with info that you already > >have." > > Spamming everyone with comments about a forum post is not > helping here. As well, nobody has the information previously > requested from you, as you didn't file a new report. >
Christopher, spamming everyone without your useless posts about duplicating same bug is even less useless. > >"*IF* it is a BIOS/firmware/EC bug there is no point in > >opening yet another bug report for an issue that can't be > >resolved in Linux!" > > Then you don't understand how linux kernel development works. And you Christopher do not know how linux kernel development works too! *NOBODY* in linux kernel development want from users to open duplicate bug reports. > On select occasions, linux kernel engineers (not Dell > employees) have implemented patches that WORKAROUND buggy, > and outdated BIOS and hardware firmware. > Citation needed (TM). Who and how implemented WORKAROUND for outdated BIOS? And what is outdated BIOS?? Btw, *I* am that developer who implemented WORKAROUND for current situation and sent patch to upstream kernel (which is now part of 3.18 release). But it has nothing with BIOS and there are no outdated BIOS versions. If you still do not understand this problem reported in this (and more other!) bugs happens on all Latitude Exx40 machines with any BIOS version. I'm fed up with you. You just spam bug reports, bitching on users who reported serious and critical problems, you did not helped with *anything* and also you did not implemented any fix for this problem. Sorry but *all* your comments in this (and others too) are totally useless. It did not helped me or other people who wanted to fix this problem. What you have done is just fed up users and forced them to not report bugs anymore because it is useless... > However, by not filing a report, you are robbing developers to > track the true impact this has, all the hardware permutations > that may be affected, and the opportunity to review your > hardware specifically (marking yourself affected, or making > "Me too!" comments is useless here as it's not verifiable by > anyone). As well, you are just adding comment noise that > isn't contributing towards having the issue addressed. By not > doing as previously requested, you are only delaying your own > problem from being addressed. Addressed to whom? In last year nobody else provided any fix for this bug. So what are you trying to do? We already know that this problem is *same* for all Exx40 laptops and affect all people. And posts "me too" just say that this problem happens really on all those laptops and with all BIOS versions. -- Pali Rohár [email protected] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258837 Title: [Dell Latitude E7440] ALPS touchpad keeps having state reset Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Bug description: The mouse cursor keeps on jumping around, and these messages appear in the log when it happens: Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1 Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced. The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad". This is occurring with Ubuntu 13.10, though I have also seen this behaviour in the version of Linux Mint based on Ubuntu 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: allanc 1852 F.... pulseaudio /dev/snd/controlC0: allanc 1852 F.... pulseaudio Date: Sat Dec 7 22:19:22 2013 HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec InstallationDate: Installed on 2013-12-07 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E7440 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 07F3F4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
