« previous next »
Pages: 1 2 [3] 4 5

Author Topic: touchscreen problem  (Read 34581 times)

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5549
  • DOES work for LinuxMCE.
    • View Profile
Re: touchscreen problem
« Reply #30 on: September 17, 2009, 07:17:34 pm »
it comes down to the fact that I decode and send everything that comes across the input subsystem. I need to find a better way to filter spurious events.

-Thom
Logged

Zaerc

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 2256
  • Department of Redundancy Department.
    • View Profile
Re: touchscreen problem
« Reply #31 on: September 17, 2009, 07:54:25 pm »
Quote from: widescreen on September 17, 2009, 05:37:26 pm
...
Hope you understand where we're coming from from, it's a little frustrating to have something working one day, and spending alot of money to purchase more hardware that was proven compatible, to only have your entire setup made useless the next day because of an error i did not make, nor have the equip to fix.
...
The error is all yours, if only just for using alpha software in a production environment.  Yes this needs to be fixed, but simply saying that you made no error is bullshit.
Logged
"Change is inevitable. Progress is optional."
-- Anonymous

widescreen

  • Veteran
  • ***
  • Posts: 70
    • View Profile
Re: touchscreen problem
« Reply #32 on: September 17, 2009, 08:54:19 pm »
Quote from: hari on August 26, 2009, 05:08:49 pm
tschak: if this is really a regression, it has to be fixed asap. We can't trash existing stuff with new patches. And just as a note, that hid stuff should not really be handled in orbiter.

br, Hari

Zaerc, i tend to agree with the statement above. i can't understand why you would even jump in here and not have anything beneficial to say.  I am aware that it is alpha, but does it really makes sense to say my statement is bullshit, taking into account it was working up until a recent update? i could understand you saying that if i was expecting a new feature or something that has been broken prior to a recent update. so how is the error all mine?  come on dude, i was only making sure that thom didn't take offense to my posts because no disrespect was intended. read the post, i even thanked him for his help in trying to fix it back.  Thom, once again, thanks.  zaerc, take it easy
Logged

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1758
    • View Profile
Re: touchscreen problem
« Reply #33 on: September 17, 2009, 09:56:52 pm »
Quote from: Zaerc on September 17, 2009, 07:54:25 pm
Quote from: widescreen on September 17, 2009, 05:37:26 pm
...
Hope you understand where we're coming from from, it's a little frustrating to have something working one day, and spending alot of money to purchase more hardware that was proven compatible, to only have your entire setup made useless the next day because of an error i did not make, nor have the equip to fix.
...
The error is all yours, if only just for using alpha software in a production environment.  Yes this needs to be fixed, but simply saying that you made no error is bullshit.

Everyone is being told regularily to install 0810 and that 0710 is no longer supported.  These 2 posts specifically come to mind:

http://forum.linuxmce.org/index.php?topic=8689.msg58754#msg58754
http://forum.linuxmce.org/index.php?topic=8568.msg57650#msg57650

Seems to me that someone testing your alpha software has found a bug that may not have been found otherwise.  How is this the users error?

The more you insult your userbase the less people want to contribute.

J.
Logged

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: touchscreen problem
« Reply #34 on: September 17, 2009, 11:58:13 pm »
Zaerc, Thom, Phenigma & Widescreen.....

cool it please! drop the argument at this point, and stay on thread....

of course this is an issue, and naturally it needs to be fixed.... I'm quite certain that thom will get on to it when he has a chance, he is very busy. We are in an unfortunate, sticky situation.... 0710 is no longer supported (and cannot be, realistically) however 0810 is still in Alpha... please be mindful of what alpha means, even though it is really the only "supported" version available at the moment.

Things will improve, and thom will fix this in due course. In the meantime, lets impassionately report the symptoms. Thom is obviously not experiencing the same issue, so any further data will help him lock it down.

Thom - perhaps there is a simple way in which they can capture the HID stream and send it to you so that you can see the issue occurring and adjust your filtering??
Logged

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5549
  • DOES work for LinuxMCE.
    • View Profile
Re: touchscreen problem
« Reply #35 on: September 18, 2009, 12:01:24 am »
grepping for GenericHIDInterface in the Orbiter log should be sufficient.

-Thom
Logged

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: touchscreen problem
« Reply #36 on: September 18, 2009, 12:47:19 am »
ok, guys, do you know how to do this? Find your orbiter log file by looking up its device number in the web admin, then:

grep -i generichidinterface /var/log/pluto/##_LaunchOrbiter.sh.log

where ## is the device number
Logged

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5549
  • DOES work for LinuxMCE.
    • View Profile
Re: touchscreen problem
« Reply #37 on: September 18, 2009, 01:19:36 am »
i typically tail it.

-Thom
Logged

widescreen

  • Veteran
  • ***
  • Posts: 70
    • View Profile
Re: touchscreen problem
« Reply #38 on: September 18, 2009, 03:35:21 am »
bb90>
01      09/16/09 17:13:09.761           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:13.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:17.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:21.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:25.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:29.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:33.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>
01      09/16/09 17:13:37.765           GenericHIDInterface::DecodeEventInFD: Short read from fd 1 <0xb3c6bb90>

