From: MINAMI H. <mi...@mi...> - 2005-03-10 03:25:04
|
On Wed, Mar 09, 2005 at 04:30:11PM +0100, Mike FABIAN wrote: > Mike FABIAN <mf...@su...> =E3=81=95=E3=82=93=E3=81=AF=E6=9B=B8=E3=81= =8D=E3=81=BE=E3=81=97=E3=81=9F: >=20 > >> Hmm, I could reproduce the problem on -depth=3D8 but not on -depth=3D= 24. > > > > I use -depth=3D16. > > > >> Are you running X in 256 color mode? > > > >> and how did you set your root pixmap? > > > > display -geometry 1600x1200 -window root ~/pic/20040530-150954.jpg >=20 > I switched to useing -depth=3D24 but that doesn't make a difference, > the error message remains: Thanks, I understand what's hpenning. With gdk-pixbuf, mlterm only see _XROOTPMAP_ID for root pixmap since it had seemed to be the de-facto standard for me. If I understanding correctly, both of GNOME and KDE use the property. However, some applications are still using different ones like ESETROOT_PMAP_ID or XSETROOT_ID. Maybe "display" is one of them and mlterm+gdk-pixbuf currently do not work well with it. In the mlterm's imlib support module, there is a hack to grab root window's image in such cases. Though the same trick also had ben used in the gdk-pixbuf module, I've dropped it 2 years ago since such effort is not necessary if _XROOTPMAP_ID was correctly set and glabing X server may stop screen update noticeably long(up to 0.5[s]). Would you try to set a wallpaper by another one? ex. "fvwm-root" should work according to its manpage. It should also be possible to investigate how "display" works but I don't have enough motovation/time fo now... minami |