-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan,
This just occured to me When I had beta3 installed and just
before RC1 came out qt3 and lib1t3 where upgraded. Let me see if my
older disks are anywhere around... (slim chance) but just about that
time my ability to launch kde3
On Wednesday 19 March 2003 06:07 am, Jan Ciger wrote:
Jan,
This just occured to me When I had beta3 installed and just
before RC1 came out qt3 and lib1t3 where upgraded. Let me see if my
older disks are anywhere around... (slim chance) but just about that
time my ability to
Greg Meyer wrote:
On Wednesday 19 March 2003 06:07 am, Jan Ciger wrote:
Jan,
This just occured to me When I had beta3 installed and just
before RC1 came out qt3 and lib1t3 where upgraded. Let me see if my
older disks are anywhere around... (slim chance) but just about that
time my
On Wednesday 19 March 2003 10:25 am, scott chevalley wrote:
I'll ask again then. Should this be reported upstream? I didn't see
anything about this in the KDE bugzilla. I did not check trolltech.
It wasn't a kde problem... a patch was applied to libqt3 between 12mdk
and 13mdk that
On Wednesday 19 March 2003 10:44 am, Frederic Crozat wrote:
It wasn't a kde problem... a patch was applied to libqt3 between 12mdk
and 13mdk that forces the use of AA fonts, which will fail if the Render
extension is not present. There's a link in a previous message that
points to a
On Wednesday 19 March 2003 11:12 am, Frederic Crozat wrote:
On Wed, 19 Mar 2003 11:08:23 -0500, Greg Meyer wrote:
On Wednesday 19 March 2003 10:44 am, Frederic Crozat wrote:
It wasn't a kde problem... a patch was applied to libqt3 between 12mdk
and 13mdk that forces the use of AA fonts,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 19 March 2003 11:47 am, Greg Meyer wrote:
On Wednesday 19 March 2003 11:12 am, Frederic Crozat wrote:
On Wed, 19 Mar 2003 11:08:23 -0500, Greg Meyer wrote:
On Wednesday 19 March 2003 10:44 am, Frederic Crozat wrote:
It wasn't a
On Wednesday 19 March 2003 12:05 pm, Gary Greene wrote:
I know, and I don't mean to be rude. I am willing to report this
upstream, I just would like someone from MandrakeSoft to let me know if
this is desireable, or if it is better handled through official
channels since it affects the
Greg Meyer wrote:
On Wednesday 19 March 2003 12:05 pm, Gary Greene wrote:
I know, and I don't mean to be rude. I am willing to report this
upstream, I just would like someone from MandrakeSoft to let me know if
this is desireable, or if it is better handled through official
channels since it
Am Montag, 17. März 2003, 15:31:41 Uhr MET, schrieb Jesse Wagner:
On Mon, 17 Mar 2003 15:02:33 +0100, Götz Waschk
Would you happen to have a changelog for this release of nautilus/GNOME?
Yes, but I'm not google. Take a look at the gnome web site.
--
Götz Waschk master of computer science
On Tue, 18 Mar 2003 09:11:06 +0100, Götz Waschk
[EMAIL PROTECTED] said:
Am Montag, 17. März 2003, 15:31:41 Uhr MET, schrieb Jesse Wagner:
On Mon, 17 Mar 2003 15:02:33 +0100, Götz Waschk
Would you happen to have a changelog for this release of nautilus/GNOME?
Yes, but I'm not google. Take a
Am Dienstag, 18. März 2003, 03:26:10 Uhr MET, schrieb Jesse Wagner:
Yea, I tried that. And I tried google. No such luck.
So you were afraid of downloading the tarballs? The source is also
browsable through the web-CVS of gnome.
From the NEWS file of eel:
This is eel 2.2.2. It is part of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don't you want to try a Qt-only app on GNOME to confirm? mysqlcc or
qcad or something else qt-only should do.
Just tried a pure qt app in an Xnested Fluxbox and it segfaults. The
same app runs fine in gnome:
$ ./qttest
Xlib: extension
On Tuesday 18 March 2003 07:00 am, Jan Ciger wrote:
Don't you want to try a Qt-only app on GNOME to confirm? mysqlcc or
qcad or something else qt-only should do.
Just tried a pure qt app in an Xnested Fluxbox and it segfaults. The
same app runs fine in gnome:
$ ./qttest
I just checked the sources of Gnome 2.2.1 and noticed the March 15, 2003
timestamps (ftp.gnome.org/pub/gnome/desktop/2.2/2.2.1/sources/).
Although I'd like to see Mandrake be the first distro of Gnome v2.2.1 in the
next v9.1, would the wait for the Mandrake v9.1 release be worth it include
Jan Ciger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don't you want to try a Qt-only app on GNOME to confirm? mysqlcc or
qcad or something else qt-only should do.
Just tried a pure qt app in an Xnested Fluxbox and it segfaults. The
same app runs fine in gnome:
$ ./qttest
On Tue, 2003-03-18 at 04:00, Jan Ciger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don't you want to try a Qt-only app on GNOME to confirm? mysqlcc or
qcad or something else qt-only should do.
Just tried a pure qt app in an Xnested Fluxbox and it segfaults. The
same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
G?tz Waschk wrote on Tue, Mar 18, 2003 at 12:46:21PM +0100 :
Yea, I tried that. And I tried google. No such luck.
So you were afraid of downloading the tarballs? The source is also
browsable through the web-CVS of gnome.
From the NEWS file of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan,
I get the same thing here in a regular window (ie my desktop)
anti-aliasing etc is working fine. But only in vnc or Xnest do the qt
applications give this kind of error. Same version of vnc in 9.0 works
fine. So I don't suspect vnc.
On Tue, 2003-03-18 at 04:33, Greg Meyer wrote:
On Tuesday 18 March 2003 07:00 am, Jan Ciger wrote:
Don't you want to try a Qt-only app on GNOME to confirm? mysqlcc or
qcad or something else qt-only should do.
Just tried a pure qt app in an Xnested Fluxbox and it segfaults. The
Jan Ciger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan,
I get the same thing here in a regular window (ie my desktop)
anti-aliasing etc is working fine. But only in vnc or Xnest do the qt
applications give this kind of error. Same version of vnc in 9.0 works
fine. So I don't
On Tue, 2003-03-18 at 10:20, Jan Ciger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan,
I get the same thing here in a regular window (ie my desktop)
anti-aliasing etc is working fine. But only in vnc or Xnest do the qt
applications give this kind of error. Same version
I do believe this worked for me recently... I think it became broken, at
least that I noticed it, around RC1 or just afterwards... and I know that
kde apps, and Xft in general is supposed to automatically fall back to the
normal rendering if the RENDER extension is not available...
scott
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You do get the same error when running the same app directly (without
Xnest or VNC) ? Then how come that the antialiasing works, when it does
not have Render ? Either I am missing something or we do not understand
each other.
oops should
On Tuesday 18 March 2003 01:33 pm, scott chevalley wrote:
I do believe this worked for me recently... I think it became broken, at
least that I noticed it, around RC1 or just afterwards... and I know
that kde apps, and Xft in general is supposed to automatically fall back
to the normal
On Tuesday 18 March 2003 02:28 pm, Jan Ciger wrote:
You do get the same error when running the same app directly (without
Xnest or VNC) ? Then how come that the antialiasing works, when it does
not have Render ? Either I am missing something or we do not understand
each other.
oops
On Tuesday 18 March 2003 02:28 pm, Jan Ciger wrote:
You do get the same error when running the same app directly (without
Xnest or VNC) ? Then how come that the antialiasing works, when it does
not have Render ? Either I am missing something or we do not understand
each other.
oops
On Tue, 2003-03-18 at 11:28, Jan Ciger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You do get the same error when running the same app directly (without
Xnest or VNC) ? Then how come that the antialiasing works, when it does
not have Render ? Either I am missing something or
On Tuesday 18 March 2003 02:28 pm, Jan Ciger wrote:
You do get the same error when running the same app directly (without
Xnest or VNC) ? Then how come that the antialiasing works, when it does
not have Render ? Either I am missing something or we do not understand
each other.
oops
On Tue, 2003-03-18 at 11:28, Jan Ciger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You do get the same error when running the same app directly (without
Xnest or VNC) ? Then how come that the antialiasing works, when it does
not have Render ? Either I am missing something or
On Tuesday 18 March 2003 07:08 pm, James Sparenberg wrote:
On Tue, 2003-03-18 at 11:28, Jan Ciger wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You do get the same error when running the same app directly (without
Xnest or VNC) ? Then how come that the antialiasing works,
On Tuesday 18 March 2003 08:54 pm, Greg Meyer wrote:
Greg,
If you want I can send these rpms to you for verification.
I just rebuilt qt with the 3.1.1-12 spec file from cvs and the problem is
gone. Laurent applied a patch for -13 that turned on AA by default. See
my other
On Tue, 2003-03-18 at 18:04, Greg Meyer wrote:
On Tuesday 18 March 2003 08:54 pm, Greg Meyer wrote:
Greg,
If you want I can send these rpms to you for verification.
I just rebuilt qt with the 3.1.1-12 spec file from cvs and the problem is
gone. Laurent applied a patch for
For anyone that wants to test, I have posted the libqt3.1.1-12mdk
rpms that I rebuilt here:
http://cybercfo.gkmweb.com/RPMS
Since falling back to those RPMS I can once again run KDE programs from
Gnome. It is good to know what the problem has been. I haven't tried
running tightvnc server from
Will it be included in the upcoming 9.1 ?
-
** http://www.gnomedesktop.org/search.php?query=topic=60* The GNOME
Project is pleased to announce the immediate availability of the GNOME
2.2.1 Desktop and Developer Platform!
The 2.2.x series is devoted to bugfixes, translations, and
Am Montag, 17. März 2003, 14:37:45 Uhr MET, schrieb LUGGE:
Will it be included in the upcoming 9.1 ?
Yes, if manage to build and test it in the next fifteen minutes.
--
Götz Waschk master of computer science University of Rostock
On Monday 17 March 2003 08:41 am, Götz Waschk wrote:
Am Montag, 17. März 2003, 14:37:45 Uhr MET, schrieb LUGGE:
Will it be included in the upcoming 9.1 ?
Yes, if manage to build and test it in the next fifteen minutes.
ROTFLMAO
Well then, you should be able to sneak a few more things in
Am Montag, 17. März 2003, 08:51:09 Uhr MET, schrieb Greg Meyer:
But this does mean that 9.1 goes out the door with KDE and KDE apps
unable to run in Xnest or vnc. Major, major, major, and it means I'm
going to have to stick to 9.0. oh Poo.
As long as GNOME apps run fine I don't mind :-)
But I
On Mon, 2003-03-17 at 13:41, Götz Waschk wrote:
Am Montag, 17. März 2003, 14:37:45 Uhr MET, schrieb LUGGE:
Will it be included in the upcoming 9.1 ?
Yes, if manage to build and test it in the next fifteen minutes.
GNOME minor releases are sort-of rolling as well, I seem to remember, so
we
On Mon, 2003-03-17 at 13:51, Greg Meyer wrote:
On Monday 17 March 2003 08:41 am, Götz Waschk wrote:
Am Montag, 17. März 2003, 14:37:45 Uhr MET, schrieb LUGGE:
Will it be included in the upcoming 9.1 ?
Yes, if manage to build and test it in the next fifteen minutes.
ROTFLMAO
Well
Am Montag, 17. März 2003, 13:45:45 Uhr MET, schrieb Adam Williamson:
GNOME minor releases are sort-of rolling as well, I seem to remember, so
we probably have a mix of 2.2.0 and 2.2.1 in Cooker. We don't have the
newest Nautilus, though, I don't think.
That not nice, but it's simply too late.
On Monday 17 March 2003 08:58 am, Adam Williamson wrote:
On Mon, 2003-03-17 at 13:51, Greg Meyer wrote:
On Monday 17 March 2003 08:41 am, Götz Waschk wrote:
Am Montag, 17. März 2003, 14:37:45 Uhr MET, schrieb LUGGE:
Will it be included in the upcoming 9.1 ?
Yes, if manage to build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
On Monday 17 March 2003 08:58 am, Adam Williamson wrote:
Yes. At first I thought it was Galaxy, because GNOME had trouble too.
This
was only because the galaxy window that pops for new users is qt.
Once you
prevent that from
But this does mean that 9.1 goes out the door with KDE and KDE
apps unable to run in Xnest or vnc. Major, major, major, and
it means I'm going to have to stick to 9.0. oh Poo.
--
Greg
I agree that being unable to run in Xnest or use vnc is a major problem. It
is inconceivable to me that anyone
v9.1(RC) earlier in the testing cycle so
issues can/may get resolved NOW before release.
Just my penny stock opinion...
~Ken
- Original Message -
From: Bob Brickey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, March 17, 2003 4:08 PM
Subject: Re: [Cooker] GNOME 2.2.1 Desktop
On Mon, 2003-03-17 at 05:51, Greg Meyer wrote:
On Monday 17 March 2003 08:41 am, Götz Waschk wrote:
Am Montag, 17. März 2003, 14:37:45 Uhr MET, schrieb LUGGE:
Will it be included in the upcoming 9.1 ?
Yes, if manage to build and test it in the next fifteen minutes.
ROTFLMAO
Well
On Mon, 17 Mar 2003 15:02:33 +0100, Götz Waschk
[EMAIL PROTECTED] said:
Am Montag, 17. März 2003, 13:45:45 Uhr MET, schrieb Adam Williamson:
GNOME minor releases are sort-of rolling as well, I seem to remember, so
we probably have a mix of 2.2.0 and 2.2.1 in Cooker. We don't have the
newest
On Mon, 2003-03-17 at 07:04, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
On Monday 17 March 2003 08:58 am, Adam Williamson wrote:
Yes. At first I thought it was Galaxy, because GNOME had trouble too.
This
was only because the galaxy window
On Monday 17 March 2003 06:13 pm, James Sparenberg wrote:
On Mon, 2003-03-17 at 05:51, Greg Meyer wrote:
On Monday 17 March 2003 08:41 am, Götz Waschk wrote:
Am Montag, 17. März 2003, 14:37:45 Uhr MET, schrieb LUGGE:
Will it be included in the upcoming 9.1 ?
Yes, if manage to build
On Mon, 2003-03-17 at 07:04, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
On Monday 17 March 2003 08:58 am, Adam Williamson wrote:
Yes. At first I thought it was Galaxy, because GNOME had trouble too.
This
was only because the galaxy window
On Mon, 2003-03-17 at 19:13, Quel Qun wrote:
On Mon, 2003-03-17 at 07:04, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
On Monday 17 March 2003 08:58 am, Adam Williamson wrote:
Yes. At first I thought it was Galaxy, because GNOME had
On Mon, 2003-03-17 at 17:39, Greg Meyer wrote:
On Monday 17 March 2003 06:13 pm, James Sparenberg wrote:
On Mon, 2003-03-17 at 05:51, Greg Meyer wrote:
On Monday 17 March 2003 08:41 am, Götz Waschk wrote:
Am Montag, 17. März 2003, 14:37:45 Uhr MET, schrieb LUGGE:
Will it be included
On Tuesday 18 March 2003 01:20 am, James Sparenberg wrote:
I would be curious to see if it is a XFree bug in 4.3 that does not exist
in 4.2.1 also. Could I try to doengrade XFree to 4.2.1 on a 9.1 box and
see what that does.
There was someone in the Expert group trying to do just this...
53 matches
Mail list logo
