Re: Midnight Commander: bug report and patch
On Thu, Dec 24, 2009 at 11:37 AM, Ben Okopnik wrote: > I tried reporting this bug in Launchpad more about a week back, and > never got any response. Since it's a pretty big one (zip file contents > not showing up), I figured I'd send it here; hopefully, someone finds it > helpful! There seems to be a workaround in place already, but the actual culprit definitely wasn't fixed. Thanks for chasing it down! I've merged your patch (diff -u tends to be friendlier for me) in the latest upload to Lucid, 3:4.7.0-1ubuntu1. Best, -Dan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
Then we have this mysterious guy from Portugal who feels the political > dimension of the problem. He will try to defend the case in a heroic > fashion. And when you believe that you finally made it and the problem > is properly discussed amoung those guys who matter, the Canonical dude > shows up and wipes it all out with a quicky: this is only desire and > not a bug, classified "invalid". *BANG* > The mysterious guy from Portugal (myself) is one of the thousand mysterious guys which participates on Free Software and Ubuntu. I wish you the best luck finding someone "who matters" . About the problem which you have reported, and per the discussion we had on the bug my opinion is very clear, Ubuntu should be secure by default, it shouldn't ask you for authorization to be secure. Since so far you are the only person reporting the problem, let me ask, what is the impact of the problem ? What solution do you propose ? There are plenty of bugs affecting mysterious guys and blocking them from using a piece of equipment or performing a specific task. In my opinion filling a bug for something that does not work as you expect is reasonable, trying to get more attention when there is no clear impact, is not. Best regards, -- João Luís Marques Pinto GetDeb Team Leader http://www.getdeb.net http://blog.getdeb.net -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
On Tue, 2010-01-05 at 22:32 +0100, Patrick Freundt wrote:
> On Tue, Jan 5, 2010 at 10:15 PM, Brian Murray wrote:
> > Bug reporting does not "require[s] a form of social network" as the bug
> > was properly reported without one. Rather to move the bug along the
> > triaging process usually requires other people to look at it and
> > indicate whether or not they also experience the bug.
>
> Well, yes! I can see that clearly now by this perfect example here[1]
> on your launchpad, and how fine grained Canonical's tactics work out,
> if (!) you dont run into a super (ninja) troll like me.
>
> At first a person who seems like the cute and warmhearted animal
> friend ("thank you for making Ubuntu better by reporting a bug"). Then
> the classic developer guy who tries to tell me at first the problem
> does not exist. Only as I raise the tone he confirmes the problem.
> Then we have this mysterious guy from Portugal who feels the political
> dimension of the problem. He will try to defend the case in a heroic
> fashion. And when you believe that you finally made it and the problem
> is properly discussed amoung those guys who matter, the Canonical dude
> shows up and wipes it all out with a quicky: this is only desire and
> not a bug, classified "invalid". *BANG*
For the record, I'm the "Canonical dude"...and I didn't do this as a
representative of Canonical, rather a common sense user of Ubuntu. I
don't disagree that what Firefox does without your consent isn't wrong,
BUT I disagree that because you don't like what an application
does...it's automatically a bug. Is it a bug that we don't
automatically enable and password protect your screensaver in Ubuntu? or
that we don't automatically encrypt all your data?
Perhaps you will get farther opening a bug with mozilla?...good luck
--
Robbie Williamson rob...@ubuntu.com
Ubuntu robbiew[irc.freenode.net]
"You can't be lucky all the time, but you can be smart everyday"
-Mos Def
"Arrogance is thinking you are better than everyone else, while
Confidence is knowing no one else is better than you." -Me ;)
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
On Tue, Jan 5, 2010 at 10:44 PM, C de-Avillez wrote: > [...] instead of > reasoning, you keep on being aggressive. > p.s. by the way, I agree with your bug point -- I do not like programmes > calling home, or elsewhere, without my explicit consent. But I do not > see this as a such a big issue -- I can always stop using the package, > or configure it *not* to do that And that is reason and cause why I am not smooth and loving anymore. Just stopping to use firefox wont do the trick here, as my bug report is in context of several other topics. So the situation in short is this: you better leave the Debian community as long as you can to end up at Ubuntu. Its not really the thing, but now there is Chromium OS which bases its work on Ubuntu Karmic. And you have Mozilla that plays into the cards of Google. You have Novell and Suse that play into the cards of Microsoft. And by the year 2010 we all end up where we started with Free Software 10-15 years ago. This _must_ lead to unhappyness if you are not one of those who get paid really well for taking part in this game. P. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
Am Dienstag, den 05.01.2010, 22:32 +0100 schrieb Patrick Freundt: > Then > the classic developer guy who tries to tell me at first the problem > does not exist. He couldn't reproduce it. Not existing and not reproducible are two different pairs of shoes. You can only proof the existence of bug, not the absence (except for the few mathematical verified programs). -- Benjamin Drung Ubuntu Developer (www.ubuntu.com) | Debian Maintainer (www.debian.org) signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
On 01/05/2010 02:56 PM, Patrick Freundt wrote: > On Tue, Jan 5, 2010 at 9:43 PM, Remco wrote: > >> You can start a topic on ubuntuforums.org if you're not comfortable with IRC. >> > Just so I get this straight - you aswell as Brian Murray suggest, that > bug reporting can not be handled within launchpad alone, and instead I > should wear myself out on IRC or forums, until I collected enough > people who will flame the heck out of that Canonical guy who took a > political decision and set the bug status to "invalid"? > > Well, ok. If that is how Ubuntu works, then good luck guys :) > > P. > > No, this is not correct. You do not need to wear yourself out on IRC or the forums. And there is no flaming needed. In fact flaming (or aggressiveness) is not, usually, a good way to get constructive attention. You reported a bug. Good. Now, what usually happens is (eventually) some people will look at it, and add their comments/views on the issue. It may take a time -- we have more bugs, and bug reporters clamoring for attention than we have people available. A bug will, eventually, be confirmed by *other* people having the same issue, or by a triager that is able to reproduce it. It is not just because one feels it is a bug, someone else *must* feel the same. Which, BTW, does not really make it --yet -- in a real bug. This is how it works. What Brian and Remco suggested was for you to spearhead the process -- which you do not want to do. No problems, you can just wait. But you do *not* want to wait. You want the maintainer, and only the maintainer, to look at it. Eventually someone would get there. But you wanted to speed up the process, and you got some answers on how to do it. And you dismissed them. I do not understand your reasoning here. Anyway. You reported a problem. The issue is now understood. Someone took a decision on it. You do not agree with it but, (again) instead of reasoning, you keep on being aggressive. Ah well. ..C.. p.s. by the way, I agree with your bug point -- I do not like programmes calling home, or elsewhere, without my explicit consent. But I do not see this as a such a big issue -- I can always stop using the package, or configure it *not* to do that signature.asc Description: OpenPGP digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
On Tue, Jan 5, 2010 at 10:15 PM, Brian Murray wrote:
> Bug reporting does not "require[s] a form of social network" as the bug
> was properly reported without one. Rather to move the bug along the
> triaging process usually requires other people to look at it and
> indicate whether or not they also experience the bug.
Well, yes! I can see that clearly now by this perfect example here[1]
on your launchpad, and how fine grained Canonical's tactics work out,
if (!) you dont run into a super (ninja) troll like me.
At first a person who seems like the cute and warmhearted animal
friend ("thank you for making Ubuntu better by reporting a bug"). Then
the classic developer guy who tries to tell me at first the problem
does not exist. Only as I raise the tone he confirmes the problem.
Then we have this mysterious guy from Portugal who feels the political
dimension of the problem. He will try to defend the case in a heroic
fashion. And when you believe that you finally made it and the problem
is properly discussed amoung those guys who matter, the Canonical dude
shows up and wipes it all out with a quicky: this is only desire and
not a bug, classified "invalid". *BANG*
Guys, please forget about this bug reportig thing. Its only good for
comedy. We all better go and write our own blog.
Have a nice day!
Patrick (the ninja troll) Freundt
[1]
https://bugs.launchpad.net/bugs/500601
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
On Tue, Jan 05, 2010 at 09:32:26PM +0100, Patrick Freundt wrote: > On Tue, Jan 5, 2010 at 6:33 PM, Brian Murray wrote: > > > A good first step after reporting a new bug report is finding another > > Ubuntu user who can recreate the bug report and subsequently confirm it > > and set the bug's status to Confirmed. > > So bug reporting requires a form of social network as pre-condition > and Internet Relay Chat is still popular, no matter of all the > problems. No, I was replying to your specific question of: "What would be such a next step?"[1] Bug reporting does not "require[s] a form of social network" as the bug was properly reported without one. Rather to move the bug along the triaging process usually requires other people to look at it and indicate whether or not they also experience the bug. [1] https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2010-January/010371.html -- Brian Murray @ubuntu.com signature.asc Description: Digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
proper procedure regarding bug reports
On Tue, Jan 5, 2010 at 9:43 PM, Remco wrote: > You can start a topic on ubuntuforums.org if you're not comfortable with IRC. Just so I get this straight - you aswell as Brian Murray suggest, that bug reporting can not be handled within launchpad alone, and instead I should wear myself out on IRC or forums, until I collected enough people who will flame the heck out of that Canonical guy who took a political decision and set the bug status to "invalid"? Well, ok. If that is how Ubuntu works, then good luck guys :) P. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
On Tue, Jan 5, 2010 at 21:32, Patrick Freundt wrote: > On Tue, Jan 5, 2010 at 6:33 PM, Brian Murray wrote: > >> A good first step after reporting a new bug report is finding another >> Ubuntu user who can recreate the bug report and subsequently confirm it >> and set the bug's status to Confirmed. > > So bug reporting requires a form of social network as pre-condition > and Internet Relay Chat is still popular, no matter of all the > problems. You can start a topic on ubuntuforums.org if you're not comfortable with IRC. -- Remco -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
On Tue, Jan 5, 2010 at 6:33 PM, Brian Murray wrote: > A good first step after reporting a new bug report is finding another > Ubuntu user who can recreate the bug report and subsequently confirm it > and set the bug's status to Confirmed. So bug reporting requires a form of social network as pre-condition and Internet Relay Chat is still popular, no matter of all the problems. Well, in this case I better switch from launchpad to the efforts of blogging. Thank you. P. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: proper procedure regarding bug reports
On Tue, Jan 05, 2010 at 12:49:13AM +0100, Patrick Freundt wrote: > To avoid misunderstandings I would like to ask the list in a bit more > detailed kind of way for the proper procedure regarding bug reports, - > because I am lacking official feedback regarding bug #500601, and on > the one side I am aware that we had christmas and new year > celebrations, people are generally busy with many things, etc. and on > the other side I would like to move forward with several other topics > that indirectly rely on this bug report. > > When you are sure that a software is not behaving as expected and you > easily managed to reproduce that behaviour isolated from other > influences, then how much time should you give to a bug report till > you try a next step? > > What would be such a next step? A good first step after reporting a new bug report is finding another Ubuntu user who can recreate the bug report and subsequently confirm it and set the bug's status to Confirmed. This could be a friend or a bug triager - lots of whom can be found in the #ubuntu-bugs channel. -- Brian Murray @ubuntu.com signature.asc Description: Digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Starting on 9,10 as GUEST
I try to explain with my poor english... My situation : I am a french teatcher in a secondary school and i am the administrator of all the computers of the school Reaparing, installing managing all of the 80 machines in the classrooms. About Ubuntu : I use Ubuntu from the beginning at home. I am constant user of it . I try to change for better some proceedings and build programs for school. I haven't finish because I have lots of ideas... Last year I install on all of computers in my school : Ubuntu 9,04 as you can see on the picture of a classroom join in this mail. At this time i ask students to get an USB Key to save their works and use only the guest session. (Only for protection of the system) To do that, I use an addon menu and a script witch permit to every one to start the machine on the guest session at the logon menu of Ubuntu ( I explain to do it for others teatchers on my web site : http://mproduction.nuxit.net.). I keep the admin count to install softwares and makes upgrades (only for me) I don' want that eache student log on Ubuntu with a standard user, password on spécific name or count , ONLY as GUEST For a school it is very usefull. With the new version of Ubuntu 9,10, the GDM change... and my script doesn't work... My question is COULD YOU HELP ME or explaine to me how I can have in the logon menu a possibility to use ubuntu 9,10 à the logon menu as a guest so that i can upgrade and keep my methode of protection of the system as i have done in Ubuntu 8,04. I havent found a solution today... i can't upgrade form 9,04 to 9,10. I would be very glad if an engineer from Ubuntu on a developper show me how to transforme my script or show me a new proceeding to start as GUEST in Ubuntu 9,10... Please , i believe in you, in Ubuntu, Help me, I wait for your answer. Long life to Canonical and Ubuntu. Best regards, MARLIN Bertrand -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
