Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-13 Thread Attilio Fiandrotti

Holger Wansing wrote:

Hi,

On Thu, 07 Jun 2007 21:33:55 +0200 Attilio Fiandrotti wrote:
I'm aware we had problems like that before, but we addressed them by 
switching to linux_input before.
Moreover i wonder why this bug doesn't show up when booting with 
expertgui, as Holger reported.


I'm sorry, I have to corrrect myself:
some more investigation has shown, that the expertgui
boot method wasn't the reason for the keymap beeing ok,
but another queery thing:
When you try to switch to another terminal (with Ctrl-Alt-Fx),
this doesn't work (I have already reported this), but after
the failed attempt the keymap is correct! 
Huh?


Holger, you said switching to a different VT (with Ctrl-Alt-Fx) this 
doesn't work, right ? but was this tested on i386 or x86 ?


In the latter case, that's a known issue, but i never heard f vt 
switching broken on i386.

Could you please specify which architecture you're referring to?

thanks

Attilio


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



Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-13 Thread Frans Pop
On Wednesday 13 June 2007 10:27, Attilio Fiandrotti wrote:
 Holger, you said switching to a different VT (with Ctrl-Alt-Fx) this
 doesn't work, right ? but was this tested on i386 or x86 ?

s/x86/amd64/

 In the latter case, that's a known issue, but i never heard f vt
 switching broken on i386.

It was broken on i386 this time.
I have just checked and the same workaround we already had for in place 
for amd64 is now also required for i386. I have committed the necessary 
changes. It would be nice if somebody could check if it is needed for 
powerpc as well.


The German keyboard issue is unrelated. With VT switching fixed I have 
been able to check that the keyboard _is_ correct in the shell on VT2 and 
VT3, so it looks like the keymap reloading for directfb is broken 
somehow. If I check VT1, the messages about keymap reloading are indeed 
missing; these messages are displayed if I test with an Etch image.

Attilio: it would be great if you could look into this.


pgpBK3LRo7hxJ.pgp
Description: PGP signature


Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-13 Thread Attilio Fiandrotti

Frans Pop wrote:

On Wednesday 13 June 2007 10:27, Attilio Fiandrotti wrote:

Holger, you said switching to a different VT (with Ctrl-Alt-Fx) this
doesn't work, right ? but was this tested on i386 or x86 ?


s/x86/amd64/


Indeed, i was menaing amd64, not x86, sorry..


In the latter case, that's a known issue, but i never heard f vt
switching broken on i386.


It was broken on i386 this time.
I have just checked and the same workaround we already had for in place 
for amd64 is now also required for i386. I have committed the necessary 
changes. It would be nice if somebody could check if it is needed for 
powerpc as well.


So, i assume something has changed after etch release which requires 
libgcc on i386 too, right?


The German keyboard issue is unrelated. With VT switching fixed I have 
been able to check that the keyboard _is_ correct in the shell on VT2 and 
VT3, so it looks like the keymap reloading for directfb is broken 
somehow. If I check VT1, the messages about keymap reloading are indeed 
missing; these messages are displayed if I test with an Etch image.


Attilio: it would be great if you could look into this.


So, again something has changed after etch release, which now prevents 
keyboard reloading (which instead worked in etch) from working: any clue 
about what it may be ?


regards

Attilio


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



Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-13 Thread Frans Pop
On Wednesday 13 June 2007 13:22, Attilio Fiandrotti wrote:
 So, i assume something has changed after etch release which requires
 libgcc on i386 too, right?

Yes. No idea exactly what, but I suspect gcc. directfb itself has had an 
upload after Etch, but that included only minor changes.
I doubt it is really worthwhile to investigate exactly what changed.

  The German keyboard issue is unrelated.

 So, again something has changed after etch release, which now prevents
 keyboard reloading (which instead worked in etch) from working: any
 clue about what it may be ?

Nope. It is nothing in D-I itself. directfb seems unlikely too.
This one is all yours.


pgp6migTN1Np7.pgp
Description: PGP signature


Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-13 Thread Attilio Fiandrotti

tags 427657 patch
retitle 427657 Crash at VT switch in Etch and keymap not reloaded in Lenny
thanks

Frans Pop wrote:

On Wednesday 13 June 2007 13:22, Attilio Fiandrotti wrote:

So, i assume something has changed after etch release which requires
libgcc on i386 too, right?


Yes. No idea exactly what, but I suspect gcc. directfb itself has had an 
upload after Etch, but that included only minor changes.

I doubt it is really worthwhile to investigate exactly what changed.


The German keyboard issue is unrelated.



So, again something has changed after etch release, which now prevents
keyboard reloading (which instead worked in etch) from working: any
clue about what it may be ?


Nope. It is nothing in D-I itself. directfb seems unlikely too.
This one is all yours.


I built to i386 installers (build_netboot_gtk target) from svn trunk 
and etch branch, patching both the vt crash and the keymap bugs, see below


regards

Attilio

1) *Etch installer*
- Keymap bug is not reproducible (italian keymap works perfectly)

- VT crash bug is reproducible, the patch consists in providing 
libgcc.so.1 via EXTRAFILES, like we did for amd64 previously (i suspect 
also PPC may need this workaround)


2) *Lenny installer*
- Keymap bug is reproducible: because in lenny we use gtk 2.10.x (2.8.x 
is instead used in etch) and GDK_WINDOWING_DIRECTFB is not defined, and 
because of the #ifdef's i removed in the attached patch, the code which 
reloads the keymap is no longer built into the gtk frontend, which 
consequently doesn't reload the keymap.

