Re: Testing Kubuntu 24.04 but cannot install "ubuntu-bug" to report bugs.

`ubuntu-bug` is part of the apport package which should be installed by default. Also, if you read the page you sent, you’ll notice you can just log into Launchpad and report bugs there if you’re having some issues with `ubuntu-bug`. @wxl | polka.bike C563 CAC5 8BE1 2F22 A49D 68F6

Testing Kubuntu 24.04 but cannot install "ubuntu-bug" to report bugs.

Hi folks, I wanted to test Kubuntu 22.04 and I installed it on an old MacBoock Pro 2011. I found a bug that I want to report. But I cannot install "*ubuntu-bug*" in the system. It is not available when I attempt to "apt install ubuntu-bug". I was following this guide but no luck: - https://help.

Re: Bugs in built-in file explorer in Ubuntu Desktop 18.04

x27;s still unfixed in 18.04. > > This is most likely not an Ubuntu packaging bug, but something in the > upstream Gnome code. Have you researched are there any bugs open about > this in Gnome? > Maybe you could contribute upstream and help Gnome developers fix it? > > Or if you

Re: Bugs in built-in file explorer in Ubuntu Desktop 18.04

bug, but something in the upstream Gnome code. Have you researched are there any bugs open about this in Gnome? Maybe you could contribute upstream and help Gnome developers fix it? Or if you have an Ubuntu Advantage subscription maybe use your support channels? Reporting to a generic Ubuntu quality

Re: Bugs in built-in file explorer in Ubuntu Desktop 18.04

> I want to report two bugs in the built-in file explorer in Ubuntu > Desktop 18.04. That's still Nautilus, right? > Bug no. 2: > > The following happens for me very frequently. I've been observing that for ages on Ubuntu 16.04, I think I might even have reported it

Bugs in built-in file explorer in Ubuntu Desktop 18.04

Hello, I want to report two bugs in the built-in file explorer in Ubuntu Desktop 18.04. I can't be bothered to first create a Launchpad account, so I'm sending my bug report to this e-mail address instead and hope that it will end up in the hands of the responsible developers. Y

Re: where to report bugs

33, João M. S. Silva mailto:joao.m.santos.si...@gmail.com>> wrote: Where in https://help.ubuntu.com/community/ReportingBugs is the information about where to report the bugs? There is a link in the side bar titled "Reporting non-crash hardware and desktop application bu

Re: where to report bugs

On Tue, 26 Nov 2019 at 00:33, João M. S. Silva < joao.m.santos.si...@gmail.com> wrote: > Where in https://help.ubuntu.com/community/ReportingBugs is the > information about where to report the bugs? > There is a link in the side bar titled "Reporting non-crash hardware and

where to report bugs

Hi, Where in https://help.ubuntu.com/community/ReportingBugs is the information about where to report the bugs? Thanks. João M. S. Silva -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

On one hand we have meritocracies, like GNOME, where some people have the final saying about what things are going to be. On the other we have democracies, like Debian, where all the decisions shall be agreed before taken on. The first one has the drawback of usually ignoring individual needs

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

