[Bug 1063354] Re: Sudden Read-Only Filesystems
Hi, I can confirm Rahul Jain's observation: I am also on Mint 15. I had that problem since Mint 14, then not for a long while and yesterday it appeared again. In my case, I am sure, my Hardware is OK, no smart errors on the SSD, and as this is a notebook, I don't think, there are any pin problems on the connectors. I have noticed, that this problem appears every time, ther's heavy SDD activity, and lots of small data-blocks are beeing encrypted and written/read to the SSD. In particular yesterday I was enabling the calendar caching in my thunderbird lightning calendars. This provoked massive writing and reading operations. An other time that happened was again in thunderbird when I synchronized my 12GB IMAP Mailbox. I just tried to verify my theory about many little files/small data-blocks - I used bonnie++ to write many little files in a very fast manner. Result: same dmesg output, ends in kernel panic... This is a vital problem so a fix needs to be found asap. regards and merry Christmas , Felix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063354 Title: Sudden Read-Only Filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
Hi all of you, who are having this problem: Please review my report: https://bugs.launchpad.net/ubuntu/+bug/550559/comments/41 That's how I was able to resolve the Problem. in short words: get current kernel source from www.kernel.org install kernel-package make oldconfig using the ubuntu config found in /boot/config-2.6.XX build the new kernel, optionally create a deb package and install it. boot the new kernel... give it a try... I'm running a server now for 3 Month's without any problems. Felix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
My Hardware: Mainboard: GA-879A-UD3 The relevant output from lspci (disc controllers): 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (rev 40) 00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller (rev 40) 04:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) 04:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03) 06:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 02) 06:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 02) Used discs: Seagate ST31000524NS Firmware SN11 (according to smartctl --all), currently no FW upgrade available Western DIgital WD1003FBYX Both disc types are 24/7 discs according to their manufactures. Everytime I will talk about kernel compilation, I use the .config from the original ubuntu 10.10 server kernel and create .deb files using kernel-package. All of the issues above are the same that happened to me with the Seagate discs which I bought in the first place in combination with the mentioned mainboard. I already had a working system on those 4 discs, but connected through an PCI-E SAS controller, working like a charm. As the controller was only for testing purposes, I connected my 4 discs directly to the mainboard. Thats where all the problems begun you are describing above. I couldn't boot my system anymore, but each time, when I booted with RIP-Linux or knoppix the installed linux raid + lvm2 signatures were found and usable. No errors were reported to dmesg. Simply booting the system was not possible. As the data on the discs were not to important, I decided to install from scratch... So I booted with my ubuntu 10.10 server cd. When the installer came to the partition manager, the errors you're describing all occurred on console ALT+F4. When I hit the reset button, the mainboard's bios did not recognize the discs anymore and hung while trying to enumerate the connected discs. After a hard reboot (pulled the cable) the bios at least worked again. So I made an bios upgrade. Same problem as before. By the time I destroyed my filesystem voluntarily as I thought, that this might have something to do with a signature, the initial SAS controller had written to the discs. I tried with Ubuntu 10.04 Server - exactly the same... So every time I booted a recent Ubuntu version, 64 or 32 bit, the partition manager could not read the discs and the mainboard was not able to enumerate after soft-reset. Everytime I booted with a non Ubuntu distro, I had no problems, I concluded, that this might be an ubuntu issue, so I decided to setup the new Debian Squeeze. Worked like a charm to me. But as usual, debian is outdated by the time it's released, so I installed the ubuntu 10.10 server kernel to my debian system and guess: Yes, same problem as above Next step was to use the ubuntu kernel sources, compile them in debian, and boot them - worked Now I got the vanilla kernel 2.6.37 (current stable), compiled and booted - worked Now I knew, that's an Ubuntu Kernel issue. 2 weeks later and having returning 3 of 4 hard discs as I thought they might have a failure (transportation etc...) I decided to buy the 4 Western Digital 1TB discs to have a comparison. Setup Ubuntu 10.10 Server works perfectly. Now I setted up Ubuntu 10.10 Server to an old 160GB WD disc Next I plugged in the Seagate discs and got instantly the errors from above, so I compiled a recent stable vanilla kernel, in a native ubuntu environment and rebootet. All my Seagate discs were connected at that time of the reboot, and the system rebooted with my vanilla kernel without having any errors or performance issues. So I started my raid and lvm2, formated the /root partition on the lvm2, mounted it and all the other lvm2 partitions to the fs tree, and installed a ubuntu-minimal with debootstrap, chrooted, installed mdadm and lvm2, installed my vanilla kernel, setted up grub2 and bootet. Voila, my system's booting and running on the Seagate discs. 3 weeks have passed, since I started. But it was all worth the effort. Felix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 397096] Re: ata exception and hang when booting, at T=n.81606 s
please read my comment here, maybe this is related? https://bugs.launchpad.net/ubuntu/+bug/550559/comments/41 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/397096 Title: ata exception and hang when booting, at T=n.81606 s -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285892] Re: ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
please read my comment here, maybe this is related? https://bugs.launchpad.net/ubuntu/+bug/550559/comments/41 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/285892 Title: ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615077] Re: [Maverick] SDL local window broken in last update
Hi, I also encountered that problem: I'm running Maverik Merkat 10.10: Same message operation failed: failed to retrieve chardev info in qemu with 'info chardev' I played around like when you have a physical machine, that won't work: You remove piece by piece until it boots to figure out the faulty hardware: So I figured out, that when I reduce the used physical memory from 3072 MB RAM to 2048 the machine booted again. Remains the question: why did it work before with 3072MB and suddenly it stoops. BTW: I have 12GB physical memory in my server as well as 12 CPU Cores which gives me 24 threads. I had this problem before, and then usually a reboot of the machine did it also, of course, I can't reboot a host that runs 4 productive machines during business hours... What I'm curious about: The error message says error to retrieve chardev info... which console command could I use to directly check for info chardev? I think this is a mayor issue, as else kvm/libvirt or what ever else is responsible to cause that, is not to be run in productive environments. For me I switched from vmware-server to kvm to use pure open source... but I'm already thinking on going back as these issues, as well as still sometimes guests looses their network while still showing an up-state link within the guest - and so far there is no solution for that either. Thank you for solving those issues! -- [Maverick] SDL local window broken in last update https://bugs.launchpad.net/bugs/615077 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 615077] Re: [Maverick] SDL local window broken in last update
Hi, I also encountered that problem: I'm running Maverik Merkat 10.10: Same message operation failed: failed to retrieve chardev info in qemu with 'info chardev' I played around like when you have a physical machine, that won't work: You remove piece by piece until it boots to figure out the faulty hardware: So I figured out, that when I reduce the used physical memory from 3072 MB RAM to 2048 the machine booted again. Remains the question: why did it work before with 3072MB and suddenly it stoops. BTW: I have 12GB physical memory in my server as well as 12 CPU Cores which gives me 24 threads. I had this problem before, and then usually a reboot of the machine did it also, of course, I can't reboot a host that runs 4 productive machines during business hours... What I'm curious about: The error message says error to retrieve chardev info... which console command could I use to directly check for info chardev? I think this is a mayor issue, as else kvm/libvirt or what ever else is responsible to cause that, is not to be run in productive environments. For me I switched from vmware-server to kvm to use pure open source... but I'm already thinking on going back as these issues, as well as still sometimes guests looses their network while still showing an up-state link within the guest - and so far there is no solution for that either. Thank you for solving those issues! -- [Maverick] SDL local window broken in last update https://bugs.launchpad.net/bugs/615077 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 639734] Re: Pressing buttons on quanta hardware is very hard and imprecise
Henrik, could you provide a 32 bit version of mtview? I'd like to test the driver on an other machine, because ginn appears not to work... regards, Felix -- Pressing buttons on quanta hardware is very hard and imprecise https://bugs.launchpad.net/bugs/639734 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 639734] Re: Pressing buttons on quanta hardware is very hard and imprecise
Sure, education comes first! No, the mouse up issue is not solved yet, but I was on a fair one month ago and I realized, that touchscreens running under windows behave exactly the same way: when you touch the screen, it emulates a single-click, which means touching is same as left-click and moving... annoying. The far better solution would be to distinguish between soft approach = mouse-move and hard-touch = click that way you could move around the cursor without marking any icons or text etc... I also have the impression, that the sensitivity has gotten better... when using the clip controls or to snap the window edges for resize is better... Regarding my improval for the UI: I bought an android phone, and there within the phonebook there is on the right screen side 0-9A-Z from top to the bottom. When you move above them, the current letter is displayed in a huge manner in the middle of the screen so you always know, what's underneath your fingers I think, that's worth implementing in ubuntu... Regarding the X-start problem: No, I have not yet tried to reconfigure the server... it simply append after the upgrade. I will let you know, as soon as I have tried it! -- Pressing buttons on quanta hardware is very hard and imprecise https://bugs.launchpad.net/bugs/639734 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 675245] [NEW] evaluation from the systemload on multiprocessor machines in 50-landscape-sysinfo
Public bug reported: Binary package hint: update-motd Hi, The following issue applies to any recent Ubuntu distribution and architecture: I have made an observation regarding the calculation of the system load within the update-motd package: When I was logging in to my 12-core /12GB RAM Server I got the message System information disabled due to load higher then 1 But when I checked the system with top or htop barely 2 cores where occupied. So I investigated the code in /etc/update-motd/50-landscape-sysinfo. Next I informed myself about the calculation of the sysload and it's meaning. Apparently, a load average of 1.0 means, that means that 1 CPU has been fully occupied during the measuring period of 1/5/15 minutes... So, on a 12 core machine a load of 1.0 is no danger and indicator for resource shortage. Therefor I have added some lines to /etc/update-motd/50-landscape-sysinfo: #!/bin/sh cput=`cat /proc/cpuinfo |grep processor|wc -l` cpuc=`echo scale=0;$cput/2| bc -l` #echo cpucores: $cpuc #exit if [ $(echo `cut -f1 -d ' ' /proc/loadavg` $cpuc.0 | bc) -eq 1 ]; then echo echo -n System information as of /bin/date echo /usr/bin/landscape-sysinfo else echo echo System information disabled due to load higher than CPU Core-Count $cpuc fi Maybe I'm totaly wrong about my theory, then please teach me otherwise, else, maybe it's worth to publish it? Regards, Felix ** Affects: update-motd (Ubuntu) Importance: Undecided Status: New -- evaluation from the systemload on multiprocessor machines in 50-landscape-sysinfo https://bugs.launchpad.net/bugs/675245 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 639734] Re: Pressing buttons on quanta hardware is very hard and imprecise
Hello, there is news, and I'm not sure, if this is still the right place for that to post but it relates to it, so feel free to make a new bug out of that: After the Upgrade to 10.10 my x-server doesn't start, and I can't even use CRTL+ ALT + F1 to switch to a console... the only way I got the report was to login via ssh! First I stopped the gdm. Next: startx - brings up that error message below. So I disconnected the USB cable from the screen and fired up gdm again - gdm started normally. Then I reconnected the touchscreen - and it was perfectly recognized and usable. What is wrong? Thanks, in advanced. (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device Unable to query/initialize EVTouch hardware. [dix] couldn't enable device 11 (EE) Couldn't init device Acer T231H Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e82fb] 1: /usr/bin/X (0x8048000+0x5da8d) [0x80a5a8d] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb76fc410] 3: /usr/bin/X (xf86findOptionValue+0x24) [0x80cab64] 4: /usr/bin/X (0x8048000+0x6a5e2) [0x80b25e2] 5: /usr/bin/X (0x8048000+0x6b169) [0x80b3169] 6: /usr/bin/X (xf86OpenSerial+0x43) [0x816da43] 7: /usr/lib/xorg/modules/input/evtouch_drv.so (0xb6d27000+0x2413) [0xb6d29413] 8: /usr/bin/X (EnableDevice+0xc9) [0x80679c9] 9: /usr/bin/X (0x8048000+0x1fd5f) [0x8067d5f] 10: /usr/bin/X (0x8048000+0x1a577) [0x8062577] 11: /lib/libc.so.6 (__libc_start_main+0xe7) [0xb741ece7] 12: /usr/bin/X (0x8048000+0x1a191) [0x8062191] Segmentation fault at address 0x3 Caught signal 11 (Segmentation fault). Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. -- Pressing buttons on quanta hardware is very hard and imprecise https://bugs.launchpad.net/bugs/639734 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 639734] Re: Pressing buttons on quanta hardware is very hard and imprecise
we are almost there! I am writing this text with the onboard onscreen keyboard. we need now some improvement to distinguish between a movement, a click and a dbl-click. the cursor is very precise - which is good for almost tasks except for window snapping operations like resizing windows. the problem is, that the finger is covering the cursor, hence you dont see, when the cursor snaps the window border to resize! my proposition would be a bubble message close to the finger to indicate the underlaying cursor icon so that one knows when to start the resizing. an other issue is the use of that onscreen keyboard: to actualy change the mouse position from one key to the other (i notice this everywhere) i have to slightly sweep to the position where the cursor should then go. maybe this is related to the first issue. but congratulations and thank you for this version. this should be the basis for any further improvements. -- Pressing buttons on quanta hardware is very hard and imprecise https://bugs.launchpad.net/bugs/639734 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 639734] Re: Pressing buttons on quanta hardware is very hard and imprecise
I can confirm Linus's observations. -- Pressing buttons on quanta hardware is very hard and imprecise https://bugs.launchpad.net/bugs/639734 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 639734] Re: Pressing buttons on quanta hardware is very hard and imprecise
New Driver: Pointer follows finger very smoothly, but the left mouse click or dbl click is impossible - same behavior for real mouse. Loading the driver when easystroke is active, the screen pointer behaves like permanently pressed, as in easystroke the left button is configured for the gesture recognition; therefor the gesture recognition does not work either. The real mouse doesn't work at all until I unload the driver, kill easystroke and reload the driver. The right button and the wheel from the real mouse are working (context menus are opening and scrolling in windows works also fine) -- Pressing buttons on quanta hardware is very hard and imprecise https://bugs.launchpad.net/bugs/639734 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 639734] Re: Pressing buttons on quanta hardware is very hard and imprecise
** Attachment added: quanta-new-output.dat https://bugs.launchpad.net/ubuntu/+source/utouch/+bug/639734/+attachment/1597722/+files/quanta-new-output.dat -- Pressing buttons on quanta hardware is very hard and imprecise https://bugs.launchpad.net/bugs/639734 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 639734] Re: Pressing buttons on quanta hardware is very hard and imprecise
The Test sequence was: try to tap on some of the desktop icons (left), next tap on the gnome-menu and other elements within the gnome-panel. Mouse-Over Tool-tips within the panel are popping up. -- Pressing buttons on quanta hardware is very hard and imprecise https://bugs.launchpad.net/bugs/639734 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 639734] [NEW] pressing buttons on quanta hardware is verry hard and unprecisely
Public bug reported: Binary package hint: utouch Works fine with easystroke for gesture recognition Moving windows is very hard, changing the size almost impossible. Using the clip controls is also very hard. Even with a stylus (used from an ancient Compaq IPaq) The attachments: during recording I have touched the screen on all edges, one finger and two fingers. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: utouch 1.1 ProcVersionSignature: Ubuntu 2.6.35-20.29-server 2.6.35.4 Uname: Linux 2.6.35-20-server x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 15 18:25:30 2010 InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release amd64 (20100427) LsInput: /dev/input/event0 MachineType: System manufacturer System Product Name MtDevices: Acer T231H: /dev/input/event5 PackageArchitecture: all ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-20-server root=UUID=9c294c89-0d00-4504-bc28-9070a486c118 ro quiet splash vga=791 ProcEnviron: LANG=de_AT.utf8 SHELL=/bin/bash SourcePackage: utouch dmi.bios.date: 07/02/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0507 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0507:bd07/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: utouch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hci maverick touch ubuntu-une -- pressing buttons on quanta hardware is verry hard and unprecisely https://bugs.launchpad.net/bugs/639734 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 639734] Re: pressing buttons on quanta hardware is verry hard and unprecisely
** Attachment added: quanta-bugrep.tgz https://bugs.launchpad.net/bugs/639734/+attachment/1589347/+files/quanta-bugrep.tgz ** Attachment added: 0003040830010003.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589348/+files/0003040830010003.txt ** Attachment added: 00030A8102050001.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589349/+files/00030A8102050001.txt ** Attachment added: 00030A8102050002.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589350/+files/00030A8102050002.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589351/+files/BootDmesg.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589352/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589353/+files/Dependencies.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589354/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589355/+files/Lsusb.txt ** Attachment added: PciDisplay.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589356/+files/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589357/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589358/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589359/+files/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589360/+files/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589361/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589362/+files/UdevLog.txt ** Attachment added: XInput.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589363/+files/XInput.txt ** Attachment added: XorgConf.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589364/+files/XorgConf.txt ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589365/+files/XorgLog.txt ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589366/+files/XorgLogOld.txt ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/639734/+attachment/1589367/+files/Xrandr.txt -- pressing buttons on quanta hardware is verry hard and unprecisely https://bugs.launchpad.net/bugs/639734 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 639734] Re: pressing buttons on quanta hardware is verry hard and unprecisely
As requested /proc/bus/input/devices: I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name=AT Translated Set 2 keyboard P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=0a81 Product=0205 Version=0110 N: Name=CHESEN PS2 to USB Converter P: Phys=usb-:00:04.0-3/input0 S: Sysfs=/devices/pci:00/:00:04.0/usb4/4-3/4-3:1.0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: EV=120013 B: KEY=10007 ff9807ff febeffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=0a81 Product=0205 Version=0110 N: Name=CHESEN PS2 to USB Converter P: Phys=usb-:00:04.0-3/input1 S: Sysfs=/devices/pci:00/:00:04.0/usb4/4-3/4-3:1.1/input/input4 U: Uniq= H: Handlers=kbd mouse0 event4 B: EV=17 B: KEY=1f001f 202 3878d801d001 1e 0 B: REL=103 B: MSC=10 I: Bus=0003 Vendor=0408 Product=3001 Version=0110 N: Name=Acer T231H P: Phys=usb-:00:02.0-2/input0 S: Sysfs=/devices/pci:00/:00:02.0/usb3/3-2/3-2:1.0/input/input5 U: Uniq= H: Handlers=mouse1 event5 B: EV=1b B: KEY=400 0 0 0 0 0 B: ABS=263 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name=Video Bus P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:11/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event6 B: EV=3 B: KEY=3e000b 0 0 0 -- pressing buttons on quanta hardware is verry hard and unprecisely https://bugs.launchpad.net/bugs/639734 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
