Bug#444826: [Fwd: synaptic feast]

[William Montreal]

Package: SLAPD, libgnome32, libgtk1.2

---


--- Begin Message ---
Synaptic wasn't in the list of the bug report utility so I had to use
the email.  I don't know whom is the fault but I had a few packages
still marked even after I applied the changes.  I was getting tired of
seeing the same errors at each installation os I tried removiong the
faulty packages and now I'm stuck with an even biger problem !  more of
them listed and even 2 broken packages ...  mostly related to gnome.

So to start off I had 3 packages and now I got a dozen, the original
were SLAPD, and 2 gnome librairies in which the only recongnised
dependency were WineX.

I have some text pop up in a console when the same error pops up after
applying changes which is  BREAKING NEWS ! while tring to get the list I
conldn't because of the broken ones and now I'm back to the original
culprits which give me this error :

E: /cdrom//pool/main/g/gtk+1.2/libgtk1.2-common_1.2.10-18_all.deb:
subprocess pre-installation script returned error exit status 2
E: /cdrom//pool/main/g/gtk+1.2/libgtk1.2_1.2.10-18_amd64.deb: subprocess
new post-removal script returned error exit status 2
E: 
/cdrom//pool/main/l/linux-2.6/linux-image-2.6.18-5-amd64_2.6.18.dfsg.1-13_amd64.deb:
 subprocess new pre-removal script returned error exit status 2
E: /cdrom//pool/main/o/openldap2.3/slapd_2.3.30-5_amd64.deb: subprocess
pre-installation script returned error exit status 2
E: /cdrom//pool/main/i/imlib/gdk-imlib11_1.9.14-31_amd64.deb: subprocess
new post-removal script returned error exit status 2
E: /cdrom//pool/main/g/gnome-libs/libgnome32_1.4.2-34_amd64.deb:
subprocess pre-installation script returned error exit status 2
E: /cdrom//pool/main/g/gnome-libs/libgnomesupport0_1.4.2-34_amd64.deb:
subprocess new post-removal script returned error exit status 2
E: /cdrom//pool/main/g/gnome-libs/libgnomeui32_1.4.2-34_amd64.deb:
subprocess new post-removal script returned error exit status 2
E: /cdrom//pool/main/g/gnome-libs/libgnorba27_1.4.2-34_amd64.deb:
subprocess new post-removal script returned error exit status 2
E: /cdrom//pool/main/g/gnome-libs/libgnorbagtk0_1.4.2-34_amd64.deb:
subprocess new post-removal script returned error exit status 2
E: /cdrom//pool/main/g/gnome-libs/gnome-libs-data_1.4.2-34_all.deb:
subprocess new post-removal script returned error exit status 2
E: /cdrom//pool/main/s/supertux/supertux_0.1.3-1.1_amd64.deb: subprocess
new post-removal script returned error exit status 2

--- End Message ---

Bug#286644: x2x: AltGr characters not getting through

[Lucas Nussbaum]

On 21/12/04 at 11:35 +0200, era eriksson wrote:
> Package: x2x
> Version: 1.27-8
> Severity: normal
> 
> I'm running x2x over to a Woody system and it works wonderfully apart
> from one thing: on my Finnish keyboard, characters such as '|' and '\'
> are typed with AltGr, and this doesn't work on the remote desktop.
> Instead, I get the unshifted characters, i.e. AltGr+'<' produces just
> '<' instead of the expected '|'. On the local display, this works as
> expected.
> 
> Here's the command I'm using:
> 
>  bash$ ssh -f -X remotehost x2x -east -to $DISPLAY
> 
> x2x over on the Woody box is 1.27-5.1 -- if upgrading to a newer
> version fixes this, it's not advertised in the changelog.
> 
> Running xev on the remote system, I can see that other shift keys are
> transferred correctly, but pressing AltGr doesn't result in anything
> at all in xev. (Locally, I get this:
> 
> KeyPress event, serial 23, synthetic NO, window 0x501,
> root 0x3b, subw 0x0, time 86116041, (140,105), root:(1556,976),
> state 0x0, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
> XLookupString gives 0 bytes:  ""
> 
> KeyRelease event, serial 28, synthetic NO, window 0x501,
> root 0x3b, subw 0x0, time 86120867, (140,104), root:(1556,975),
> state 0x80, keycode 113 (keysym 0xfe03, ISO_Level3_Shift), same_screen 
> YES,
> XLookupString gives 0 bytes:  ""
> 
>  which looks okay to me, although on the other display, if I type
> AltGr on the local keyboard, xev says this instead:
> 
> KeyPress event, serial 23, synthetic NO, window 0x401,
> root 0x31, subw 0x0, time 4108957447, (73,108), root:(593,571),
> state 0x0, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES,
> XLookupString gives 0 characters:  ""
> 
> KeyRelease event, serial 28, synthetic NO, window 0x401,
> root 0x31, subw 0x0, time 4108960807, (73,108), root:(593,571),
> state 0x2000, keycode 113 (keysym 0xff7e, Mode_switch), same_screen YES,
> XLookupString gives 0 characters:  ""
> 
> Should I somehow attempt to unify the discrepancy, i.e. configure the
> Woody X server to generate ISO_Level3_Shift instead, or vice versa?
> Can I do that with xmodmap even though it doesn't even seem to
> register the keypress currently?)
> 
> I imagine this is related to #256857 but my understanding of how X
> manages keypresses is limited.

Hi era,

can you still reproduce that problem ?

It works fine for me (but I use a french keyboard, not a finnish one).
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]