|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
GNOME 2.26Dear maintainers,
sorry for nagging, but what is the plan for GNOME 2.26? The current mix of GNOME 2.24 and 2.26 in sid is unfortunately not particularly usable, I currently experience far more issues and reproducible crashes than usual. At the same time, reporting bugs on these issues does not seem to make an awful lot of sense, because it is about unsupported versions and nobody will fix crashes in a Debian package which will be replaced by a new upstream soon. (Actually, I reported some of the issues, but did not receive feedback on many of them) Thanks, Johannes -- To UNSUBSCRIBE, email to debian-gtk-gnome-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: GNOME 2.26Le mercredi 20 mai 2009 à 10:01 +0200, Johannes Rohr a écrit :
> sorry for nagging, but what is the plan for GNOME 2.26? Unless more than one person starts working on it, it is becoming clear to me that the plan is to wait for a very long time. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling |
|
|
Re: GNOME 2.26Le mercredi 20 mai 2009 à 12:00 +0200, Josselin Mouette a écrit :
> Le mercredi 20 mai 2009 à 10:01 +0200, Johannes Rohr a écrit : > > sorry for nagging, but what is the plan for GNOME 2.26? > > Unless more than one person starts working on it, it is becoming clear > to me that the plan is to wait for a very long time. Let me also add that #517768 is a blocker for large parts of GNOME 2.26 and that we will be able to go forth only when it is fixed. If you want to help, start by reproducing this (MIME cache version 1.0 in your home, version 1.1 in the system, using nautilus 2.26) and try to understand why the 1.0 cache is not simply ignored by the xdgmime code in glib2.0. Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling |
|
|
|
|
|
Re: GNOME 2.262009/5/20 Josselin Mouette <joss@...>:
> Let me also add that #517768 is a blocker for large parts of GNOME 2.26 > and that we will be able to go forth only when it is fixed. > > If you want to help, start by reproducing this (MIME cache version 1.0 > in your home, version 1.1 in the system, using nautilus 2.26) and try to > understand why the 1.0 cache is not simply ignored by the xdgmime code > in glib2.0. IMO, it should save time for people who want to help if a sample mime.cache 1.0 file is available. Does anyone who has the problem still keeps their file? Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-gtk-gnome-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: GNOME 2.26Hello Josselin!
> > > sorry for nagging, but what is the plan for GNOME 2.26? > > > > Unless more than one person starts working on it, it is becoming clear > > to me that the plan is to wait for a very long time. What do you mean with that sentence? You are the only one in the Gnome team? How can I help when I am not a maintainer? > Let me also add that #517768 is a blocker for large parts of GNOME 2.26 > and that we will be able to go forth only when it is fixed. > > If you want to help, start by reproducing this (MIME cache version 1.0 > in your home, version 1.1 in the system, using nautilus 2.26) and try to > understand why the 1.0 cache is not simply ignored by the xdgmime code > in glib2.0. Sorry for the stupid question. How can I find out which mime version I use. I do not have this problem and I use nautilus 2.26. > > Cheers, > -- > .''`. Josselin Mouette > : :' : > `. `' “I recommend you to learn English in hope that you in > `- future understand things” -- Jörg Schilling CU Michael -- ,''`. : :' : Michael Ott `. `' e-mail: michael at king-coder dot de `- |
|
|
Re: GNOME 2.26Le jeudi 21 mai 2009 à 10:41 +0200, Michael Ott a écrit :
> > > Unless more than one person starts working on it, it is becoming clear > > > to me that the plan is to wait for a very long time. > What do you mean with that sentence? You are the only one in the Gnome > team? How can I help when I am not a maintainer? Actually that’s a bit of an exaggeration, but apart from Luca Bruno and I, other maintainers don’t seem so eager to see GNOME 2.26 packaged. > > Let me also add that #517768 is a blocker for large parts of GNOME 2.26 > > and that we will be able to go forth only when it is fixed. Note that in the meantime, I have reassigned it so that it is not a blocker anymore. It is still a blocker for squeeze, of course, but it’s not blocking the transition anymore. > > If you want to help, start by reproducing this (MIME cache version 1.0 > > in your home, version 1.1 in the system, using nautilus 2.26) and try to > > understand why the 1.0 cache is not simply ignored by the xdgmime code > > in glib2.0. > Sorry for the stupid question. How can I find out which mime version I > use. I do not have this problem and I use nautilus 2.26. The home directory cache is only created when you add new MIME types at the user level. To create a 1.0 version cache, you need the pre-GNOME 2.24 tools: shared-mime-info 0.30, nautilus 2.22 + glib < 2.17 or nautilus 2.20 + gnome-vfs 2.22. Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling |
|
|
Re: GNOME 2.26On Wed, May 20, 2009 at 12:09:41PM +0200, Josselin Mouette wrote:
> Let me also add that #517768 is a blocker for large parts of GNOME 2.26 > and that we will be able to go forth only when it is fixed. > > If you want to help, start by reproducing this (MIME cache version 1.0 > in your home, version 1.1 in the system, using nautilus 2.26) and try to > understand why the 1.0 cache is not simply ignored by the xdgmime code > in glib2.0. I don't use nautilus; is there a simpler test case? My limited testing suggests that mime.cache _is_ ignored by glib when it is v1.0, but in this case glib reads other files in the mime directory (aliases, globs, etc.). If there is a v1.1 mime.cache, then those files are _not_ read. If there is incorrect data in those files that may explain the bug, but it does not explain why things start working if someone removes mime.cache; as far as glib is concerned, a missing mime.cache is the same as an existing v1.0 mime.cache. Now, if there is some other component in the system that silently regenerates ~/.local/share/mime/mime.cache if it is missing (during login, for example), that could explain everything... Gabor -- --------------------------------------------------------- MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences --------------------------------------------------------- -- To UNSUBSCRIBE, email to debian-gtk-gnome-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
| Free embeddable forum powered by Nabble | Forum Help |