device number is 31, got error message grep: /var/log/pluto/31_LaunchOrbiter.sh.log: No such file or directory. pulled up above log using grep -i generichidinterface /var/log/pluto/21_LaunchOrbiter.sh.log. 21_LaunchOrbiter.sh.log being the only log under that directory.  Also pulled up the log on the md itself, but it had no mention of genericHIDInterface. pretty sure that the above is not what is needed, but that all that seems to come up remotely close to the request. let me know where to find the correct log if so. thanks alot guys. I appreciate the help big time fellas. thanks again.

Logged

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5549
  • DOES work for LinuxMCE.
    • View Profile
Re: touchscreen problem
« Reply #39 on: September 18, 2009, 03:40:47 am »
you should not see a short read at all. did you remove an input device?

-Thom
Logged

widescreen

  • Veteran
  • ***
  • Posts: 70
    • View Profile
Re: touchscreen problem
« Reply #40 on: September 18, 2009, 05:21:52 am »
Quote from: tschak909 on September 18, 2009, 03:40:47 am
you should not see a short read at all. did you remove an input device?

-Thom

thom, nope buddy. i only don't leave the mds on since i don't use it since the problem began.  maybe wrong dir/log i'm looking into?    :-\
Logged

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5549
  • DOES work for LinuxMCE.
    • View Profile
Re: touchscreen problem
« Reply #41 on: September 18, 2009, 05:25:45 am »
short reads happen when the handler tries to read from a device that is no longer there...hmm..

do you not see DecodeEventinFD messages?

-Thom
Logged

widescreen

  • Veteran
  • ***
  • Posts: 70
    • View Profile
Re: touchscreen problem
« Reply #42 on: September 18, 2009, 05:33:03 am »
Quote from: tschak909 on September 18, 2009, 05:25:45 am
short reads happen when the handler tries to read from a device that is no longer there...hmm..

do you not see DecodeEventinFD messages?

-Thom


yes, could that be due to the removal of another md days ago? should i post sections of the whole log to give you a better idea of what is happening?
Logged

widescreen

  • Veteran
  • ***
  • Posts: 70
    • View Profile
Re: touchscreen problem
« Reply #43 on: September 18, 2009, 05:38:49 am »
here is the log from the md

== ATTEMPT FRESH START ==
1   09/11/09 10:04:38   /usr/pluto/bin/Spawn_Device.sh 33 (spawning-device)   25394 Dev: 33; Already Running list: 32,
== FRESH START ==
1   09/11/09 10:04:39   /usr/pluto/bin/Spawn_Device.sh 33 (spawning-device)   device: 33 ip: dcerouter cmd_line: LaunchOrbiter.sh
0   09/11/09 10:04:39   33 (spawning-device)   Entering 33
========== NEW LOG SECTION ==========
1   09/11/09 10:04:39   33 (spawning-device)   Starting... 1
1   09/11/09 10:04:39   33 (spawning-device)   Found /usr/pluto/bin/LaunchOrbiter.sh
05   09/11/09 10:11:14.597      Xlib: ErrorHandler_Grabber() // static int X11wrapper::ErrorHandler_Grabber(Display*, XErrorEvent*) <0xb70ec8e0>
05   09/11/09 10:11:14.634      Xlib: ErrorHandler_Grabber() // static int X11wrapper::ErrorHandler_Grabber(Display*, XErrorEvent*) <0xb70ec8e0>
Logged

widescreen

  • Veteran
  • ***
  • Posts: 70
    • View Profile
Re: touchscreen problem
« Reply #44 on: September 18, 2009, 05:42:28 am »
========== NEW LOG SECTION ==========
1   09/17/09 23:17:52   33 (spawning-device)   Starting... 2
1   09/17/09 23:17:52   33 (spawning-device)   Found /usr/pluto/bin/LaunchOrbiter.sh
05   09/17/09 23:17:54.829      Creating child 34 <0xb6fa48e0>
05   09/17/09 23:17:54.881      Creating child 36 <0xb6fa48e0>
05   09/17/09 23:17:54.935      Creating child 37 <0xb6fa48e0>
05   09/17/09 23:17:54.993      Creating child 38 <0xb6fa48e0>
05   09/17/09 23:17:55.056      Creating child 39 <0xb6fa48e0>
08   09/17/09 23:20:15.885      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:20:15.887      acquiring 4482.0.0.4484.2410 <0xb6f63b90>
08   09/17/09 23:20:15.889      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:20:15.891      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:20:16.183      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:20:16.183      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:20:16.184      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:20:18.478      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:20:18.478      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:20:18.479      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:22:16.519      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:22:16.519      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:22:16.520      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:22:16.881      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:22:16.881      acquiring 4482.0.0.4484.2410 <0xb6f63b90>
08   09/17/09 23:22:16.884      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:22:16.886      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:22:17.152      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:22:17.152      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:22:17.153      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
08   09/17/09 23:22:19.408      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
08   09/17/09 23:22:19.408      Orbiter::AcquireGrid orbiter grid pnp_33 max row 5 max col 3 cur row 0 cur col 0 <0xb6f63b90>
05   09/17/09 23:22:19.409      DataGridRenderer::RenderObject Need to render cell <0,0>=Internal HDD, cell count 1 <0xb6f63b90>
05   09/17/09 23:22:47.459      Event type 1 <0xb6fa48e0>
05   09/17/09 23:22:47.460      Event type 1 <0xb6fa48e0>
Logged
Pages: 1 2 [3] 4 5
« previous next »
 

Sitemap