[opensuse-factory] openSUSE 10.2 bug prioritization
Hi everyone, while going through the openSUSE 10.2 "RED bugs" (Blocker/Criticals), I thought it might be a good idea to ask for some help regarding bug prioritization. openSUSE 10.2 is going to be released rather soon. With the current bug count of 910 open bugs filed for 10.2, we will certainly have to postpone fixing some of them to 10.3. Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users! Thanks in advance, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Christoph, On Saturday 04 November 2006 09:18, Christoph Thiel wrote:
...
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users!
Where does one see this status indication? And how does one alter or influence it? I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149). And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
Christoph
Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Nov 04, 2006 at 09:37:50AM -0800, Randall R Schulz wrote:
I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149).
Still crashing the last RPM you tried? Please comment in bugzilla.
And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
We have 1) legal (*) 2) technical issues with/when enabling Subpixel hinting. Best regards, Stefan (*) probably resolved since friday Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Stefan, On Saturday 04 November 2006 10:15, Stefan Dirsch wrote:
On Sat, Nov 04, 2006 at 09:37:50AM -0800, Randall R Schulz wrote:
I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149).
Still crashing the last RPM you tried? Please comment in bugzilla.
I've replied there with all the information requested.
And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
We have
1) legal (*) 2) technical
issues with/when enabling Subpixel hinting.
How is it that you have (2) when I do not by the simple expedient of rebuilding the package with the proper configuration change?
Best regards, Stefan
(*) probably resolved since friday
Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Nov 04, 2006 at 10:48:02AM -0800, Randall R Schulz wrote:
Stefan,
On Saturday 04 November 2006 10:15, Stefan Dirsch wrote:
On Sat, Nov 04, 2006 at 09:37:50AM -0800, Randall R Schulz wrote:
I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149).
Still crashing the last RPM you tried? Please comment in bugzilla.
I've replied there with all the information requested.
Ok. Then we know which update has been responsible for the regression you see on your system. Unfortunately the update contains huge changes (over about 3 months git master checkins), so it won't be easy to fix this issue. Therefore I can't make any promises to have this fixed until final release! And going back is no option ATM.
And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
We have
1) legal (*) 2) technical
issues with/when enabling Subpixel hinting.
How is it that you have (2) when I do not by the simple expedient of rebuilding the package with the proper configuration change?
That it works for you does not mean, that it works for all fonts. Subpixel rendering is currently broken in freetype2, believe me. This issue is under investigation and the feature won't be enabled again until we have fixed it. Best regards, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Stefan, On Saturday 04 November 2006 12:00, Stefan Dirsch wrote:
On Sat, Nov 04, 2006 at 10:48:02AM -0800, Randall R Schulz wrote:
Stefan,
On Saturday 04 November 2006 10:15, Stefan Dirsch wrote:
On Sat, Nov 04, 2006 at 09:37:50AM -0800, Randall R Schulz wrote:
I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149).
Still crashing the last RPM you tried? Please comment in bugzilla.
I've replied there with all the information requested.
Ok. Then we know which update has been responsible for the regression you see on your system. Unfortunately the update contains huge changes (over about 3 months git master checkins), so it won't be easy to fix this issue. Therefore I can't make any promises to have this fixed until final release! And going back is no option ATM.
Why is going back to a stable release not an option? And how do you figure that a frequently bombing X server _is_ an option?
And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
We have
1) legal (*) 2) technical
issues with/when enabling Subpixel hinting.
How is it that you have (2) when I do not by the simple expedient of rebuilding the package with the proper configuration change?
That it works for you does not mean, that it works for all fonts. Subpixel rendering is currently broken in freetype2, believe me. This issue is under investigation and the feature won't be enabled again until we have fixed it.
Perhaps it would make more sense to adjust the schedule to the requirements of the software included rather than the reverse? The fact is, in both these cases you switched to new versions of software when those versions were inferior to the ones they replaced. Why do this?
Stefan
Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Randall You don't know the details, why we switched to newer releases of X.Org and freetype2. And no, we will not discuss all decisions for software updates. Especially when there are legal issues. Best regards, Stefan On Sat, Nov 04, 2006 at 12:12:36PM -0800, Randall R Schulz wrote:
Stefan,
On Saturday 04 November 2006 12:00, Stefan Dirsch wrote:
On Sat, Nov 04, 2006 at 10:48:02AM -0800, Randall R Schulz wrote:
Stefan,
On Saturday 04 November 2006 10:15, Stefan Dirsch wrote:
On Sat, Nov 04, 2006 at 09:37:50AM -0800, Randall R Schulz wrote:
I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149).
Still crashing the last RPM you tried? Please comment in bugzilla.
I've replied there with all the information requested.
Ok. Then we know which update has been responsible for the regression you see on your system. Unfortunately the update contains huge changes (over about 3 months git master checkins), so it won't be easy to fix this issue. Therefore I can't make any promises to have this fixed until final release! And going back is no option ATM.
Why is going back to a stable release not an option? And how do you figure that a frequently bombing X server _is_ an option?
And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
We have
1) legal (*) 2) technical
issues with/when enabling Subpixel hinting.
How is it that you have (2) when I do not by the simple expedient of rebuilding the package with the proper configuration change?
That it works for you does not mean, that it works for all fonts. Subpixel rendering is currently broken in freetype2, believe me. This issue is under investigation and the feature won't be enabled again until we have fixed it.
Perhaps it would make more sense to adjust the schedule to the requirements of the software included rather than the reverse?
The fact is, in both these cases you switched to new versions of software when those versions were inferior to the ones they replaced. Why do this?
Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Stefan, On Saturday 04 November 2006 12:38, Stefan Dirsch wrote:
Randall
You don't know the details, why we switched to newer releases of X.Org and freetype2. And no, we will not discuss all decisions for software updates. Especially when there are legal issues.
So you want to enlist our help in beta testing (and I put considerable time into filing these reports and supplying the follow-up information requested) and then just ignore us when we have problems you don't care to fix? Surely you can see that with an X server behaving as the current one does the system has no usable GUI at all. Am I just supposed to accept that? And I do not see why legal issues are an excuse for not informing your users. This is open source software, and I think we deserve to know what's going on within the organization that is using that software for their own profit-making purposes. We also need to know your reasoning and plans so we can make our own plans. If you're not going to be able to supply what I need, then I'd just as soon cut my losses now and start working with a distribution that can. I'd probably be more understanding if you'd give me something to go on, but from what I'm getting here, it sounds like you don't give a damn whether users and customers get something useful or not. For the record, I've been paying for boxed versions of SuSE Linux for over five years now, including every single version released from 9.0 onward and a few earlier ones. So far, I'd planned to buy the boxed 10.2 release, as well. So I feel I've got a legitimate reason to press this issue.
Stefan
Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Nov 04, 2006 at 01:05:25PM -0800, Randall R Schulz wrote:
On Saturday 04 November 2006 12:38, Stefan Dirsch wrote:
Randall
You don't know the details, why we switched to newer releases of X.Org and freetype2. And no, we will not discuss all decisions for software updates. Especially when there are legal issues.
So you want to enlist our help in beta testing (and I put considerable time into filing these reports and supplying the follow-up information requested) and then just ignore us when we have problems you don't care to fix?
Did I say this? I'm still interested in fixing this problem. I would like to spend my time on this instead of discussing why we switched to a newer Xserver verion closer to X.org 7.2 release rather than staying with something undefined between 7.1 and 7.2, which won't be easy to support you might imagine. Best regards, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Stefan, On Saturday 04 November 2006 13:25, Stefan Dirsch wrote:
On Sat, Nov 04, 2006 at 01:05:25PM -0800, Randall R Schulz wrote:
On Saturday 04 November 2006 12:38, Stefan Dirsch wrote:
Randall
You don't know the details, why we switched to newer releases of X.Org and freetype2. And no, we will not discuss all decisions for software updates. Especially when there are legal issues.
So you want to enlist our help in beta testing (and I put considerable time into filing these reports and supplying the follow-up information requested) and then just ignore us when we have problems you don't care to fix?
Did I say this? I'm still interested in fixing this problem. I would like to spend my time on this instead of discussing why we switched to a newer Xserver verion closer to X.org 7.2 release rather than staying with something undefined between 7.1 and 7.2, which won't be easy to support you might imagine.
And I'd both like to have it fixed and help with the fixing. For what it's worth, I'm a long-time Unix / Linux programmer and even though I mostly do Java these days, I'm still competent with native programming in C and C++, so I can do more than just install alternate versions and send in log files, if need be. Please let me know if there's more I can do. (I am receiving and monitoring CC's of postings to bug 216149).
Best regards, Stefan
RRS --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 04 November 2006 09:37, Randall R Schulz wrote:
Christoph,
On Saturday 04 November 2006 09:18, Christoph Thiel wrote:
...
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. ...
Where does one see this status indication? And how does one alter or influence it?
I'd still like to hear answers to these questions.
...
Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Lørdag 04 november 2006 20:31 skrev Randall R Schulz:
Where does one see this status indication? And how does one alter or influence it?
I'd still like to hear answers to these questions.
Go to any bug, this for instance: https://bugzilla.novell.com/show_bug.cgi?id=216097 The status is clearly marked in red, "New". You can change it at the bottom but in this particular case Christoph asked to post to the mailinglist with reasons for making a given bug a "blocker", not changing it autonomously, as we'd then soon have 800 blockers. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Nov 04, 2006 at 09:06:32PM +0100, Martin Schlander wrote:
Lørdag 04 november 2006 20:31 skrev Randall R Schulz:
Where does one see this status indication? And how does one alter or influence it?
I'd still like to hear answers to these questions.
Go to any bug, this for instance: https://bugzilla.novell.com/show_bug.cgi?id=216097
The status is clearly marked in red, "New". You can change it at the bottom but in this particular case Christoph asked to post to the mailinglist with reasons for making a given bug a "blocker", not changing it autonomously, as we'd then soon have 800 blockers.
Exactly! The plan is to get a better idea of where the problems are, so we can make sure to address them. (However, I can't promise that each and every blocker will be resolved until GM -- at some point blockers aren't real blockers anymore ... the usual disclaimers apply, etc. ;)) Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Nov 04, 2006 at 09:37:50AM -0800, Randall R Schulz wrote:
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users!
Where does one see this status indication? And how does one alter or influence it?
What do you mean by "status indication"? If you are talking about bug severity, I'd like to ask you to refrain from changing it. Technically, that's something which should be exclusively done by engineering or product management.
I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149).
And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
I'm in good hope that we will be able to resolve that issue very soon. Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Cristoph, On Sunday 05 November 2006 03:37, Christoph Thiel wrote:
...
Where does one see this status indication? And how does one alter or influence it?
What do you mean by "status indication"? If you are talking about bug severity, I'd like to ask you to refrain from changing it. Technically, that's something which should be exclusively done by engineering or product management.
OK, "severity." What I was really looking for is a way to see a listing of these bugs. I tried to generate a list, but apparently I'm using the Bugzilla Advanced Search feature incorrectly, 'cause I get zero listings. What combination of settings there will lsit the bugs with the severity level(s) you want reviewed?
I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149).
And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
I'm in good hope that we will be able to resolve that issue very soon.
Good... but: Which one? The X server crash or the font rendering? I can live with the latter (mostly be rebuilding the FreeType2 package), but the X server is a severe problem.
Best, Christoph
Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Randall R Schulz schrieb:
OK, "severity." What I was really looking for is a way to see a listing of these bugs. I tried to generate a list, but apparently I'm using the Bugzilla Advanced Search feature incorrectly, 'cause I get zero listings.
What combination of settings there will lsit the bugs with the severity level(s) you want reviewed?
Use this link to get a list of all unresolved 10.2 bugs, sorted by severity: https://bugzilla.novell.com/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=SUSE%20Linux&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailqa_contact2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=bug_status&field-1-1-0=classification&field-1-2-0=product&field0-0-0=noop&keywords=&keywords_type=anywords&long_desc=&long_desc_type=substring&product=openSUSE%2010.2&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type0-0-0=noop&value-1-0-0=NEW%2CASSIGNED%2CNEEDINFO%2CREOPENED&value-1-1-0=SUSE%20Linux&value-1-2-0=openSUSE%2010.2&value0-0-0=&votes=&order=bugs.bug_severity%20asc&query_based_on= Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Nov 05, 2006 at 07:03:57AM -0800, Randall R Schulz wrote:
What combination of settings there will lsit the bugs with the severity level(s) you want reviewed?
I was looking for hiding bugs in the Major/Normal/Minor/Enhancement range.
I surely hope I don't have to live with an X server that dies every couple of hours (https://bugzilla.novell.com/show_bug.cgi?id=216149).
And the beta1 font rendering is pretty poor. I have work-arounds for both, but they are not tenable in the long term since they both require running alternate versions of packages in place of those that are part of the distribution.
I'm in good hope that we will be able to resolve that issue very soon.
Good... but: Which one? The X server crash or the font rendering? I can live with the latter (mostly be rebuilding the FreeType2 package), but the X server is a severe problem.
... the font rendering. Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Christoph Thiel wrote:
Hi everyone,
while going through the openSUSE 10.2 "RED bugs" (Blocker/Criticals), I thought it might be a good idea to ask for some help regarding bug prioritization.
openSUSE 10.2 is going to be released rather soon. With the current bug count of 910 open bugs filed for 10.2, we will certainly have to postpone fixing some of them to 10.3.
What about bugs which have patches attached? Even if they are not red right now, it causes less work to apply the patches than it causes to release updates after GA. How should we tag these bugs? Keyword "Fix_is_Ready"? Regards, Carl-Daniel -- http://www.hailfinger.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, Christoph Thiel wrote:
while going through the openSUSE 10.2 "RED bugs" (Blocker/Criticals), I thought it might be a good idea to ask for some help regarding bug prioritization.
https://bugzilla.novell.com/show_bug.cgi?id=202133 If it's not fixed, there is no X.org on Pegasos PPC. That would make openSUSE on this platform quite useless... Bye, -- CzP http://peter.czanik.hu/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le samedi 4 novembre 2006 14:31, Peter Czanik a écrit :
Hello,
Christoph Thiel wrote:
while going through the openSUSE 10.2 "RED bugs" (Blocker/Criticals), I thought it might be a good idea to ask for some help regarding bug prioritization.
https://bugzilla.novell.com/show_bug.cgi?id=202133 If it's not fixed, there is no X.org on Pegasos PPC. That would make openSUSE on this platform quite useless... Bye,
novell support opensuse don't think a lot of client use ppc --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, Marc Collin wrote:
https://bugzilla.novell.com/show_bug.cgi?id=202133 If it's not fixed, there is no X.org on Pegasos PPC. That would make openSUSE on this platform quite useless... Bye,
novell support opensuse don't think a lot of client use ppc
According to my download statistics (I ran a large seeder for beta1 DVD downloads), about 5% of downloads were PPC. I also maintain PPC version of Packman packages for 10.1, and the number of users seems to be constantly rising. 10.2 without X.org would break these nice tendencies... Bye, -- CzP http://peter.czanik.hu/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Lørdag 04 november 2006 18:18 skrev Christoph Thiel:
openSUSE 10.2 is going to be released rather soon. With the current bug count of 910 open bugs filed for 10.2, we will certainly have to postpone fixing some of them to 10.3.
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users!
Maybe we should also help you guys clean up a little? Some of the 900+ bugs are mine, and some of those have either been resolved already or are wontfixes, but their status hasn't been changed. I assume this applies to other reports than mine too. https://bugzilla.novell.com/show_bug.cgi?id=204826 I understand that the evil bastards at broadcom won't allow redistribution of their stupid firmware. Might as well close it if no progress is going on. https://bugzilla.novell.com/show_bug.cgi?id=215649 Obviously a wontfix. https://bugzilla.novell.com/show_bug.cgi?id=215269 The localization will be in b2 or b2+ - the report is pretty irrelevant. 3 down, 907 to go. I also have some for 10.1 that are either fixed or irrelvant, will close em up now. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Martin Schlander
Lørdag 04 november 2006 18:18 skrev Christoph Thiel:
openSUSE 10.2 is going to be released rather soon. With the current bug count of 910 open bugs filed for 10.2, we will certainly have to postpone fixing some of them to 10.3.
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users!
Maybe we should also help you guys clean up a little?
Some of the 900+ bugs are mine, and some of those have either been resolved already or are wontfixes, but their status hasn't been changed. I assume this applies to other reports than mine too.
Feel free to close them.
https://bugzilla.novell.com/show_bug.cgi?id=204826 I understand that the evil bastards at broadcom won't allow redistribution of their stupid firmware. Might as well close it if no progress is going on.
https://bugzilla.novell.com/show_bug.cgi?id=215649 Obviously a wontfix.
https://bugzilla.novell.com/show_bug.cgi?id=215269 The localization will be in b2 or b2+ - the report is pretty irrelevant.
3 down, 907 to go.
I also have some for 10.1 that are either fixed or irrelvant, will close em up now.
Thanks a lot! Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Christoph Thiel schrieb:
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users!
OK, here we go: https://bugzilla.novell.com/show_bug.cgi?id=206954 There is still no audio player installed by default for GNOME users who decide not to use the AddOn product. https://bugzilla.novell.com/show_bug.cgi?id=216560 The author of cdrecord heavily dislikes it if other programs call themselves cdrecord. Even if it's just an oversight and might break translations, we should fix the wodim package description to avoid such trouble. https://bugzilla.novell.com/show_bug.cgi?id=217660 This package, part of the GNOME platform, is completely broken and the fix is easy. More and more packages from www.gnomefiles.org depend on it, users should be able to install them and not be blocked by a relatively stupid packaging bug. https://bugzilla.novell.com/show_bug.cgi?id=217326 This is happening to a lot of people and is really annoying. It makes zmd unusable and happens even during first installations, so people don't get their security update repos synced with zmd. https://bugzilla.novell.com/show_bug.cgi?id=218032 The gtk2ification of gnucash was impatiently awaited by many people, and now gnucash doesn't start up. There was a different bug where gnucash didn't start up that was marked critical. This one should be critical, too - because gnucash is installed by default. https://bugzilla.novell.com/show_bug.cgi?id=217875 Updating lua so extremely late was already wrong in the first place, but now at least the consequences should be minimized. File conflicts are a serious packaging bug, and users will see it if they try to install two games that need different lua versions. The packages should be split as suggested in comment 1 and the remaining conflicting parts marked as conflicting. https://bugzilla.novell.com/show_bug.cgi?id=216982 Don't know how to solve, but at least there should be an Xgl update for 10.1 that fixes the wrong %postun script so that at least those users who install patches regularly can update properly. https://bugzilla.novell.com/show_bug.cgi?id=214884 https://bugzilla.novell.com/show_bug.cgi?id=210922 https://bugzilla.novell.com/show_bug.cgi?id=216880 There should not be any unresolved dependencies in the final product. This looks very buggy. https://bugzilla.novell.com/show_bug.cgi?id=216155 If the report is correct, it seems to break the build of Xine, which is very bad because it's one of the first package many users are typically installing. https://bugzilla.novell.com/show_bug.cgi?id=215392 Gives the desktop an unfinished feeling and users are being told to use the eject context menu because of possible data loss. They should not run into an error message when doing that. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Andreas, first of all, many thanks for the extensive list! On Sun, Nov 05, 2006 at 02:41:24AM +0100, Andreas Hanke wrote:
Christoph Thiel schrieb:
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users!
OK, here we go:
https://bugzilla.novell.com/show_bug.cgi?id=206954 There is still no audio player installed by default for GNOME users who decide not to use the AddOn product.
I have that issue in my inbox already -- should be resolved on Beta2.
https://bugzilla.novell.com/show_bug.cgi?id=216560 The author of cdrecord heavily dislikes it if other programs call themselves cdrecord. Even if it's just an oversight and might break translations, we should fix the wodim package description to avoid such trouble.
+1, a cdrecord compat-symlink won't vanish any time soon, though.
https://bugzilla.novell.com/show_bug.cgi?id=217660 This package, part of the GNOME platform, is completely broken and the fix is easy. More and more packages from www.gnomefiles.org depend on it, users should be able to install them and not be blocked by a relatively stupid packaging bug.
+1, elevated.
https://bugzilla.novell.com/show_bug.cgi?id=217326 This is happening to a lot of people and is really annoying. It makes zmd unusable and happens even during first installations, so people don't get their security update repos synced with zmd.
-> blocker.
https://bugzilla.novell.com/show_bug.cgi?id=218032 The gtk2ification of gnucash was impatiently awaited by many people, and now gnucash doesn't start up. There was a different bug where gnucash didn't start up that was marked critical. This one should be critical, too - because gnucash is installed by default.
-> crit.
https://bugzilla.novell.com/show_bug.cgi?id=217875 Updating lua so extremely late was already wrong in the first place, but now at least the consequences should be minimized. File conflicts are a serious packaging bug, and users will see it if they try to install two games that need different lua versions. The packages should be split as suggested in comment 1 and the remaining conflicting parts marked as conflicting.
+1
https://bugzilla.novell.com/show_bug.cgi?id=216982 Don't know how to solve, but at least there should be an Xgl update for 10.1 that fixes the wrong %postun script so that at least those users who install patches regularly can update properly.
+1, IIRC there is a compiz update in the queue already -- I'll look into this on Monday.
https://bugzilla.novell.com/show_bug.cgi?id=214884 https://bugzilla.novell.com/show_bug.cgi?id=210922 https://bugzilla.novell.com/show_bug.cgi?id=216880 There should not be any unresolved dependencies in the final product. This looks very buggy.
Right ;)
https://bugzilla.novell.com/show_bug.cgi?id=216155 If the report is correct, it seems to break the build of Xine, which is very bad because it's one of the first package many users are typically installing.
+1, easy to fix.
https://bugzilla.novell.com/show_bug.cgi?id=215392 Gives the desktop an unfinished feeling and users are being told to use the eject context menu because of possible data loss. They should not run into an error message when doing that.
+1. Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 05 November 2006 13:56, Christoph Thiel wrote:
https://bugzilla.novell.com/show_bug.cgi?id=216982 Don't know how to solve, but at least there should be an Xgl update for 10.1 that fixes the wrong %postun script so that at least those users who install patches regularly can update properly.
+1, IIRC there is a compiz update in the queue already -- I'll look into this on Monday.
I'm not sure that this is the best solution as upgrade will fail for all those who missed this last update of 10.1. I'd rather do what I suggested to fix the %postun script in the 10.2 package and remove the unneded SuSEConfig.xdm in an update for xgl for 10.2. Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org
On Sun, Nov 05, 2006 at 05:31:54PM +0200, Andras Mantia wrote:
On Sunday 05 November 2006 13:56, Christoph Thiel wrote:
https://bugzilla.novell.com/show_bug.cgi?id=216982 Don't know how to solve, but at least there should be an Xgl update for 10.1 that fixes the wrong %postun script so that at least those users who install patches regularly can update properly.
+1, IIRC there is a compiz update in the queue already -- I'll look into this on Monday.
I'm not sure that this is the best solution as upgrade will fail for all those who missed this last update of 10.1. I'd rather do what I suggested to fix the %postun script in the 10.2 package and remove the unneded SuSEConfig.xdm in an update for xgl for 10.2.
I guess you already stated this in the bug? :) Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 05 November 2006 18:09, Christoph Thiel wrote:
On Sun, Nov 05, 2006 at 05:31:54PM +0200, Andras Mantia wrote:
On Sunday 05 November 2006 13:56, Christoph Thiel wrote:
https://bugzilla.novell.com/show_bug.cgi?id=216982 Don't know how to solve, but at least there should be an Xgl update for 10.1 that fixes the wrong %postun script so that at least those users who install patches regularly can update properly.
+1, IIRC there is a compiz update in the queue already -- I'll look into this on Monday.
I'm not sure that this is the best solution as upgrade will fail for all those who missed this last update of 10.1. I'd rather do what I suggested to fix the %postun script in the 10.2 package and remove the unneded SuSEConfig.xdm in an update for xgl for 10.2.
I guess you already stated this in the bug? :)
Sure, just that the idea was different here, so I thought it is wise to mention. ;-) Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org
Christoph Thiel wrote:
while going through the openSUSE 10.2 "RED bugs" (Blocker/Criticals), I thought it might be a good idea to ask for some help regarding bug prioritization.
https://bugzilla.novell.com/show_bug.cgi?id=218122 Enable more than 15 partitions for libata. I have already written a patch for this bug. Once it is applied, we have up to 63 partitions per libata/SCSI drive and the warning in the installer can disappear. Regards, Carl-Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006/11/05 12:53 (GMT+-0500) Carl-Daniel Hailfinger apparently typed:
Christoph Thiel wrote:
while going through the openSUSE 10.2 "RED bugs" (Blocker/Criticals), I thought it might be a good idea to ask for some help regarding bug prioritization.
Enable more than 15 partitions for libata. I have already written a patch for this bug. Once it is applied, we have up to 63 partitions per libata/SCSI drive and the warning in the installer can disappear.
Why didn't you attach your patch to the existing bug that AJ already reopened once? https://bugzilla.novell.com/show_bug.cgi?id=214992 -- "Rejoice and be glad, because great is your reward in heaven." Matthew 5:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, Am Samstag, 4. November 2006 18:18 schrieb Christoph Thiel:
while going through the openSUSE 10.2 "RED bugs" (Blocker/Criticals), I thought it might be a good idea to ask for some help regarding bug prioritization.
My candidates: https://bugzilla.novell.com/show_bug.cgi?id=216485 opensuse-updater shows error message in tooltip zypp-checkpatches-wrapper does not get the suid-root bit if running with permissions.secure. This makes opensuse-updater unuseable. Please reconsider the settings for permissions.secure (or remove zmd when running with permissions.secure - I consider its broken permission concept more critical ;-) https://bugzilla.novell.com/show_bug.cgi?id=148105 no error message when RPM database is missing YaST silently switches to "new installation" mode if I start in upgrade mode with the RPM database not available. There should be an error message that informs the user about the switch to "new installation" mode and the reason for it. Probably easy to fix (add the error message), and can avoid some problems. https://bugzilla.novell.com/show_bug.cgi?id=166881 solver should provide "dont delete $otherpackage" as possible conflict solution. This one could avoid several conflict messages. However, I'm not sure if it should be done at this late stage of development :-/ https://bugzilla.novell.com/show_bug.cgi?id=171082 YaST2 AppArmor report module should use radio buttons instead of checkboxes for archived reports "Just" an enhancement, but a usability problem and probably easy to fix. I also vote for fixing all bugs that have a patch attached already. Regards, Christian Boltz -- Wünschenswert wäre es auch, wenn Umfragen vor jeder Bundestagswahl, ob die Erst- oder die Zweitstimme die wichtigere sei, wenigstens soviele richtige Ergebnisse zeitigten, als würde man die gleiche Anzahl Schimpansen befragen. ;) [Bernd Brodesser in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, Am Sonntag, 5. November 2006 20:32 schrieb Christian Boltz:
My candidates:
Another one: https://bugzilla.novell.com/show_bug.cgi?id=193095 Font of Gnome apps don't have antialiasing in KDE Looks terrible :-( (The GIMP setup assistant looks even more terrible than the two screenshots in the bugreport - I can attach the GIMP screenshot if you want/request it.) Regards, Christian Boltz -- Wenn schon, dann höchstens Homo Sapiens Sapiens XEmacensis, die Entwicklungslinie, die im Laufe der Evolution sieben Finger an jeder Hand entwickelt hat. Und das alles nur um alle Tastenkürzel zur Bedienung von XEmacs nutzen zu können. [T. Templin über David Haller] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Nov 05, 2006 at 10:11:08PM +0100, Christian Boltz wrote:
Hello,
Am Sonntag, 5. November 2006 20:32 schrieb Christian Boltz:
My candidates:
Another one:
https://bugzilla.novell.com/show_bug.cgi?id=193095 Font of Gnome apps don't have antialiasing in KDE Looks terrible :-( (The GIMP setup assistant looks even more terrible than the two screenshots in the bugreport - I can attach the GIMP screenshot if you want/request it.)
+1 Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Christian, many thanks for sharing these with us! On Sun, Nov 05, 2006 at 08:32:57PM +0100, Christian Boltz wrote:
My candidates:
https://bugzilla.novell.com/show_bug.cgi?id=216485 opensuse-updater shows error message in tooltip zypp-checkpatches-wrapper does not get the suid-root bit if running with permissions.secure. This makes opensuse-updater unuseable. Please reconsider the settings for permissions.secure (or remove zmd when running with permissions.secure - I consider its broken permission concept more critical ;-)
Let's get the security teams point of view here.
https://bugzilla.novell.com/show_bug.cgi?id=148105 no error message when RPM database is missing YaST silently switches to "new installation" mode if I start in upgrade mode with the RPM database not available. There should be an error message that informs the user about the switch to "new installation" mode and the reason for it. Probably easy to fix (add the error message), and can avoid some problems.
+1
https://bugzilla.novell.com/show_bug.cgi?id=166881 solver should provide "dont delete $otherpackage" as possible conflict solution. This one could avoid several conflict messages. However, I'm not sure if it should be done at this late stage of development :-/
Right, nothing for the 10.2 timeframe.
https://bugzilla.novell.com/show_bug.cgi?id=171082 YaST2 AppArmor report module should use radio buttons instead of checkboxes for archived reports "Just" an enhancement, but a usability problem and probably easy to fix.
So, where is the patch? ;) Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Nov 06, 2006 at 10:31:04AM +0100, Christoph Thiel wrote:
Christian, many thanks for sharing these with us!
On Sun, Nov 05, 2006 at 08:32:57PM +0100, Christian Boltz wrote:
My candidates:
https://bugzilla.novell.com/show_bug.cgi?id=216485 opensuse-updater shows error message in tooltip zypp-checkpatches-wrapper does not get the suid-root bit if running with permissions.secure. This makes opensuse-updater unuseable. Please reconsider the settings for permissions.secure (or remove zmd when running with permissions.secure - I consider its broken permission concept more critical ;-)
Let's get the security teams point of view here.
Rational: You likely do not want users to be able to run system administrator tasks in "secure" mode at all, without root password protection. It should probably not start opensuse-updater then. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, first: two other candidate to fix for 10.2 I missed yesterday - both have the fix already included: https://bugzilla.novell.com/show_bug.cgi?id=190084 apparmor.vim missing The apparmor syntax highlighting file for vim is missing (was removed in 10.1 because it was terribly outdated). I have updated and fixed it. (well, vim syntax profiles can cause real headache...) The working file is attached to the bugreport. It simply needs to be added to the vim package. (Not sure if the assignee is the correct one.) https://bugzilla.novell.com/show_bug.cgi?id=188068 pin -v 100 foo tries to "su 100" ("su $2") The description says it all, and the fix is available. (Martin?) second: Am Montag, 6. November 2006 10:36 schrieb Marcus Meissner:
On Mon, Nov 06, 2006 at 10:31:04AM +0100, Christoph Thiel wrote:
On Sun, Nov 05, 2006 at 08:32:57PM +0100, Christian Boltz wrote:
https://bugzilla.novell.com/show_bug.cgi?id=216485 zypp-checkpatches-wrapper does not get the suid-root bit if running with permissions.secure. This makes opensuse-updater unuseable. [...] You likely do not want users to be able to run system administrator tasks in "secure" mode at all, without root password protection.
Hmm, zen-updater runs with permissions.secure in 10.1 [1] - and even grants _permanent_ permissions once one has entered the root password. Since I didn't install any updates with opensuse-updater yet: how does it handle installing updates? Does it ask for the root password every time when installing packages (as susewatcher did)? (If yes, I would consider it more secure than zen-updater.)
It should probably not start opensuse-updater then.
Not starting the updater at all isn't a solution also because not installing updates will make the system insecure over time. (Yes, I know that there's a difference bitween "installing updates" and "being notified about updates" - but it's easy to "forget" to run the update when nothing notifies you...) To sum it up: - being notified about updates should be available independend of the permissions.* level (I don't see that this could cause any harm because a user could also check the RPM database for outdated packages ;-) - missing notification could cause security problems (if nobody installs the fixed packages) - installing updates should require the root password (maybe permissions.easy could be an exception) If you really don't change your decision here, I foretell that this will become a FAQ for 10.2 ;-) Regards, Christian Boltz PS @ Christoph: regarding bug 171082: sorry, I only speak german, english, pfälzisch, bash, php, perl, (my)sql and HTML - but not ycp :-( [1] dunno for 10.2 - I uninstalled it ;) -- Wenn Du Dich weiter doof stellst, dann: Warning: loading builtin philipp-cool-down.dll. Couldn't be loaded! Expect trouble!!! [Philipp Zacharias in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Nov 07, 2006 at 12:01:15AM +0100, Christian Boltz wrote:
first: two other candidate to fix for 10.2 I missed yesterday - both have the fix already included:
https://bugzilla.novell.com/show_bug.cgi?id=190084 apparmor.vim missing The apparmor syntax highlighting file for vim is missing (was removed in 10.1 because it was terribly outdated). I have updated and fixed it. (well, vim syntax profiles can cause real headache...)
The working file is attached to the bugreport. It simply needs to be added to the vim package. (Not sure if the assignee is the correct one.)
https://bugzilla.novell.com/show_bug.cgi?id=188068 pin -v 100 foo tries to "su 100" ("su $2") The description says it all, and the fix is available. (Martin?)
Both are fixed already in STABLE and will hit Beta2 ;) [You need to watch opensuse-commit more closely ;)] Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, Am Dienstag, 7. November 2006 01:35 schrieb Christoph Thiel:
On Tue, Nov 07, 2006 at 12:01:15AM +0100, Christian Boltz wrote:
two other candidate to fix for 10.2 I missed yesterday - both have the fix already included: [...] Both are fixed already in STABLE and will hit Beta2 ;)
:-)
[You need to watch opensuse-commit more closely ;)]
Yes, seems so :-/ Regards, Christian Boltz --
Ich an seiner Stelle hätte den Fotografen reallife geplonkt. Wie entsteht denn in "reallife" dein *PLONK*? Beim Einschlag der Faust auf dem Auge? man "Ernst August" [Torsten Wiens und Cornell Binder in datr-s]
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 04 November 2006 11:18, Christoph Thiel wrote:
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated.
https://bugzilla.novell.com/show_bug.cgi?id=130452 (Update tomcat to current version) Tomcat 5.5 was released over two years ago, please update. -- Glenn Holmer (Q-Link: ShadowM) http://www.lyonlabs.org/commodore/c64.html --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Nov 07, 2006 at 03:51:57AM -0600, Glenn Holmer wrote:
On Saturday 04 November 2006 11:18, Christoph Thiel wrote:
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated.
https://bugzilla.novell.com/show_bug.cgi?id=130452 (Update tomcat to current version)
Tomcat 5.5 was released over two years ago, please update.
Sorry -- but at this stage we won't take a package update like this. However, Sonja is working on providing a recent tomcat through the openSUSE Build Service. Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, https://bugzilla.novell.com/show_bug.cgi?id=212053 Set promote_secondaries=1 by default Rationale: If you have multiple IP addresses on one network card and you delete the primary address, all other IP addresses on this card vanish unexpectedly. This has bitten quite some people in the past. Setting promote_secondaries=1 fixes this bug. I can provide a patch for this if needed. Regards, Carl-Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Just filed another bug after notification from upstream. https://bugzilla.novell.com/show_bug.cgi?id=218948 Resizing Vista NTFS partitions may keep Vista from booting It seems that current Windows Vista Release Candidates refuse to boot after any of the NTFS partitions they access are resized. Details at http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html#vista The linux-ntfs developers appreciate any testing and reports. Regards, Carl-Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Nov 08, 2006 at 12:15:40AM +0100, Carl-Daniel Hailfinger wrote:
Just filed another bug after notification from upstream.
https://bugzilla.novell.com/show_bug.cgi?id=218948 Resizing Vista NTFS partitions may keep Vista from booting
It seems that current Windows Vista Release Candidates refuse to boot after any of the NTFS partitions they access are resized. Details at http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html#vista The linux-ntfs developers appreciate any testing and reports.
Thanks for the heads-up! Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, Christoph Thiel wrote:
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users!
I would like that someone looks at bug 217259 - YaST2 x86-64 - Printer segfaults https://bugzilla.novell.com/show_bug.cgi?id=217259 Tobias --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Tobias Burnus
Hi,
Christoph Thiel wrote:
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated. I'd propose posting the bug numbers in this thread + giving a short rationale. Please keep in mind that we should try to focus on the bugs that really affect a majority of the users!
I would like that someone looks at bug 217259 - YaST2 x86-64 - Printer segfaults https://bugzilla.novell.com/show_bug.cgi?id=217259
Will be done, I moved it forward, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Christoph Thiel schrieb:
[...]
I'd like to point at bug 210935: The "istanbul" package is completely broken. The current summary of this bug is just a tiny subset the brokenness: It also installs its gconf schemas into /etc/gconf which doesn't work at all and other ugly things. I will attach a fix for the packaging brokenness shortly. The bug is ugly because istanbul had already been broken (in a different way) in 10.1. Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, Nov 12, 2006 at 04:45:25PM +0100, Andreas Hanke wrote:
Christoph Thiel schrieb:
[...]
I'd like to point at bug 210935:
The "istanbul" package is completely broken. The current summary of this bug is just a tiny subset the brokenness: It also installs its gconf schemas into /etc/gconf which doesn't work at all and other ugly things.
I will attach a fix for the packaging brokenness shortly. The bug is ugly because istanbul had already been broken (in a different way) in 10.1.
Thanks for bringing this up! I'v CCed myself to the bug and will make sure that it get's fixed. A patch will be very much appreciated! Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
And another one: https://bugzilla.novell.com/show_bug.cgi?id=220274 I have heard that very often. I think it's a problem with the native x86_64 build and a duplicate of bug 219982 which is already "Critical", but a confirmation would be nice. Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 12 November 2006 17:42, Andreas Hanke wrote:
And another one:
https://bugzilla.novell.com/show_bug.cgi?id=220274
I have heard that very often. I think it's a problem with the native x86_64 build and a duplicate of bug 219982 which is already "Critical", but a confirmation would be nice.
I doubt it. "Doesn't work at all with sun java 1.5" and "starts slowly" don't sound like duplicate bugs --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Anders Johansson schrieb:
On Sunday 12 November 2006 17:42, Andreas Hanke wrote:
And another one:
https://bugzilla.novell.com/show_bug.cgi?id=220274
I have heard that very often. I think it's a problem with the native x86_64 build and a duplicate of bug 219982 which is already "Critical", but a confirmation would be nice.
I doubt it. "Doesn't work at all with sun java 1.5" and "starts slowly" don't sound like duplicate bugs
It's both specific to x86_64 and there was another report (don't have the # at hand) where the reporter said that completely removing Sun Java resolved the slowness. It doesn't really matter whether it's a duplicate, an OOo startup time of almost 2 minutes is certainly unacceptable and needs more attention than "Normal", especially if it happens to many people. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Christoph Thiel schrieb:
Therefore, I'd like to ask YOU to help identify those bugs, that are currently hiding under the radar (ie. aren't "red") and should be elevated.
Given that today is officially the last day where non-Blockers are allowed to be fixed, I'd like to point at the following two non-Blockers which are still annoying enough (and have fixes attached): https://bugzilla.novell.com/show_bug.cgi?id=221383 The gdm default configuration file (/opt/gnome/share/gdm/defaults.conf) is corrupted because it contains a comment that is not commented out: Willing script, none is shipped, X11's one is used by default. Should be: # Willing script, none is shipped, X11's one is used by default. This invalidates the file and causes all values below the corrupted line to be discarded, esp. the "MinimalUID" setting. I assume that the impact of this is higher than currently known and documented in the bug report. https://bugzilla.novell.com/show_bug.cgi?id=220300 Alacarte is untranslated although it installs many translations because it doesn't find them. I have a feeling that the bug is currently incorrectly assigned because of a misunderstanding (alacarte doesn't have anything to do with gnome-main-menu) - can you investigate? Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (16)
-
Anders Johansson -
Andras Mantia -
Andreas Hanke -
Andreas Jaeger -
Carl-Daniel Hailfinger -
Christian Boltz -
Christoph Thiel -
Felix Miata -
Glenn Holmer -
Marc Collin -
Marcus Meissner -
Martin Schlander -
Peter Czanik -
Randall R Schulz -
Stefan Dirsch -
Tobias Burnus