The patch is commited upstream.
Driver is not fully functional due to other bugs, but at least it's not
crashing anymore.
Should I post here a backport of the upstream bug targetted to the
Karmic driver version ?
--
driver crash xorg server on XkbApplyMappingChange
Public bug reported:
Binary package hint: xserver-xorg-input-aiptek
Trying to get my tablet working on my Ubuntu 9.10 (xorg 7.4; xorg-input-aiptek
1.3.0), my X server crashes.
After some investigations, I got a xorg backtrace showing XkbApplyMappingChange
as the last called method.
According
** Patch added: aiptek.diff
http://launchpadlibrarian.net/39264173/aiptek.diff
--
driver crash xorg server on XkbApplyMappingChange
https://bugs.launchpad.net/bugs/522575
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Bug watch added: freedesktop.org Bugzilla #26584
https://bugs.freedesktop.org/show_bug.cgi?id=26584
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=26584
Importance: Unknown
Status: Unknown
--
driver crash xorg server on XkbApplyMappingChange
Changes for the volume and network switch have been incorporated in the linux
kernel since this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a195dcdcff33b8ef01a23cbc489fdfcdfa28c88e
Those changes have been chipped with kernel 2.6.29 and are in Karmic.
It
Changes for the volume and network switch have been incorporated in the linux
kernel since this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a195dcdcff33b8ef01a23cbc489fdfcdfa28c88e
Those changes have been chipped with kernel 2.6.29 and are in Karmic.
It
Please have a look at bug #328989.
This package is not needed anymore as everything is handled in the
standard kernel acpi interface when the eeepc_laptop kernel module is
loaded.
So, please consider removing this package and stop new bug reports for a
non installable and non used package.
--
I did not already had a look at the new package, but is removing all the
UTF-8 sequences necessary ?
I mean, just replacing the old one (as I said here above):
Just lost some hours trying to get this working on my Jaunty
installation.
I also found that modifying the fontconfig.properties file resolved the problem.
I'm currently using fr_BE.UTF-8 as my locale.
The remaining problem does not come from some bug in the jdk, but only
the UTF-8 fonts
Inserting rfkill-input is necessary (I suppose some hal magic should
insert it automatically); but for now, inserting it manually is
required.
For the rest, I suppose your posted log is from a stock jaunty kernel.
The kernel from Andy should contain backport of the patches included in kernel
Troy, you said you did a fresh jaunty instal, did you patched your
kernel, or installed the one proposed by andy (see here above) ?
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You
*** This bug is a duplicate of bug 232170 ***
https://bugs.launchpad.net/bugs/232170
** This bug has been marked a duplicate of bug 232170
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
--
eeepc-acpi-scripts is not
Shouldn't the patch for ubuntu be:
http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/ui/dialog/print.cpp?view=patchr1=19909r2=19908pathrev=19909
** Attachment added: inkscape_bitmap.diff
http://launchpadlibrarian.net/24862898/inkscape_bitmap.diff
--
Bitmap-type print
If the correct patches are applied, as described in bug 232170,
everything is working. Those patches are included in kernel 2.6.29, but
unfortunately jaunty will ship with kernel 2.6.28.
--
eeepc-acpi-scripts is not installable
https://bugs.launchpad.net/bugs/262679
You received this bug
As this package is now automatically installed with jaunty, it's a
really annoying bug that should impacts all wireless users...
workaround works for me also, ath5k.
--
wireless-crda breaks capability to connect hidden wlan
https://bugs.launchpad.net/bugs/336915
You received this bug
Andy:
With your kernel build, wireless , sound, brightness and sleep keys work OK (
just as fine as the custom build I used) on my eeepc 701.
The only change I need to get everything working out of the box is to
add rfkill_input to /etc/modules (maybe some hal magic should do it for
me
Any chance a backport of the last Matthew Garrett's patch (mentioned here above
by Sitsofe) get in the Jaunty release ?
Or will we have to patch it our self and wait for Karmic ?
If there is something missing for this patch to get in, let me know what
it is...
--
EeePC Volume and Wireless
This package is not necessary anymore as everything needed to handle
eeepc acpi signals in the standard way is now in the linux kernel.
Just load the eeepc_laptop module and everything just works.
--
eeepc-acpi-scripts is not installable
https://bugs.launchpad.net/bugs/262679
You received this
Public bug reported:
Binary package hint: eeepc-acpi-scripts
As all acpi signals for the eeepc can be handled by the linux kernel in
the standard way, this package is not needed anymore.
The only remaining bit to solve is having ubuntu load the eeepc_laptop
module when running on an eeepc.
This last patch from mjg59 is the only missing part to get a working out of the
box eee 701.
Adding it to the kernel package should be really a nice.
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
Yes it solves the problem...
I think I now have a fully functional intrepid on my eeepc 701...
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
https://bugs.launchpad.net/bugs/232170
You received this bug notification because
I merged last Matthew's patch with previous one (making hot key and
rfkill working toegether).
It works well for me (except this nasty xorg bug that prevents rfkill
input capture but it's another problem...)
This new version allows me to start with rfkill default_state=0
(wireless disabled) and
Matthew Garrett posted some news about the eeepc wifi on his blog
=http://mjg59.livejournal.com/100587.html
And he propose a new patch I did not already tested:
= http://www.codon.org.uk/~mjg59/tmp/eeepc-laptop-hotplug.diff
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box
Porting this fix to the future intrepid release is trivial and will save
some paper ;-)
** Also affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
--
Bitmap-type print to printer and preview produces low resolution output
https://bugs.launchpad.net/bugs/258916
You received
A potential solution is maybe attached to upstream bug:
http://bugzilla.gnome.org/show_bug.cgi?id=329040
--
Alternative import structure, based on import rolls
https://bugs.launchpad.net/bugs/204011
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I also noticed some strange behavior just after boot; and the patch for
rfkill_input may solve it.
But there is another problem coming from the way key events are
processed: xorg evdev driver catch all input events and rfkill_input do
not see them anymore when under X.
If I switch in console
Adding:
options rfkill default_state=0
in:
/etc/modprobe.d/options
Should disable the wifi transmitter at boot time (in fact when the
rfkill module loads).
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrepid Alpha 1)
For me, if the kernel patch proposed in bug #232170 is applied this
package should be removed at all.
--
eeepc-acpi-scripts is not installable
https://bugs.launchpad.net/bugs/262679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Echoing 0/1 to /sys/class/rfkill/rfkill0/state works. Not the key itself.
Any advice if I should look in the eeepc-laptop module or in some keyboard
configuration stuff ?
That said it's fun to see that without the eeepc-laptop module loaded,
the FN+F2 key works out of the box. Other keys do not
I found the problem; but from latest xorg developments, it does not seem
to be easily solved:
http://lists.freedesktop.org/archives/xorg/2008-August/037728.html
In fact the wireless hotkey is working well when used in console mode,
but when xorg with evdev is launched, it prevents rfkill_input to
After some more tests, the display button works well, and emits
XF86Display event which is OK (except that if you do not bind this key
to some desktop events, it is used a volume up).
So, Mattew's patch is working well on a eeepc 701, given that you tweak a
little bit you modules:
- load pciehp
Following Sitsofe suggestion, I tried Matthew's patch on my eeepc 701.
At least, I get the volume keys working.
I still have issues with the wireless and display one; that needs some
investigations.
I also noticed that this patch activates the wifi card when loaded.
--
EeePC Volume and
Current problems (still need further investigations):
- Display button make the volume to go up. Maybe a bad key configuration
somewhere.
- Wireless button does not do anything; wireless is turned on when the module
is loaded but nothing happens when I press the toggle off button. And yes, I'm
For some ACPI hotkeys, the eeepc does not emit standards codes and in
that case needs specific ACPI events mapping (that for some of them
overlaps with standard/common one).
Also, for some actions triggered by ACPI events, there are some specific
scripts to be run, like for example the wireless
My computer was not updated with backports.
I tried it and it works well. Thanks.
--
Lack of a small gui version
https://bugs.launchpad.net/bugs/255323
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: wesnoth
Since development version 1.3.17, wesnoth includes a compilation flag
that allows small GUI (reduced user interface for small devices).
This option had been added to allow users to play wesnoth on devices
like the Asus EEEPC.
A simple fix for
Same problem with gthumb.
Latest svn revision added the following mime types to the gthumb.desktop file:
x-content/image-dcf
x-content/image-picturecd
--
[hardy] media tab in file management preferences missing applications
https://bugs.launchpad.net/bugs/191475
You received this bug
Public bug reported:
Binary package hint: gthumb
Ubuntu Release: Ubuntu 8.04.1
Package version: 3:2.10.8-0ubuntu1
Short problem:
Importing photos when I insert an USB mass storage media does not shows me
gthumb as an import option.
What I expect:
If I open a nautilus window, and go to
I got also some troubles today once updating my fresh Hardy
installation.
First step, I made to resolve this issue is to install Python 2.4.
It seems pycentral crashes if a packages specify a python version that is not
installed.
After that I got an error when trying to update jockey-common.
Nobu, did you installed python 2.4 ?
apt-get install python2.4
this will solve: AttributeError: 'NoneType' object has no attribute
'byte_compile'
Next, apply my patch to your pycentral.
--
[hardy] pycentral crashed with ValueError in parse_versions()
https://bugs.launchpad.net/bugs/192992
Public bug reported:
Binary package hint: simple-ccsm
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu hardy (development branch)
simple-ccsm package: 0.6.99+git20080112-0ubuntu1
The simple-ccsm package should add a dependency on the ccsm package
since
It seems this can be resolved by removing the @euro from your locale.
For example, launch k3b with the following command line:
LANG=it_IT.UTF-8 k3b
--
Text encoding inconsistency
https://bugs.launchpad.net/bugs/43244
You received this bug notification because you are a member of Ubuntu
Bugs,
olor_url = "006792";
google_color_text = "00";
//-->
[Bug 262679] Re: eeepc-acpi-scripts is not installable
Olivier Samyn
Reply via email to
<!--
google_ad_client = "pub-7266757337600734";
43 matches
Mail list logo