The attached patch should be commited in trunk only.

-VT crash bug is not reproducible because libgcc is already provided in 
lenny installer by some udeb
Index: cdebconf/src/modules/frontend/gtk/gtk.c
===
--- cdebconf/src/modules/frontend/gtk/gtk.c	(revisione 47245)
+++ cdebconf/src/modules/frontend/gtk/gtk.c	(copia locale)
@@ -49,13 +49,7 @@
 #include debian-installer/slist.h
 #include gdk/gdkkeysyms.h
 
-#if GTK_CHECK_VERSION(2,10,0)
-#ifdef GDK_WINDOWING_DIRECTFB
 #include directfb.h
-#endif
-#else
-#include directfb.h
-#endif
 
 #define WINDOW_WIDTH 800
 #define WINDOW_HEIGHT 600
@@ -1493,14 +1487,7 @@
  * for dfb to support automatic keymap change detection and reloading
  * (See also bug #381979)
  */
-
-#if GTK_CHECK_VERSION(2,10,0)
-#ifdef GDK_WINDOWING_DIRECTFB
 dfb_input_device_reload_keymap( dfb_input_device_at( DIDID_KEYBOARD ) );
-#endif
-#else
-dfb_input_device_reload_keymap( dfb_input_device_at( DIDID_KEYBOARD ) );
-#endif
 
 gtk_rc_reparse_all();
 


Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-13 Thread Frans Pop
On Wednesday 13 June 2007 16:16, Attilio Fiandrotti wrote:
 2) *Lenny installer*
 - Keymap bug is reproducible: because in lenny we use gtk 2.10.x (2.8.x
 is instead used in etch) and GDK_WINDOWING_DIRECTFB is not defined

Great. I'll commit the patch and upload.

 -VT crash bug is not reproducible because libgcc is already provided in
 lenny installer by some udeb

No, that is not correct. I added the EXTRAFILES workaround for i386 too. 
It is currently not provided by a udeb.


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



Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-13 Thread Attilio Fiandrotti

Frans Pop wrote:

On Wednesday 13 June 2007 16:16, Attilio Fiandrotti wrote:

2) *Lenny installer*
- Keymap bug is reproducible: because in lenny we use gtk 2.10.x (2.8.x
is instead used in etch) and GDK_WINDOWING_DIRECTFB is not defined


Great. I'll commit the patch and upload.


ok


-VT crash bug is not reproducible because libgcc is already provided in
lenny installer by some udeb


No, that is not correct. I added the EXTRAFILES workaround for i386 too. 
It is currently not provided by a udeb.


ah ok, i didn't know that, but do you confirm now also etch needs the 
EXTRAFILES workaround for i386 (and possibly powerpc) too?


Attilio



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



Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-13 Thread Frans Pop
On Wednesday 13 June 2007 17:15, Attilio Fiandrotti wrote:
 ah ok, i didn't know that, but do you confirm now also etch needs the
 EXTRAFILES workaround for i386 (and possibly powerpc) too?

No, I don't see why Etch would need it. Only unstable/lenny.
It is quite likely that powerpc needs it too.

I plan to discuss what to do about this lib with some people at debconf. 
Still not completely sure if we really want to add this lib or not. First 
it is 41k and I don't think we could reduce the lib. Also, it would be 
the first udeb for the gcc-4.2 and as having a udeb does complicate 
migrations for any source package, I'm rather reluctant to request that 
for something as big as gcc unless it is really needed.


pgp7dPGlo3V7r.pgp
Description: PGP signature


Re: Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-11 Thread Holger Wansing
Hi,

On Thu, 07 Jun 2007 21:33:55 +0200 Attilio Fiandrotti wrote:
 I'm aware we had problems like that before, but we addressed them by 
 switching to linux_input before.
 Moreover i wonder why this bug doesn't show up when booting with 
 expertgui, as Holger reported.

I'm sorry, I have to corrrect myself:
some more investigation has shown, that the expertgui
boot method wasn't the reason for the keymap beeing ok,
but another queery thing:
When you try to switch to another terminal (with Ctrl-Alt-Fx),
this doesn't work (I have already reported this), but after
the failed attempt the keymap is correct! 
Huh?



-- 
Kind regards
Holger

==
Created with Sylpheed 2.3.0
under THE NEW DEBIAN GNU/LINUX 4.0 »Etch«
http://counter.li.org/,  Registered LinuxUser #311290
Try out OpenGL 3D-Desktop Beryl! www.beryl-project.org
=


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



Re: Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-07 Thread Christian Perrier
reassign 427657 cdebconf-gtk-udeb
thanks

I just reproduced that bug with g-i but I can't reproduce it with D-I.

It is not limited to the german keymap. The same hapens with the
French one.




signature.asc
Description: Digital signature


Processed: Re: Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-07 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 427657 cdebconf-gtk-udeb
Bug#427657: wrong keyboard at gui install
Bug reassigned from package `console-data' to `cdebconf-gtk-udeb'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#427657: Processed: Re: Bug#427657: wrong keyboard at gui install

2007-06-07 Thread Attilio Fiandrotti

Christian Perrier wrote:

reassign 427657 cdebconf-gtk-udeb
thanks

I just reproduced that bug with g-i but I can't reproduce it with D-I.

It is not limited to the german keymap. The same hapens with the
French one.




I'm aware we had problems like that before, but we addressed them by 
switching to linux_input before.
Moreover i wonder why this bug doesn't show up when booting with 
expertgui, as Holger reported.


Attilio


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