On 31/05/17 01:43, C de-Avillez wrote: ... I will simply keep those as short as possible. And instead of making a monologue, with all the information, I would simulate an actual conversation. Usually with 10-20 seconds answers. (https://youtu.be/L45EqUl2q4M) I will not listen to it. If you c

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

Sorry but I spend an hour writing an answer to these emails, but even then I ended with something extra long that I think nobody will read or understand. In fact that's what usually happens when I answer in text. On the other hand when I use video in a couple of minutes I'm usually done. I w

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

On Tue, 30 May 2017 20:33:34 +0200 Alberto Salvia Novella wrote: > Sorry but I spend an hour writing an answer to these emails, but even > then I ended with something extra long that I think nobody will read > or understand. Writing is easy. Anybody can write. But *good* writing is difficult. W

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

n Sun, 28 May 2017 16:54:45 +0200 > Alberto Salvia Novella wrote: > > > About: > > (https://help.ubuntu.com/community/ReportingBugs) > > (https://wiki.ubuntu.com/es20490446e/Reporting%20bugs) > > OK, let's get thru the proposed page. > > I will be copying te

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

you as a driver of substantial changes to the bugs reporting guide, which consists of written text? -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

On Sun, 28 May 2017 16:54:45 +0200 Alberto Salvia Novella wrote: > About: > (https://help.ubuntu.com/community/ReportingBugs) > (https://wiki.ubuntu.com/es20490446e/Reporting%20bugs) OK, let's get thru the proposed page. I will be copying text from the proposed Reporting Bugs

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

Hi Alby What ..C.. just say to you shown the great admiration he has for U. We all thanks U for your effort in this community, and pls, keep his replies as suggestions to be a better man. Thank U, Alby. Thank U, ..C.. Inviato da BlueMail Il giorno 28 mag 2017, a

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

Hello Alberto, I really like the idea of a shorter manual for Bug Triaging, because the current one was hard to follow as a newbie. But I really dislike the way how you try to press others in accepting it as it is without modifications when writing this: Am 28.05.2017 um 16:54 schrieb Alberto

Re: [Ubuntu-bugcontrol] I have written a draft for the Reporting Bugs guide

On Sun, 28 May 2017 16:54:45 +0200 Alberto Salvia Novella wrote: NB: I have not yet *read* the new proposal. I am just discussing the approach here. > About: > (https://help.ubuntu.com/community/ReportingBugs) > (https://wiki.ubuntu.com/es20490446e/Reporting%20bugs) > > Sorry, but I'm absolutel

Re: I have written a draft for the Reporting Bugs guide

About: (https://help.ubuntu.com/community/ReportingBugs) (https://wiki.ubuntu.com/es20490446e/Reporting%20bugs) Sorry, but I'm absolutely convinced that the latest draft I've written is really what's needed. The sections clearly reflect every use case, and they are organised in a logical way

Re: I have written a draft for the Reporting Bugs guide

Lets show that to the customers: - (http://girlsaskguys.com/technology-internet/q2426552-would-you-follow-this) - (https://i58.servimg.com/u/f58/16/19/87/90/answer11.png) When I started this conversation I committed to something for my own curiosity, which was that I won't to shave till it

Re: I have written a draft for the Reporting Bugs guide

We do not want more people to open bugs. We want more people to open *good* bugs reports. Reports that can be worked out by triagers, maintainers, developers. This means the reports must be more on the complete side. More on the technical side. Less on the "it did not work". The tri

Re: I have written a draft for the Reporting Bugs guide

On 05/13/2017 03:08 AM, Gunnar Hjalmarsson wrote: > On 2017-05-13 02:17, C de-Avillez wrote: >> On Fri, 12 May 2017 11:57:33 +0200 Alberto Salvia Novella >> wrote: >>> And the second question is "would the proposed draft allow most >>> people to report bugs?

Re: I have written a draft for the Reporting Bugs guide

a LOT of > experience with dealing with bugs. Some of us have a LOT of experience > with *solving* bugs. Some of us have years and years of college-level > education, be it undergrad or graduate studies. Perhaps we *do* know > what we are talking about. Persons could have lot of experien

Re: I have written a draft for the Reporting Bugs guide

On 2017-05-13 02:17, C de-Avillez wrote: On Fri, 12 May 2017 11:57:33 +0200 Alberto Salvia Novella wrote: And the second question is "would the proposed draft allow most people to report bugs?" Yes, it will. And therein lies the danger. It is NOT easy to write an usable bug r

Re: I have written a draft for the Reporting Bugs guide

On Fri, 12 May 2017 11:57:33 +0200 Alberto Salvia Novella wrote: > Persons could have lot of experience, but the question is "would the > current guide allow most people to report bugs?" This is a more difficult question to answer. Let's try to define a few terms, fi

Re: I have written a draft for the Reporting Bugs guide

I strongly recommend to stop this right here right now, kill the thread and start over. I think that everyone here understands that many people are not native English speakers, and we are trying to communicate the best way possible. Also, I think everyone understands that Alberto is trying to solv

Re: I have written a draft for the Reporting Bugs guide

On May 11, 2017 3:17:14 PM PDT, Alberto Salvia Novella wrote: >Men There's more than just those in the community. > on mail I'm just b*. > put that b*** there. This is inappropriate language for this community. Please consult the Code of Conduct. > when I answer in >video I kno

Re: I have written a draft for the Reporting Bugs guide

On Thu, May 11, 2017 at 9:29 AM, Alberto Salvia Novella < es204904...@gmail.com> wrote: > With you permission I'm going to answer all email on video from now on. > Simply having to agree with people on text proves to be too tense for me. > > Anyway if you are unable to understand spoken English in

Re: I have written a draft for the Reporting Bugs guide

Brian Murray: Nor will I after finding a frog boiling in water in one. Men, I'm a very nice person in real life. But on mail I'm just bitchy. Today I was so tense because of these conversations that I even shout at someone at their face, and it was the first time something like that happened

Re: I have written a draft for the Reporting Bugs guide

On Thu, May 11, 2017 at 06:29:00PM +0100, flocculant wrote: > > > On 11/05/17 17:29, Alberto Salvia Novella wrote: > >With you permission I'm going to answer all email on video from now on. > >Simply having to agree with people on text proves to be too tense for me. > > > >Anyway if you are unabl

Re: I have written a draft for the Reporting Bugs guide

On 11/05/17 17:29, Alberto Salvia Novella wrote: With you permission I'm going to answer all email on video from now on. Simply having to agree with people on text proves to be too tense for me. Anyway if you are unable to understand spoken English in a private conversation, let me know and

Re: I have written a draft for the Reporting Bugs guide

With you permission I'm going to answer all email on video from now on. Simply having to agree with people on text proves to be too tense for me. Anyway if you are unable to understand spoken English in a private conversation, let me know and I will make an exception there. Thank you. -- U

Re: I have written a draft for the Reporting Bugs guide

I will be talking notes of your first impressions till next Thursday. On Friday I will start a first draft based on them. (https://help.ubuntu.com/community/ReportingBugs) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.c

Re: I have written a draft for the Reporting Bugs guide

Flocculant: What if the things you both agree on - everyone else in the world disagrees with? Since I will be showing the same draft to everyone, we will know. Dario Ruellan: > I have no problem leaving this in public, in fact, could be nice to > first gather consensus regarding the actual do

Re: I have written a draft for the Reporting Bugs guide

n be the way to go. Looking at the current documentation, we can divide the thing into this categories: Application crash System crash Non-crash bugs for apps Non-crash bugs for system Translation bugs and not present but implicit: non-bugs but actually feature requests Now, application crash and sys

Re: I have written a draft for the Reporting Bugs guide

On 11/05/17 00:33, Alberto Salvia Novella wrote: ... Basically because we are not skipping the public conversation. But just agreeing as far as possible first in private, so what's brought to public is just the few things that we were unable to agree with. And what if the things you both a

Re: I have written a draft for the Reporting Bugs guide

Flocculant: > What makes you think that two people talking won't amount to the > same? Alberto Salvia Novella: > (https://graphicproducts.com/articles/nemawashi) Basically because we are not skipping the public conversation. But just agreeing as far as possible first in private, so what's broug

Re: I have written a draft for the Reporting Bugs guide

Flocculant: What makes you think that two people talking won't amount to the same? (https://graphicproducts.com/articles/nemawashi) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: I have written a draft for the Reporting Bugs guide

t, one as a quick > guide, the other as advanced guide. > > I love the header on this page, allows me to quickly jump sections. > > https://wiki.ubuntu.com/Bugs/FindRightPackage > https://wiki.ubuntu.com/QATeam/Overview/Install_Bugs > > > I also like the idea about videos, si

Re: I have written a draft for the Reporting Bugs guide

On 10/05/17 20:16, Alberto Salvia Novella wrote: ...snip Do in private, so we can keep the conversation as light as possible till we finally get it to the public. Thanks for your help. Why do that? One person deciding to do what he wanted to caused issue because there was no real co

Re: I have written a draft for the Reporting Bugs guide

Dario Ruellan: I don't see why those two guides can't coexist, one as a quick guide, the other as advanced guide. What if we took advantage of the capability of wikis to abstract pages, and we make a guide that is concise, but provides generous amount of detail on sub-pages? Dario Ruellan:

Re: I have written a draft for the Reporting Bugs guide

Dario Ruellan: I don't see why those two guides can't coexist, one as a quick guide, the other as advanced guide. What if we took advantage of the capability of wikis to abstract pages, and we make a guide that is concise, but provides generous amount of detail on sub-pages? Dario Ruellan:

Re: I have written a draft for the Reporting Bugs guide

ections. https://wiki.ubuntu.com/Bugs/FindRightPackage https://wiki.ubuntu.com/QATeam/Overview/Install_Bugs I also like the idea about videos, since many users are willing to watch them instead of read a bunch of text. So, in the end, I think that Alberto need to keep exploring that idea as complement

Re: I have written a draft for the Reporting Bugs guide

27;m going to do: 1. Ask in private to people what they think it's needed in the reporting bugs guide, and how we could reach to that point. 2. Make a draft based on the agreements we made. Polish it till we agree as far as possible on it. 3. Bring the end result to public conversation, an

Re: I have written a draft for the Reporting Bugs guide

I find it odd how the Ubuntu help wiki suggests mailing list and/or IRC discussions in order for something to be changed [1] since this is not normal for a wiki. I'm guessing that newcomers completely miss this guidance principle. Invoking the Ubuntu Code of Conduct is also heavy-handed for a wiki.

Re: I have written a draft for the Reporting Bugs guide

On Tue, May 9, 2017 at 10:06 AM, Alberto Salvia Novella wrote: > Also understand that 95% contributors won't have the degree of persistence I > have on dealing with conflict. Also note that 95% of contributors won't cause as much conflict as you cause. Which is not necessary a bad thing, when pe

Re: I have written a draft for the Reporting Bugs guide

On 2017-05-09 13:20, flocculant wrote: If the sole reason for changing the wiki page was it's length, then rather than lose information, we should perhaps be looking splitting it up. I agree with this and it echoes the sentiment I shared earlier about having an "additional information" section

Re: I have written a draft for the Reporting Bugs guide

On 25/04/17 08:43, Alberto Salvia Novella wrote: Many people has been complaining through the years about not knowing how to report bugs in Ubuntu. I have been asking those people why is that, and they usually told me that the reporting bugs guide was too long, hard to skim, and nobody would

Re: I have written a draft for the Reporting Bugs guide

Walter and everyone else, (Stuff deleted) > Regardless of your feelings, the entire community is based on consensus. It's baked into the Code of Conduct. If you're impatient on how long that process takes (often a long time), I think it might be better to find a place where every commit is autom

Re: I have written a draft for the Reporting Bugs guide

On 2017-05-09 11:53, Alberto Salvia Novella wrote: The process is completely guided. It's like instructions on the instructions themselves. People aren't interested in that. *Some* people aren't interested in that. Better to offer an additional information section/page. the founder of Kubun

Re: I have written a draft for the Reporting Bugs guide

J: > "run this command, I'm not going to tell you why, > or what to expect, or how to navigate the menus and options, but just > run this command". The process is completely guided. It's like instructions on the instructions themselves. People aren't interested in that. J: > What degree of ag

Re: I have written a draft for the Reporting Bugs guide

oving the context that informs newbies WHY they shouldn't do something, leaving them no further explanation beyond "run this command, I'm not going to tell you why, or what to expect, or how to navigate the menus and options, but just run this command". These pages are N

Re: I have written a draft for the Reporting Bugs guide

Gustavo Silva: Please, do it right this time. Seems legit, except because that degree of agreement doesn't seem possible. Just see the latest email from J, for example. He basically suggested that everything is wrong, half of which was already like that in the original guide. If I had to d

Re: I have written a draft for the Reporting Bugs guide

Since there is a slight disagreement with the page's contents and the fact we do appreciate *collaboration* among contributors and teams, this is in CoC, I feel the need to revert this page ASAP to a previous version that everyone has agreed on. That is version 299. The current version is an unilat

Re: I have written a draft for the Reporting Bugs guide

On Mon, May 8, 2017 at 8:37 PM, Gunnar Hjalmarsson wrote: > > This is what the page looked like before: > https://help.ubuntu.com/community/ReportingBugs?action=recall&rev=299 > > Personally I'd like to see much of what you removed be reinserted. One > possibility might be to make the page consist

Re: I have written a draft for the Reporting Bugs guide

On 2017-04-25 09:43, Alberto Salvia Novella wrote: Many people has been complaining through the years about not knowing how to report bugs in Ubuntu. I have been asking those people why is that, and they usually told me that the reporting bugs guide was too long, hard to skim, and nobody would

Re: I have realised something about people not reporting bugs

Den 2017-04-30 kl. 20:18, skrev Thomas Ward: *Sent from my iPhone. Please excuse any typos, as they are likely to happen by accident.* On Apr 30, 2017, at 13:43, Alberto Salvia Novella wrote: Thomas Ward: Not all of us are comfortable running the latest devel release on our own compute

Re: I have realised something about people not reporting bugs

*Sent from my iPhone. Please excuse any typos, as they are likely to happen by accident.* > On Apr 30, 2017, at 13:43, Alberto Salvia Novella > wrote: > > Thomas Ward: > > Not all of us are comfortable running the latest devel release on our > > own computers (bare metal) because it would

Re: I have realised something about people not reporting bugs

la: >> I have realised something, which is that most painful bugs on new Ubuntu >> releases are hardware related. And that is probably caused by people >> testing releases on virtual machines, instead on real hardware. >> >> Graphics, wifi and UEFI are the most common s

Re: I have realised something about people not reporting bugs

Den 2017-04-30 kl. 12:36, skrev Alberto Salvia Novella: I have realised something, which is that most painful bugs on new Ubuntu releases are hardware related. And that is probably caused by people testing releases on virtual machines, instead on real hardware. Graphics, wifi and UEFI are the

Re: I have written a draft for the Reporting Bugs guide

I have came up with an alternate way to encourage people to report bugs. It's the second point in the Etiquette section: (https://wiki.ubuntu.com/es20490446e/Reporting%20bugs) -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at:

Re: I have written a draft for the Reporting Bugs guide

Nicholas Skaggs: I would encourage you to continue your efforts to improving the bug reporting guide itself, as opposed to bikeshedding about artwork or making yet another page. I mean this draft is intended to substitute the official reporting guide, once agreed. -- Ubuntu-quality mailin

Re: I have written a draft for the Reporting Bugs guide

> bikeshedding about artwork or making yet another page. I suspect you'll > find conversations on improving the bug reporting guide to be more fruitful > and receptive. > > You may find these useful as well; it's used in conjunction with the > reporting bugs pag

Re: I have written a draft for the Reporting Bugs guide

Nicholas Skaggs: I don't think you need any artwork on the page and as such I have removed it, given it's negative response in this thread. https://youtu.be/IGOsXqktN1M -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.co

Re: I have written a draft for the Reporting Bugs guide

Let me offer some clarity and history on this symbol. In my previous post I referred to it as the sauwastika. Note the alternate spelling. This is the left-facing symbol that was never used by National Socialism. It is pervasive in Buddhist iconography. It was the right-facing Hindu and Jainism sym

Re: I have written a draft for the Reporting Bugs guide

itful and receptive. You may find these useful as well; it's used in conjunction with the reporting bugs page for reporting bugs for image testing. It's been collaboratively improved by several members into something rather nice. https://wiki.ubuntu.com/Bugs/FindRightPackage

Re: I have written a draft for the Reporting Bugs guide

C de-Avillez: The swastika, independent of where/when it was created, now symbolises a dark time. Some -- myself included -- consider it abhorrent; in my case, for personal family reasons. I understand. I have removed it in favour of something less invasive. First I tried erasing only the swas

Re: I have written a draft for the Reporting Bugs guide

*Alberto: Just wanted to point out that I have never destroyed your work. If you look at the history of your wiki page (see https://wiki.ubuntu.com/es20490446e/Reporting%20bugs?action=info ) you will see that I am NOT the one the Lau

Re: I have written a draft for the Reporting Bugs guide

On Thu, 27 Apr 2017 04:41:19 +0200 Alberto Salvia Novella wrote: > Thomas Ward: > > While the purest form of the swastika comes from non-Nazi religious > > symbols, we should avoid using it because of the way it was twisted > > during the late 30s and 40s. > > The reason why the swastika is

Re: I have written a draft for the Reporting Bugs guide

Alberto: The reason why the swastika is there is because that image is an original blueprint from World War 2 Forgot to mention that I have no problem changing or removing it if needed. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https:

Re: I have written a draft for the Reporting Bugs guide

Thomas Ward: > While the purest form of the swastika comes from non-Nazi religious > symbols, we should avoid using it because of the way it was twisted > during the late 30s and 40s. The reason why the swastika is there is because that image is an original blueprint from World War 2, and if you

Re: I have written a draft for the Reporting Bugs guide

Alright guys let's all calm down and stop sniping at each other, I don't have to want to call for moderation of the list again. That said, I have my own concerns by using the swastika. While the purest form of the swastika comes from non-Nazi religious symbols, we should avoid using it because

Re: I have written a draft for the Reporting Bugs guide

Why did you make a video? Is this some sort of manifesto or something? Look I won' t watch your video, this is not normal. Please write something or not, but just please refrain from putting a nazi swastika on Ubuntu Wiki and it's over ok? Thanks. On Wed, Apr 26, 2017 at 4:51 PM Alberto Salvia N

Re: I have written a draft for the Reporting Bugs guide

Alvaro Leal: I just wanted to say that I can' t believe someone is actually planning to put a Nazi Swastika in the Ubuntu Wiki. Have you people lost your minds? My answer: https://youtu.be/aPhefCenly4 -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscr

Re: I have written a draft for the Reporting Bugs guide

I' m sorry, I don' t normally participate on this mailing list and I' m probably breaking all of your community rules and formatting standards here. Really sorry about that. I just wanted to say that I can' t believe someone is actually planning to put a Nazi Swastika in the Ubuntu Wiki. Have you

Re: I have written a draft for the Reporting Bugs guide

C de-Avillez: > We should *not* announce how to directly enter a bug in LP. If the system isn't functional reporting directly to Launchpad would be the only available method, although I agree that option should be presented as the last resort. I have clarified it: (https://wiki.ubuntu.com/es2

Re: I have written a draft for the Reporting Bugs guide

out that one of the problems with reporting > bugs is that many people won't take the time to file a bug report, but > instead they would look for a kick work around and never report. > > Curiously, when I showed the proposed draft for the bug reporting guide to > my brother, he m

Re: I have written a draft for the Reporting Bugs guide

Chris Hermansen has pointed out that one of the problems with reporting bugs is that many people won't take the time to file a bug report, but instead they would look for a kick work around and never report. Curiously, when I showed the proposed draft for the bug reporting guide to my br

Re: I have written a draft for the Reporting Bugs guide

On Tue, 25 Apr 2017 09:43:21 +0200 Alberto Salvia Novella wrote: > Many people has been complaining through the years about not knowing > how to report bugs in Ubuntu. I have been asking those people why is > that, and they usually told me that the reporting bugs guide was too > l

I have written a draft for the Reporting Bugs guide

Many people has been complaining through the years about not knowing how to report bugs in Ubuntu. I have been asking those people why is that, and they usually told me that the reporting bugs guide was too long, hard to skim, and nobody would be willing to read it. It wasn't till I put

Re: There's an idiot mass-closing old unfixed bugs

On Mon, 18 Apr 2016 13:52:07 -0700 Brian Murray wrote: > I personally think that is disrespectful of the work the bug reporter > may have put into the bug report. Additionally, lots of bugs do > persist from release to release and plenty of packages use the same > version acr

Re: There's an idiot mass-closing old unfixed bugs

Den 2016-04-19 kl. 15:11, skrev Alberto Salvia Novella: Nio Wiklund: how to make the following bug active for Lubuntu Xenial? If you are experiencing exactly the same symptoms, then just enter the affecter release first name into the tag list. But if you are not completely sure if it is exact

Re: There's an idiot mass-closing old unfixed bugs

Nio Wiklund: how to make the following bug active for Lubuntu Xenial? If you are experiencing exactly the same symptoms, then just enter the affecter release first name into the tag list. But if you are not completely sure if it is exactly the same bug, then create a new report and mention

Re: There's an idiot mass-closing old unfixed bugs

ld rather leave old reports as they are, and work only on bugs tagged as affecting current releases. If the bug is still relevant users and testers will tag it as such themselves. If you want to make sure a software still works, you are better done by testing it yourself without reading any old report

Re: There's an idiot mass-closing old unfixed bugs

k only on bugs tagged as affecting current releases. If the bug is still relevant users and testers will tag it as such themselves. If you want to make sure a software still works, you are better done by testing it yourself without reading any old report. That is much faster and likely as effective.

Re: There's an idiot mass-closing old unfixed bugs

Brian Murray: > I think bug triagers should make and effort to recreate the bug > report and if there is insufficient information then proceed down the > Incomplete path. I would rather leave old reports as they are, and work only on bugs tagged as affecting current releases. If t

Re: There's an idiot mass-closing old unfixed bugs

On Sat, Apr 16, 2016 at 11:53:54AM -0400, Thomas Ward wrote: > Teo, > > On 04/16/2016 11:28 AM, Teo Tei wrote: > > Hi, > > > > I'd like to bring your attention to the harmful conduct of a user > > handling bugs in Launchpad. > > > > There's

Re: There's an idiot mass-closing old unfixed bugs

Teo Tei: > And there's a big difference between close/invalid/wontfix and > incomplete. Usually many bugs in one release are shared with the next one. So the ideal procedure would be setting the bug status as incomplete, then telling the user: > If you are still experiencing t

Re: There's an idiot mass-closing old unfixed bugs

By the way, I wish you had a code of conduct about handling bugs in a way that is not harmful to the goal of fixing them. 2016-04-16 18:23 GMT+02:00 Teo Tei : >> When a report is filed against an old release and not yet fixed, but the >> report hasn't been updated with commen

Re: There's an idiot mass-closing old unfixed bugs

;[...]" That sounds about right, but that's not what dino99 is doing. He is CLOSING the issues. > I am not going to look through all your bugs, but the typical triage > procedure *is* to Close or Invalid or Incomplete (or Won't Fix for > series-targeted task items) EOL-release

Re: There's an idiot mass-closing old unfixed bugs

On Sat, 16 Apr 2016, at 16:28, Teo Tei wrote: > I have seen half a dozen bugs which I had reported myself ages ago, > closed in the last few days by this guy. So I have re-checked some of > those issues, and every single one of them still exists unfixed. I think that Thomas Ward ha

Re: There's an idiot mass-closing old unfixed bugs

to the harmful conduct of a user >> handling bugs in Launchpad. >> >> There's this "dino99", who is closing several bug reports just >> "because they are old", regardless of whether they are fixed or not. I >> think he should be stopped before he keeps do

Re: There's an idiot mass-closing old unfixed bugs

Teo, On 04/16/2016 11:28 AM, Teo Tei wrote: > Hi, > > I'd like to bring your attention to the harmful conduct of a user > handling bugs in Launchpad. > > There's this "dino99", who is closing several bug reports just > "because they are old", reg

There's an idiot mass-closing old unfixed bugs

Hi, I'd like to bring your attention to the harmful conduct of a user handling bugs in Launchpad. There's this "dino99", who is closing several bug reports just "because they are old", regardless of whether they are fixed or not. I think he should be stopped before

Current and future release bugs are usually shared

Just a small insight: if you are looking for debugging an Ubuntu release, it is usually a good idea looking at bugs in the previous releases too. As those are usually present in the latest release even when not tagged as such. For example, if you want to make Xenial stable it would be good

Ubiquity bugs

Hello, I hope it's not too late for Wily but these 2 Ubiquity bugs need to be fixed: Ubiquity resizes partition even when not asked to <http://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1218702> Ubiquity freezes during partition creation <http://bugs.launchpad.net/ubuntu/+

Re: Unity-2d bugs

On 30 September 2015 at 14:33, Alberto Salvia Novella wrote: > Colin Law: > Sorry, if I need to figure out what? > It was bugs that either I reported or or affected me that I was trying to > tidy up. > > Then I would just leave the reports as if someone would fix them, because

Re: Unity-2d bugs

Colin Law: Sorry, if I need to figure out what? It was bugs that either I reported or or affected me that I was trying to tidy up. Then I would just leave the reports as if someone would fix them, because that is in fact the commitment of Canonical with bugs in Unity affecting Precise

Re: Unity-2d bugs

On 29 September 2015 at 22:05, Alberto Salvia Novella wrote: > Colin Law: >> >> Is there the slightest chance of anyone working on any that have been >> around for years and so are obviously not critical? > > > If you need to figure out, these are the bugs: > &

  1   2   3   >