Re: FVWM: Bad Icon bitmap depth
Olivier Chapuis [EMAIL PROTECTED] in a message dated Mon, 26 May 2003 01:39:05 -0600 dubiously asserts... On Thu, May 22, 2003 at 10:47:36AM -0600, Sean Seery wrote: [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. I think I've the solution of the problem (I read all the others mail of this thread). Sean has a 8/24 depth screen and the X server start with DefaultDepth = 8. This is a classical situation (the X server can be configured to start with DefaultDepth = 24, but as certain old apps need depth 8 for read- write colours the default is depth 8; moreover on such hardware there is no visual pbs by using certain app under depth 8 and other with depth 24). BTW, since 2.5.6 fvwm detect this situation and fvwm choose to use the best visual: TrueColor depth 24 (before 2.5.6 the user had to use the --visual-id or --visual option; now fvwm need _no_ option). A lot of apps use this logic too. So, for applications supplied icon pixmap we have 3 acceptable depth: - depth 1 (always ok) - depth 8, the default depth - depth 24, the fvwm depth I've just committed a fix. Sean can you try the next fvwm snapshot? I have downloaded and compiled the snapshot and it does fix the problem. Thanks so much for everyones help on this problem! ftp://ftp.fvwm.org/pub/fvwm/devel/snapshots/fvwm-snap-20030526.tar.gz Thanks, Sean -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
On Mon, May 26, 2003 at 09:42:55AM +0200, Olivier Chapuis wrote: On Thu, May 22, 2003 at 10:47:36AM -0600, Sean Seery wrote: Hello, I cannot seem to figure this out so here is my plaintive cry for help: How do I get fvwm to support bitmaps with a depth of 24? Every time that I minimize an application w/such an icon(such as mozilla), fvwm spits out the following error: [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. I think I've the solution of the problem (I read all the others mail of this thread). Sean has a 8/24 depth screen and the X server start with DefaultDepth = 8. This is a classical situation (the X server can be configured to start with DefaultDepth = 24, but as certain old apps need depth 8 for read- write colours the default is depth 8; moreover on such hardware there is no visual pbs by using certain app under depth 8 and other with depth 24). BTW, since 2.5.6 fvwm detect this situation and fvwm choose to use the best visual: TrueColor depth 24 (before 2.5.6 the user had to use the --visual-id or --visual option; now fvwm need _no_ option). A lot of apps use this logic too. So, for applications supplied icon pixmap we have 3 acceptable depth: - depth 1 (always ok) - depth 8, the default depth - depth 24, the fvwm depth I've just committed a fix. Cool. Can you backport the fix to 2.4.16 too? It looks fairly simple, but I'm not sure I would catch all places I have to touch to make the patch myself. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
On Mon, May 26, 2003 at 09:50:26AM +0200, Dominik Vogt wrote: On Mon, May 26, 2003 at 09:42:55AM +0200, Olivier Chapuis wrote: On Thu, May 22, 2003 at 10:47:36AM -0600, Sean Seery wrote: Hello, I cannot seem to figure this out so here is my plaintive cry for help: How do I get fvwm to support bitmaps with a depth of 24? Every time that I minimize an application w/such an icon(such as mozilla), fvwm spits out the following error: [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. I think I've the solution of the problem (I read all the others mail of this thread). Sean has a 8/24 depth screen and the X server start with DefaultDepth = 8. This is a classical situation (the X server can be configured to start with DefaultDepth = 24, but as certain old apps need depth 8 for read- write colours the default is depth 8; moreover on such hardware there is no visual pbs by using certain app under depth 8 and other with depth 24). BTW, since 2.5.6 fvwm detect this situation and fvwm choose to use the best visual: TrueColor depth 24 (before 2.5.6 the user had to use the --visual-id or --visual option; now fvwm need _no_ option). A lot of apps use this logic too. So, for applications supplied icon pixmap we have 3 acceptable depth: - depth 1 (always ok) - depth 8, the default depth - depth 24, the fvwm depth I've just committed a fix. Cool. Can you backport the fix to 2.4.16 too? It looks fairly simple, but I'm not sure I would catch all places I have to touch to make the patch myself. Ok. But I do not think I should also backport the autodetection of the best visual on such hardware. What do you think? Regrads, Olivier -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
On Mon, May 26, 2003 at 11:43:44AM +0200, Olivier Chapuis wrote: On Mon, May 26, 2003 at 09:50:26AM +0200, Dominik Vogt wrote: On Mon, May 26, 2003 at 09:42:55AM +0200, Olivier Chapuis wrote: On Thu, May 22, 2003 at 10:47:36AM -0600, Sean Seery wrote: Hello, I cannot seem to figure this out so here is my plaintive cry for help: How do I get fvwm to support bitmaps with a depth of 24? Every time that I minimize an application w/such an icon(such as mozilla), fvwm spits out the following error: [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. I think I've the solution of the problem (I read all the others mail of this thread). Sean has a 8/24 depth screen and the X server start with DefaultDepth = 8. This is a classical situation (the X server can be configured to start with DefaultDepth = 24, but as certain old apps need depth 8 for read- write colours the default is depth 8; moreover on such hardware there is no visual pbs by using certain app under depth 8 and other with depth 24). BTW, since 2.5.6 fvwm detect this situation and fvwm choose to use the best visual: TrueColor depth 24 (before 2.5.6 the user had to use the --visual-id or --visual option; now fvwm need _no_ option). A lot of apps use this logic too. So, for applications supplied icon pixmap we have 3 acceptable depth: - depth 1 (always ok) - depth 8, the default depth - depth 24, the fvwm depth I've just committed a fix. Cool. Can you backport the fix to 2.4.16 too? It looks fairly simple, but I'm not sure I would catch all places I have to touch to make the patch myself. Ok. But I do not think I should also backport the autodetection of the best visual on such hardware. What do you think? No, I'd only backport the bug fixes. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
On 16:49 24 May 2003, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: | Forget what I said earlier., I did not look carefully at what you | wrote: | | visual id:0x2b | class:DirectColor | depth:24 planes | available colormap entries:256 per subfield | red, green, blue masks:0xff, 0xff00, 0xff | significant bits in color specification:8 bits | | So, xdpyinfo claims the display has 24 bit planes but unly 8 | bitplanes can be used to specify colours? That is strange indeed. | Fvwm uses the display's default depth, which is 8 on your system. | Yet, your X server tells the applications that they can use 24 | bits. I have no idea what this could mean. It may be a bug in | the X server. Hmm. No, this is saying he has a 24 bit display where each colour component is 8 bits deep. Which is normal. -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ The more I ride the more I notice and the more fearful I become - somebody on rec.moto -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
On Sun, May 25, 2003 at 05:59:21PM +1000, Cameron Simpson wrote: On 16:49 24 May 2003, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: | Forget what I said earlier., I did not look carefully at what you | wrote: | | visual id:0x2b | class:DirectColor | depth:24 planes | available colormap entries:256 per subfield | red, green, blue masks:0xff, 0xff00, 0xff | significant bits in color specification:8 bits | | So, xdpyinfo claims the display has 24 bit planes but unly 8 | bitplanes can be used to specify colours? That is strange indeed. | Fvwm uses the display's default depth, which is 8 on your system. | Yet, your X server tells the applications that they can use 24 | bits. I have no idea what this could mean. It may be a bug in | the X server. Hmm. No, this is saying he has a 24 bit display where each colour component is 8 bits deep. Which is normal. Ah, I see. Still, the error message Sean got claims that the root window has only 8 bitplanes: [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. ^^^ This number was returned by DefaultDepth(dpy,Scr.screen) The DefaultDepth macro returns the depth of the root window of a specific screen. In any case, I think that a) It's a bug in the application(s), and b) Posting the full output of xdpyinfo might help to resolve the problem. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
On Fri, May 23, 2003 at 09:22:00AM -0600, Sean Seery wrote: Dominik Vogt fvwm@fvwm.org in a message dated Fri, 23 May 2003 01:07:19 -0600 dubiously asserts... Dominik, [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. You can do little about it. The application is specifying an icon with 24 bitplanes, but your display has only 8 bitplanes. Fvwm copies the pixmap into the window's icon window which of course uses only 8 bitplanes. Thanks for getting back to me. It appears that I am out of luck... or am I? If I understand what you are saying, the icon window is limited to a depth of 8. Is this a limitation of the video card/monitor or fvwm itself? Replacing the monitor/video card is not horribly difficult... Forget what I said earlier., I did not look carefully at what you wrote: visual id:0x2b class:DirectColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits So, xdpyinfo claims the display has 24 bit planes but unly 8 bitplanes can be used to specify colours? That is strange indeed. Fvwm uses the display's default depth, which is 8 on your system. Yet, your X server tells the applications that they can use 24 bits. I have no idea what this could mean. It may be a bug in the X server. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
Sean Seery [EMAIL PROTECTED] writes: Hello, I cannot seem to figure this out so here is my plaintive cry for help: How do I get fvwm to support bitmaps with a depth of 24? Every time that I minimize an application w/such an icon(such as mozilla), fvwm spits out the following error: [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. I've also tried experimenting w/the -I option setting the visual-id but that appears not to have made a difference... It appears that in a brief, inexperienced perusal of the source code that this value is determined by something in XWMHints... I can't seem to find any information other than a man page on XWMHints. Any help would be appreciated. Some pertinent information: Solaris 8 fvwm 2.5.6 compiled on May 21 2003 at 08:12:32 with support for: XPM, PNG, Shape, XShm, SM, NLS xdpyinfo:(truncated...) name of display:fletch:0.0 version number:11.0 vendor string:Sun Microsystems, Inc. vendor release number:6410 maximum request size: 262140 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, MSBFirst, 32 image byte order:MSBFirst number of supported pixmap formats:3 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 132 focus: window 0x8d, revert to Parent Here is the vis-id's I attempted to use: visual id:0x2b class:DirectColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits visual id:0x2d class:TrueColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits There is a part of the output that shows the depth of the root window. What is it set to? Maybe you should just post the whole thing. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
On Thu, May 22, 2003 at 10:47:36AM -0600, Sean Seery wrote: Hello, I cannot seem to figure this out so here is my plaintive cry for help: How do I get fvwm to support bitmaps with a depth of 24? Every time that I minimize an application w/such an icon(such as mozilla), fvwm spits out the following error: [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. You can do little about it. The application is specifying an icon with 24 bitplanes, but your display has only 8 bitplanes. Fvwm copies the pixmap into the window's icon window which of course uses only 8 bitplanes. I've also tried experimenting w/the -I option setting the visual-id but that appears not to have made a difference... It appears that in a brief, inexperienced perusal of the source code that this value is determined by something in XWMHints... I can't seem to find any information other than a man page on XWMHints. Any help would be appreciated. Some pertinent information: Solaris 8 fvwm 2.5.6 compiled on May 21 2003 at 08:12:32 with support for: XPM, PNG, Shape, XShm, SM, NLS xdpyinfo:(truncated...) name of display:fletch:0.0 version number:11.0 vendor string:Sun Microsystems, Inc. vendor release number:6410 maximum request size: 262140 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, MSBFirst, 32 image byte order:MSBFirst number of supported pixmap formats:3 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 132 focus: window 0x8d, revert to Parent Here is the vis-id's I attempted to use: visual id:0x2b class:DirectColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits visual id:0x2d class:TrueColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Bad Icon bitmap depth
Dominik Vogt fvwm@fvwm.org in a message dated Fri, 23 May 2003 01:07:19 -0600 dubiously asserts... Dominik, [FVWM][GetIconBitmap]: ERROR Window 'some window' has a bad icon bitmap depth 24(should be 1 or 8)! Ignoring icon bitmap. You can do little about it. The application is specifying an icon with 24 bitplanes, but your display has only 8 bitplanes. Fvwm copies the pixmap into the window's icon window which of course uses only 8 bitplanes. Thanks for getting back to me. It appears that I am out of luck... or am I? If I understand what you are saying, the icon window is limited to a depth of 8. Is this a limitation of the video card/monitor or fvwm itself? Replacing the monitor/video card is not horribly difficult... Thanks, Sean -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
