epertinez
|
2009-03-03
, 08:56
|
Posts: 54 |
Thanked: 29 times |
Joined on Nov 2007
@ Catalonia
|
#21
|
|
2009-03-03
, 09:12
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#22
|
|
2009-03-03
, 09:17
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#23
|
The Following User Says Thank You to benny1967 For This Useful Post: | ||
|
2009-03-03
, 09:19
|
Posts: 415 |
Thanked: 732 times |
Joined on Jan 2009
@ Finland
|
#24
|
|
2009-03-03
, 10:09
|
Posts: 87 |
Thanked: 98 times |
Joined on Oct 2007
@ Austria
|
#25
|
It sounds like that's not necessarily your fault:
Known limitations: On Debian Lenny (x86 scratchbox target), the response time of actions on using the UI framework is known to be high.
The Following User Says Thank You to hns For This Useful Post: | ||
|
2009-03-03
, 10:40
|
Posts: 87 |
Thanked: 98 times |
Joined on Oct 2007
@ Austria
|
#26
|
I'm experiencing the same, multi-second gui response times on a recent laptop, and I think it's not related to Debian Lenny only, but to problems with the intel x.org driver in Ubuntu intrepid, jaunty and quite possibly Debian Lenny.
I don't have any hard evidence other than that I've seen the exact same problem happening for other applications that do something fancy graphics-wise, or java applications like jedit. I asked lcuk on IRC yesterday, and he confirmed he is also running Intrepid like me.
|
2009-03-03
, 10:55
|
Posts: 269 |
Thanked: 139 times |
Joined on Mar 2006
|
#27
|
|
2009-03-03
, 11:21
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#28
|
The Following User Says Thank You to benny1967 For This Useful Post: | ||
|
2009-03-03
, 11:39
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#29
|
|
2009-03-03
, 11:51
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#30
|