Re: Tablet pc (wacom based) not configured by default in hardy: why?
On Tue, Apr 22, 2008 at 10:56:17AM -0400, Mackenzie Morgan wrote: > On the topic of necessary things disappearing from xorg.conf...scrolling > on touchpads is still broken. I've gotten used to using real scrollbars > since I've been on Hardy for two months, but I really doubt anyone will > be pleased about the regression. I can't find the bug at the moment, > but the Synaptics section is missing from xorg.conf as well, so no > scrolling is available. Can't just use GSynaptics, of course, because > that requires having a synaptics section in xorg.conf in which you can > enable synclient. This sounds like bug 173411 to me which is solved for new installs and has a workaround for early Hardy adopters. -- 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
Re: Four crashes, no apport actions
On Wed, May 07, 2008 at 08:41:16AM -0400, Mackenzie Morgan wrote: > On Wed, 2008-05-07 at 14:36 +0200, Stéphane Graber wrote: > > > > Apport is only used during development, it's turned off in final release. > > > > Stéphane > > I got 2 apport "omg something crashed, wanna report it?" popups today. Were these somethings python applications? Apport is still currently reporting python crashes. -- 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
Re: Problem with libcupsys2
On Mon, Jun 02, 2008 at 07:58:00PM +0100, Toby Smithe wrote: > On Mon, Jun 2, 2008 at 7:51 PM, James Westby <[EMAIL PROTECTED]> wrote: > > If you see 403 errors it is one of the rare cases that > > an upload severely breaks many users systems, and it is > > a safety measure to limit the number of people that > > install the upload. > > I'm not sure what the status of this is, as I haven't encountered the > situation in a while, but previously when 403 errors were issued, I > had people coming to me in bafflement. update-manager didn't seem to > give a potential explanation for the error (and there is surely very > little chance it could be anything else). Perhaps an explanation could > be added to save users' confusion? I also recall a fair number of bug reports regarding 403 errors when a package has been removed from the archive and think a notification in update-manager would be helpful. -- 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
Re: Debugging help
On Thu, Jul 17, 2008 at 12:02:43PM -0400, Evan wrote: > I found and reported bug > #222653<https://bugs.launchpad.net/ubuntu/+source/libgnomekbd/+bug/222653>, > which has been reproduced by several people. > > AFAIK, it cannot yet be marked confirmed because not enough information is > present to fix it, however I'm not sure what else there is that we can add. > It doesn't involve a crash, so there aren't any backtraces, and nothing > related is showing up in any of the log files I've looked at. There was an error in the documentation regarding how the Confirmed bug status should be used. I've updated the description of Confirmed to indicate that it is the correct status to use if the bug is experienced by multiple users. I apologize for any confusion this caused. -- 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
Re: Bugs marked incomplete
On Mon, Sep 01, 2008 at 11:32:20PM +0200, Wouter Stomp wrote: > Hello, > > Bugs that are marked incomplete and subsequently get a reply from the > original reporter often stay in the incomplete status. This means they > automatically get closed even though the needed info was provided. I > think it would be a good idea to automatically change the status to > new once a new comment is made on an incomplete bug. There are actually two sub-statuses, if you will, to Incomplete. They are "Incomplete w/o response" and "Incomplete w/ response" both of which are searchable for via the Launchpad UI. When a bug report receives a response after being set to a status of Incomplete, the sub-status then becomes "Incomplete w/ response" and the expiration timer is reset. -- 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
Re: Errors on 8.04 upgrade page?
On Fri, Aug 22, 2008 at 06:28:11AM +0200, Mario Vukelic wrote: > Hi, > > http://www.ubuntu.com/getubuntu/upgrading > > For the upgrade Dapper -> Hardy, it recommends either "update-manager > -d" or "do-release-upgrade -d". However, in both cases the -d switch > checks for the next development release, which seems to me not to be > Hardy. > > There just was a case on the -users list where this led to trouble: > https://lists.ubuntu.com/archives/ubuntu-users/2008-August/157269.html > > Is this as bad as it looks and should this be filed as a bug? The instructions at http://www.ubuntu.com/getubuntu/upgrading have been updated with regards to how to perform an upgrade from Dapper to Hardy. Thanks for bringing this to our attention. -- 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
Re: The iPhone, VBox, and devio
On Fri, Sep 19, 2008 at 03:35:55PM -0400, Kevin Fries wrote: > I have been monitoring a problem with the iPhone breaking their > Windows Virtual Machines on Linux hosts. Basically the problem > progressed like this: > > If you have a Linux host, and tried to run iTunes on it, it would not > run correctly via Wine. Most of us tried to create a virtual machine > using one of the VM products on the market (this one was Sun's > VirtualBox, but VMWare has volumes of details on it also). This > allowed iTunes to work better, but as soon as you plugged in your > iPhone, the VM would crash. Updates to both VMWare and VBox has > stopped the crashing. However, iTunes still does not acknowledge the > phone, so you can not backup your contacts, music, etc. So, I like > many, have resorted to a dual boot situation to back up the phone. > > The phone is such an unreliable POS, that not syncing is not really an > option. So, we wait, and wait, and wait some more. Finally today, > one of the guys over at VBox/Sun came up with this solution: > > > In case one of you is in for some adventure. The iPhone works if you > > modify the linux sources and recompile your kernel: > > > > Modify MAX_USBFS_BUFFER_SIZE to 128K in drivers/usb/core/devio.c > > I figure I would ask the developer community before putting anything > in Launchpad so I can ask for something that does not make me look as > stupid as I am in this area (kernel and drivers programming). This is probably a question best answered by the kernel team, [EMAIL PROTECTED], who I am cc'ing. > * What would be the downside of requesting this change permanently > in the Ubuntu kernel modules? > > * Could it be done safely? > > * Would any other devices/apps benefit from such a change other than > the iPhone? -- 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
Re: Intrepid amd64 Live CD beta testing
On Fri, Oct 03, 2008 at 02:41:34PM +0200, Loïc Martin wrote: > Hi, > > While previous Intrepid amd64 Live CD works perfectly, the Beta one > released yesterday doesn't manage to configure properly X on my computer > (Nvidia 7900GS 256Mo PCIe, Iiyama Prolite B2403WS through VGA port). The > screen has vertical colored bars (green/gray/yellow) and going to the > console, killing gdm, dpkg-reconfigure xserver-xorg blocks at the end > (starting X from another console doesn't work : > No screens found. > > I'd like top report in Launchpad, but I'm not sure what I should report > it against. Also, is there any special tags (except of course > regression-potential) for the Beta? Bug reports regarding X can generally be filed against the 'xorg' package, and if necessary they will be moved to the correct package by the Ubuntu X team. Additionally, you'll want to include your '/etc/X11/xorg.conf' file and '/var/log/Xorg.0.log' from the Live CD. You can find out more about debugging X at http://wiki.ubuntu.com/X/Debugging. -- 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
Re: ENCFS Hardy->ibex migration
On Mon, Oct 27, 2008 at 08:37:10AM +, (``-_-´´) -- Fernando wrote: > Olá Mackenzie e a todos. > > On Saturday 25 October 2008 18:07:03 Mackenzie Morgan wrote: > > On Sat, 2008-10-25 at 12:41 +0100, (``-_-´´) -- Fernando wrote: > > > I know we are really close to release, but either we fix bug 234818 [1], > > > or add it to Release Notes, and put some hook on Update-manager, or we > > > will have several[2] users losing access to their files, with no easy way > > > of getting them back (sure, Hardy LiveCD could do the job). > > > > For future reference, when you think something needs a mention in the > > release notes, mark it as "also affects project...ubuntu-release-notes". > > I just did it for this bug. > > Yeah, I knew there was some way of doing it, but couldn't remember. > Still, since Hardy is LTS, users are going to be faced with this problem > until its fixed, on every release we have. It'd help if somebody could take a stab at writing the release notes too. Thanks, -- 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
Re: Best practice for reporting bugs
On Wed, Mar 25, 2009 at 08:44:13PM -0300, Derek Broughton wrote: > Matt Zimmerman wrote: > > >> That's going to be news to the average user, of which a noticeable number > >> are _still_ using the old bug tools to file a bug straight > >> to "ubuntu-users" > > > > We don't install those tools by default, while we do install apport. > > I know, but there's still a significant number of people using releases > pre-Intrepid (or maybe hardy), which had reportbug, and we still see those > bug reports. I know there isn't much to be done about that, but telling > everybody about - and how to use - apport will help. You might be interested to know that reportbug has been modified in Jaunty[1] and that the package override is being changed to not point people to ubuntu-users[2]. [1] http://launchpad.net/bugs/228183 [2] http://launchpad.net/bugs/326091 -- 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
Re: Apport Hooks Task Force
On Mon, Sep 21, 2009 at 06:26:27AM -0400, John Vivirito wrote: > On 09/20/2009 10:00 AM, Sense Hofstede wrote: > > Hello, > > Recently Brian Murray asked for more Apport hooks to be added to as many > > packages as possible,[0] because of the choice for Apport as the preferred > > way to report bugs. (For more information, have a look at the QATeam spec > > [1]) > > > > The move away from the web interface ought to make our lives easier because > > now more relevant information is (going to be) attached to bug reports, > > reducing the length of the correspondence, making bug triaging and fixing > > more efficient. However, if we want to have the full benefit of the > > possibilities Apport gives us, we need to do some work. > > > > High-profile packages probably will get Apport hooks in time for the Karmic > > release, but there are many more packages that could benefit from both hooks > > and symptoms. I therefore suggest to set up an operation that makes sure we > > do give as many packages as possible a nice hook. > > What should this operation do? The idea is to create an 'apport-hook' tag, > > report bugs against all packages (that don't have a hook yet) and start > > watching the bugs. Then we can write hooks and watch the tag for bugs that > > have a proper one attached. The Bugsquad could do the buggy part of the > > task, the MOTU and Ubuntu Developers can afterwards add the hooks to the > > packages (and help writing them). > > > > If we'd get the greatest part of our archive to have Apport hooks, it'll be > > much easier for us to cope with the many bug reports that inevitably are > > going to come when Karmic is released and we'd be able to learn how to deal > > with those kind of bug reports before the LTS will be there. > > > > Maybe it would be a good idea to devote a HugDay to this? It would at least > > be useful to create a wiki page an send an announcement to explain the > > procedure of adding hooks to packages. > > > > [0] > > https://lists.ubuntu.com/archives/ubuntu-bugsquad/2009-September/001546.html > > [1] https://wiki.ubuntu.com/QATeam/Specs/IncreaseApportAdoption > > > > Kind regards, > > > At the moment there is no hook for source package > lightning-sunbird. I have never written a hook and last i > looked (a while ago) and it looked hard to do. I lost link on > how to write them. If someone can give me an idea or example > it would be great. There are other Mozilla packages that are > missing hooks, however at this time i cant remember what ones > off hand. I'm on a honeymoon number 1. not sure when im going > to get back. I actually gave a class on this at the most recent Ubuntu Developer week and there is a log[1] of it available. It has become much easier to write one with the convenience functions available in apport. [1] https://wiki.ubuntu.com/MeetingLogs/devweek0909/ApportPkgHooks -- 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
Re: msql broken
On Sat, Nov 21, 2009 at 10:46:14AM -0500, Adam Strawcutter wrote: > Ok I am a noob..kind of. Been a geek all my life but took the next step > to geek hood and got ubuntu. But I cannot fix msql server. I can't get > rid of it, or anything. Its so annoying. I have tried all the apt-get -f > and everything nothing works. Please help. here is the code that I am > getting when I try and fix the bug. oh and I can't report the bug > because ubuntu tells me that msql is not a ubuntu package. HELP!!! > Thanks all. The package is actually mysql. As this seems like a support issue you might consider asking a question about this in Ubuntu's answer tracker at http://answers.launchpad.net/ubuntu/. -- 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
Re: msql broken
On Tue, Dec 01, 2009 at 03:57:08PM -0400, Derek Broughton wrote: > Brian Murray wrote: > > > On Sat, Nov 21, 2009 at 10:46:14AM -0500, Adam Strawcutter wrote: > >> Ok I am a noob..kind of. Been a geek all my life but took the next step > >> to geek hood and got ubuntu. But I cannot fix msql server. I can't get > >> rid of it, or anything. Its so annoying. I have tried all the apt-get -f > >> and everything nothing works. Please help. here is the code that I am > >> getting when I try and fix the bug. oh and I can't report the bug > >> because ubuntu tells me that msql is not a ubuntu package. HELP!!! > >> Thanks all. > > > > The package is actually mysql. > > Are you sure? Once upon a time I used msql... If that's what he is using, > then it isn't under package control. Well, I was going off the output they had included in their original e-mail. "Setting up mysql-server-5.0 (5.0.51a-3ubuntu5.4) ..."[1] [1] https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2009-November/010134.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
Re: Bugs expiry
On Tue, Dec 15, 2009 at 12:58:35PM +, Przemek Kulczycki wrote: > Hi. > The expirable bugs page shows over 8500 bugs. > https://bugs.edge.launchpad.net/ubuntu/+expirable-bugs > The oldest one is over 300 days old. > Are these bugs going to be closed automatically? Not at this point in time. > What are the settings for bugs expiring in Ubuntu? Bug expiry is currently disabled for Ubuntu in Launchpad. When it was turned on a couple of years ago it ended up being problematic from a technical standpoint and controversial probably due to the technical problems from a community standpoint. > Is the Launchpad Janitor still working or is it turned off? It is currently turned off for Ubuntu however there was a brief discussion of enabling it again for a very limited set of bug reports and then depending on how that goes expanding the set of bugs covered. -- 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
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
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
Re: Bug reporting for Ubuntu Server? WTF?
On Fri, Feb 12, 2010 at 12:17:47PM -0600, Patrick Goetz wrote: > I just filed a bug against the 64-bit Karmic (9.10) server edition on > bugs.launchpad.net and noticed that the process appears to have > regressed considerably. > > First of all, there is no longer any clear indication on the front page > of bugs.launchpad.net about how one goes about filing a bug, even when > logged in. While I understand that developers want people to use apport > (more on this in a moment) it would be nice to have a simple, brief > description explaining how to file a bug which does not involve reading > an entire manual (e.g. "(Read our guide or take a tour)"). This question better answered by the Launchpad team but as I understand it bug filing should happen in the context of a project or distribution not just anywhere. Additionally, for Ubuntu bug filing should happen with-in the context of a package instead of being filed about the distribution as a whole. > But OK, fair enough, go to project home (launchpad.net), and select the > Ubuntu project. Now I do see a big label entitled "Report a Bug", > clicking on which takes me to a lengthy advertisement for Apport. Um, > OK, apport is a great idea, but if I could or wanted to use Apport I > WOULD HAVE DONE SO -- that's why I'm on f'ing bugs.launchpad.net! Well, not every Ubuntu user is aware of apport and ubuntu-bug hence the wiki page regarding it. Lots of bug reporters are first time Ubuntu users and are not aware of the tools available to them. > The server system I'm filing a bug for doesn't have any X packages > installed and is in a location far away. I only access it using ssh, > hence can't use the graphical interfaces described in the ReportingBugs > documentation. The ReportingBugs wiki page also has a section about "Filing bugs when off-line" which discusses how to use apport-cli to save a report that you can then report from another system with X and a browser. > However, I do need to file a bug, so continue to spin my wheels skimming > over information that is completely irrelevant. At some point I find: > > -- > If you can't file your report from the menu, for example: > > * You're using the Server Edition > * The application doesn't have the appropriate menu item > * The application won't start at all > * Your problem is not related to an application but is an > infrastructure component, such as the Linux kernel or graphics subsystem > > You can still help us by using ubuntu-bug. > - > > Oh really? Suppose, being a somewhat expert user, I happen to know > exactly what package I'm filing the bug against, exactly what > distribution I'm running, and exactly what I want to say in the bug > report to simplify the process of getting the bug triaged -- how does > ubuntu-bug help with that? Well, ubuntu-bug uses apport which will check for hooks regarding the package. These hooks are written by people familiar with the package and add additional information to the bug report that would be helpful in debugging the issue. Incidentally, samba now has a hook in Lucid. > Some anonymous bug report filed against a > package which is not actually crashing would appear to be somewhat less > than helpful. Of course I could be missing something, but just typing > >ubuntu-bug samba > > followed by selecting "Send Report" with 0.0 feedback as to what is > being sent and with no ability to state what the bug actually is appears > completely useless to me. If you were to use the off-line filing method a web browser would be opened where you could then provide feedback as to what you are sending. > Finally, many pages later I find what I'm looking for: the new and > improved way of filing bugs on launchpad.net, by using the link > http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect > > So what's my gripe now? How about a field allowing me to specify that > this bug applies to a *particular* Ubuntu distribution, rather than one > single textfield and a way to upload an attachment? The single textfield, the bug summary, is used to search for duplicates before you do any additional work of writing a complete description or uploading an attachment. I'm sorry you had a poor bug reporting experience but hope you understand that we are trying to get high quality bug reports by encouraging people to use tools that gather detailed information about their systems and environments. -- 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
Re: Triaging Bugs with Patches
On Wed, Feb 17, 2010 at 10:42:34PM -0500, Evan wrote: > I've been triaging a few bugs, and I came across a pair of bugs in libpcap > which had patches [1][2]. > I found and checked the wiki page on triaging bugs with patches [3], and > after completing the available steps, I ran into a wall. > > The complete text of the section describing what to do with a bug that has a > patch reads as follows: > > > In the event that [the patch] is not a debdiff one could incorporate the > > patch into a debdiff for the latest release of Ubuntu or apply the patch to > > a bzr branch of the package and link the branch to the bug report. > > If an attachment is a debdiff and applies to a recent version of the > > package the bug report needs to be > > sponsored<https://wiki.ubuntu.com/SponsorshipProcess>to the appropriate > > archive. This is done by subscribing (NOT assigning) the > > appropriate sponsorship team to the bug. For packages in main and restricted > > the ubuntu-main-sponsors team should be subscribed. For packages in the > > universe and multiverse repositories the ubuntu-universe-sponsors team > > should be subscribed. You can view their queues at > > main-sponsors<https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-main-sponsors>and > > universe-sponsors<https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-universe-sponsors> > > . > > > > 1) The two attached patches are simple diffs, not debdiffs - is there a way > to convert them, and could it be added to this page? This isn't exactly trivial as you would need to incorporate the patch in the package's patch system (if it has one) and update the changelog among other things. Some documentation that might help in this process, if you are interested, can be found at https://wiki.ubuntu.com/PackagingGuide/Complete. > 2) As a triager, how is one expected to be able to apply a patch to a bzr > branch, and what if the project isn't hosted on launchpad/bzr? This seems > more dev-related then triager-related. Most packages are available in bzr on launchpad so you could use bzr branch lp:ubuntu/libpcap. Unfortunately, this isn't the case for libpcap though. There is also a plugin so one can use bzr patch and the link to the patch on launchpadlibrarian. > 3) Is there a way to tell from a bug page which repository the package is > in? I eventually found it on the launchpad libpcap package page, but I > couldn't find any obvious indicator on the bug page itself. This should > probably be mentioned as well. When you mouse-over the package name in the bug task table you are presented with information about the latest package version and the repository it is from. I'll update the wiki page appropriately. > To my mind, once a bug has an attached patch which the triager can verify as > at least being potentially useful, there should be a simple button "flag as > patched". > This flag should ping the maintainer with something like: "Project X has a > ticket with a patch!". > The maintainer (or another dev) should then check the patch, commit it, and > close the bug. The bugs with patches are already flagged this way in bug listings, the dual band-aid icon, additionally e-mail notifications now indicate when attachments flagged as patches are added to bug reports. The sponsorship queue is a way to collate bug reports with patches across packages which is something that isn't easy to do in Launchpad. You can either view all the bugs with patches (quite a lot at the moment) or only one package's bugs with patches. > I'm not a workflow expert, so there may be reasons for the way the system is > currently set up, but it doesn't make sense to me. I agree that the current workflow isn't ideal but hope that I've helped clarify some of the process for you. > If the general consensus is that my points on the wiki are valid, I'll take > a shot at rewriting that section. I'll be taking a look at the wiki page also. -- 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
Re: bugreporting workflow improvement needed i think..
On Wed, Feb 24, 2010 at 11:24:40AM +0100, Rene Veerman wrote: > Hi.. > > While ubuntu-bug and launchpad are a pleasure to work with, i've > noticed something about the workflow of bugreports in the unix world a > few times now.. > > Often, a developer will claim a bugreport should be sent to a > component developer. By the original bugreporter. Who i suspect are > likely not to have time or clue enough to do that. I've done it a few > times, and it's plain frustrating.. Especialy if the other dev(-team) > wants to bounce it back again. It's like being a child and having to > pass messages between my parents in a fight in different rooms of the > house.. ;-) For the most part, if this activity occurs it should take place in Launchpad. I've seen bugs have multiple bug tasks open and developers discuss the issue in the bug report. There should be no need for you to pass messages of this sort in Launchpad. > Could you guys please go 1 step further, and build some kinda > infrastructure by which bugreports can be very easily forwarded (for > evaluation) to the developer team of another app/component.. The focus > should be conflict-resolution, the guts of which probably shouldnt be > world-viewable, but short status messages for the public would be > nice. I believe that this functionality is already built into Launchpad at least for Ubuntu and other projects. However, if it isn't or there is a deficiency in it this is best brought up with the Launchpad developers rather than Ubuntu ones. You can do this on the launchpad users mailing list. -- 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
Re: Bug: python2.5-minimal
On Thu, Mar 18, 2010 at 10:34:28AM +, Dmitrijs Ledkovs wrote: > On 15 March 2010 15:48, wrote: > > Hi All > > > > I am using this list for my bug report because using "ubuntu-bug" > > did not work. I could not establish a connection to the bug database > > (continuous errors). > > > > You can try https://bugs.edge.launchpad.net/ubuntu/+filebug in your > browser to file bugs in the future However, they'll be much more complete if you use ubuntu-bug and that should always be your first mechanism for reporting bugs about Ubuntu. -- Brian Murray Ubuntu Bugmaster Days running lucid: 37 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
Re: Touch Screen Issues
On Thu, Mar 18, 2010 at 05:32:27PM -0700, Brandon Kuczenski wrote: > Hello all, > > I want to inquire about the state of touchscreen development in Ubuntu. > I recently built a touch-screen-only system running Karmic and I'm > generally happy with it (the OS is pretty heavy weight, lots of caching > to disk, etc, but that is the way of things in this Aero-Aqua-world) but > the touch screen support is lacking. I'm using xorg-input-evtouch. I'm running Lucid on a touchscreen system and am not having many of the issues that you mention. I strongly recommend downloading Beta 1 and testing it, even as a Live CD, with your system. -- Brian Murray Ubuntu Bugmaster Days running lucid: 38 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
Re: Touch Screen Issues
On Sun, Mar 21, 2010 at 05:49:45PM -0700, Brandon Kuczenski wrote: > On Fri, 19 Mar 2010, Erik Andersen wrote: > > > > > > >I'm running Lucid on a touchscreen system and am not having many > >of the issues that you mention. I strongly recommend downloading > >Beta 1 and testing it, even as a Live CD, with your system. > > > > In particular, does click-and-drag work? Yes, it does. > > > >I was considering buying a touch screen and am curious: Are different > >screens more or less driver supported as far as touch (like wireless > >devices) or is it pretty standard (like usb devices)? > > > > I've only tried this one. It's USB- I plugged it in and checked > /var/log/messages to see what to google for. evtouch seems to be > pretty common and works fine just by installing the ubuntu package. > > It's completely unusable before it's been calibrated-- it thinks > "up" is "down" and the usable screen is only 1/2 size. So I ran the > calibration program from the console. My screen required no calibration in Lucid. -- Brian Murray Ubuntu Bugmaster Days running lucid: 41 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
Re: Touch Screen Issues
On Fri, Mar 19, 2010 at 08:21:26PM +, Caroline Ford wrote: > Do programs generally work okay or does it depend on libraries etc? The touchscreen and stylus control the pointer just the way a mouse would. -- Brian Murray Ubuntu Bugmaster Days running lucid: 42 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
Re: Missing OGRE plugin in libOgreMain-1.6.1 package
On Fri, Apr 16, 2010 at 11:49:01PM +0300, Hagai Hadad wrote: > Hi, > I've installed OGRE via synaptic and I found that it is missing a plugin. > In the file "plugins.cfg" (/etc/OGRE/plugins.cfg) there is this line: > Plugin=Plugin_EXRCodec.so > but "Plugin_EXRCodec.so" is not installed. It'd be best if you were to report this as a bug in Launchpad using the command 'ubuntu-bug ogre'. In the event that you don't decide to use ubuntu-bug and file a report manually in Launchpad it'd be helpful if you were to include information about the specific package version and release of Ubuntu you are using. -- Brian Murray Ubuntu Bug Master 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
Re: How long is the queue for SRU requests?
On Fri, Jun 11, 2010 at 07:46:08AM -0400, Evan wrote: > I submitted a couple of SRU requests a while ago (for Lucid), and they > haven't been looked at yet. I'm sure the SRU team is quite busy given > that Lucid is an LTS, but I was wondering approximately how long is > expected between submitting a request and it getting looked at by a > member of the team. I'm starting to wonder if I missed a step. It'd be helpful if you were to provide some information so somebody could look into this issue. Something like a bug number or information about what you mean by "SRU requests". Did you nominate a bug for Lucid? Did you add a debdiff to a bug report? -- Brian Murray Ubuntu Bug Master 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
Re: HeadPhone
On Fri, Jun 11, 2010 at 12:46:41PM +0530, Muhammad Babar Shahzad wrote: > My Del vostro 1014 with ubuntu 10.04 do not mute whenever a headphone > jak is connected this problem is with all vostro 1014 laptops. For help of this nature your best bet is to ask a question about this in Ubuntu's answer tracker at http://answers.launchpad.net/ubuntu/. -- Brian Murray Ubuntu Bug Master 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
Re: Busy work
On Fri, Feb 04, 2011 at 12:44:55PM +, Reuben Thomas wrote: > Just now, I got a notification about a bug I filed two and a half years ago: > > https://bugs.launchpad.net/ubuntu/+source/pmount/+bug/237361 > > It's a trivial man page formatting bug. > > In the last two and a half years, it has twice received the attentions > of Ubuntu developers. Once, two months after I filed it; once, just > now. Each time the developer changed some tags. > > Now, I don't want to downplay the importance of correct tagging of > bugs, but, as I said, this is a trivial documentation bug. How about > just fixing it? > > I see this happen again and again. It's sad, because it is not a good > use of Ubuntu dev time, and the bug often takes ages to get fixed. I appreciate your frustration and I'm sorry that we don't have time to handle every bug report to everyone's satisfaction. Having said that it you are making an assumption that the people changing tags on this bug report are developers. The Ubuntu community includes more than just developers, there are also bug triagers, documentation writers, translaters and artists just to name a few. Its entirely possible that the person tagging your bug was not a developer and may not be a position to "just fix it". -- Brian Murray Ubuntu Bug Master 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
Re: Lunar Lobster (23.04) UI Freeze
On Thu, Mar 16, 2023 at 09:31:52AM -0700, Erich Eickmeyer wrote: > Hi Paride, > > As I understand it, this wasn't supposed to go out until EoD US Pacific Time > (UTC -0700) which would place it at basically UTC 1100, if my math is > correct. With that, could we have some more time before this officially goes > into effect? There was some miscommunication among the mailing list moderators and the email was allowed through a bit earlier than planned. Yes, you can have a few more hours. Brian -- 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: apport feature request
On Wed, May 23, 2007 at 10:00:50PM +0200, Thilo Six wrote: > Hello > > Today i did some triage a came across apport generated bugs. > Following request/suggestion: > apport adds some environment data to the bug report (ExecutablePath, $PATH > kernel). > I was told that in some circumstances an apport bug can have less usefull > information e.g. when that report was generated with an older version of > apport that might have bugs that were fixed later. Actually what I meant was that there are probably some apport generated bug reports about older versions of packages. For example an automated apport crash report, submitted during Feisty's development cycle, about an older version of OpenOffice.org than is currently available in Feisty. I apologize for any confusion. -- 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
More Bug Statistic Graphs
Kees Cook's reimplementation[0] of Carthik's bug graphs prompted me to start graphing too. In addition to the total Ubuntu bug's graph[1], with a new 365 day view, in the "test" graphs area[2] you can find graphs of packages with more than 100 bugs, one of desktop team bugs and one of new bugs without a package. [0] https://lists.ubuntu.com/archives/ubuntu-bugsquad/2007-July/000601.html [1] http://people.ubuntu.com/~brian/graphs/ [2] http://people.ubuntu.com/~brian/testing_graphs/ -- 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
Re: That need to close bugs?
On Wed, Sep 12, 2007 at 07:06:29AM +0800, Onno Benschop wrote: > That is fine if the bug is likely to be a one-off-non-repeatable > offender, like say a corrupt file on a file system that has been > erased > and reformatted. But I don't think that this bug is in that class. > Having a bug like this closed means there is little chance for casual > visitors to stumble on the bug and link the report to the behaviour > they're seeing. The fact that the bug is Invalid does not mean that the bug does not show up for a casual visitor to Launchpad. I would imagine this casual visitor would submit a new bug report and that process shows you Invalid bugs. I tested this by submitting a new bug report about the linux-source-2.6.15 package with prism54 in the subject and quite a few Invalid bug reports showed up in the "Is the bug you're reporting one of these?" dialog. > Most of my personal linux troubleshooting revolves around googling for > output seen on syslog. With a closed bug like the one Alexandre showed > us, do not show up as far as I know. I don't think that Google would selectively index bug reports based on their state. You should be able to craft a Google search using something like "site:launchpad.net inurl:bugs intitle:Bug" and a search string to prove this. While slightly contrived I used a specific bug number, 112283, which is currently Invalid and it showed up in Google. -- 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
Re: That need to close bugs?
On Wed, Sep 12, 2007 at 06:57:28AM +0800, Onno Benschop wrote: > It is good that you raise this issue in my opinion. I too have seen this > kind of behaviour and wondered what to do about it. I wondered if adding > a comment to the bug would help, but found no particularly transparent > or productive way to engage the person closing the bug. The Ubuntu kernel team has specified that certain minimum bug requirements be met[0] for a bug report regarding their packages - linux-source-2.6.15 in this case. The particular bug report mentioned did not meet the kernel team's minimum requirements and subsequently was closed. As they are most familiar with the kernel and the maintainer of those packages I think it is important to follow their guidelines. > I'm almost wondering if it's happening because you get karma from > closing a bug. Personally, I am not closing bugs to gain karma. I am employed by Canonical to improve the quality of Ubuntu especially via its bug reports. Additionally, as far as I know you can't do anything with Launchpad karma. > From my perspective, closing a bug like this adds to the workload > because now there needs to be effort in combining and locating duplicate > bugs, some of which have been closed like this. It makes the overall > bug-list smaller, but it does in my opinion not create a better signal > to noise ratio. I have seen cases where the combined mass of partial > information was enough to locate the source of a bug. As Matthew Paul Thomas mentioned in a different e-mail it is important to make efficient use of the QA team. While having a lot of bugs in the "Incomplete" state would be one way of dealing with bugs with insufficient information, it would create more "noise" in that there would be more bug reports in the QA team's queue which are not particularly useful. Also as I mentioned in my other e-mail the fact that the bug is Invalid does not delete it from Malone or hide it from all search results. Furthermore, there is nothing to prevent someone from combining multiple partial Invalid bugs into a complete Confirmed one. [0] https://wiki.ubuntu.com/KernelTeamBugPolicies -- 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
Re: That need to close bugs?
On Tue, Sep 18, 2007 at 10:11:49AM +0200, Reinhard Tartler wrote: > Sarah Hobbs <[EMAIL PROTECTED]> writes: > > > As one of those who triages various KDE bugs...in the area of KDEBase, > > in particular, there are around 450 open bugs, we *have* to close > > invalid bugs. There are around 750, with the INVALID and WONTFIX bugs > > included. > > Please correct me, but I suspect that when you mean "we have to close > invalid bugs", I think you actually mean "we need to filter out those > incomplete bugs which we don't have the ressources for investiagting > further from 'our' 'default' bug listings". (YMMV of course what is > "your default" bug listing. > > I think tags could help you here, right? One tag that I have been using is 'needs-devrelease-testing'. My thought was that this tag would identify bugs that there is enough information to try and reproduce them or that requires specific hardware, but the original reporter has not given enough information for someone to debug the problem. -- 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
Re: Bug(s) that should be fixed for release
On Wed, Oct 03, 2007 at 09:35:18PM -0400, Todd Deshane wrote: > Hi All, > > Is there a running list of key bugs that are planned to be fixed > before the release? Bugs that have a milestone for the development release can be found at: https://launchpad.net/ubuntu/+milestone/ubuntu-7.10-rc -- 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
Re: Hug Day - 09 January 2008
On Mon, Jan 07, 2008 at 08:58:01PM +0100, Mathias Florian Menzer wrote: > Hi Brian! > > It would be much better, if future Hug Days could be announced some more > time in advance. We could then reach more people when publishing this in > forums and Newsposts. If the Hug Days are on Wednesday when would you like to find out about it? Should the list of bugs be finalized when the announcement is sent out? Thanks, -- 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
Re: Hardy Alpha-3 networking
On Sat, Jan 12, 2008 at 11:45:22PM -0600, Richard Mancusi wrote: > Desktop i386 install > > Is the following a bug or can anyone change network > settings via System/Administration/Network > And can you verify it really changed by looking in the > appropriate file. You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an "Unlock" button and selections remain greyed out until I unlock the application. If your system is fully up to date and the "Unlock" button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, -- 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
Re: About "Windows Client Integration" blueprint
On Thu, Jan 31, 2008 at 08:29:20AM -0800, George Farris wrote: > On Wed, 2008-01-30 at 19:04 +0100, Fabrizio Balliano wrote: > > Hi to all, > > I'm following with a lot of interest this blueprint for hardy: > > https://blueprints.launchpad.net/ubuntu/+spec/windows-authentication-integration > > which will allow users to easily authenticate agains an active directory. > > > > That blueprint is marked "essential" but I can't find any info about > > the development progress, I also wrote the author but I got no answer. > > Does anyone have info about that? > > So, is there any movement on this stuff? Seems one of those "must > haves" to move Ubuntu into more serious enterprise usage. This looks like a server team blueprint to me so you might try their specific mailing list. -- 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
Re: libc borked
On Thu, Mar 13, 2008 at 02:00:03AM -0400, Scott Kitterman wrote: > On Wed, 12 Mar 2008 23:30:14 -0400 "Todd Deshane" <[EMAIL PROTECTED]> > wrote: > >Cory, > > > >Please read: > >http://www.ubuntu.com/community/conduct > > > >Also, you didn't provide any useful information. Bug reports, versions, > etc. > > > >If it is hardy then you should expect things to break from time to time. If > >it is a stable release, then you should report bugs appropriately. > > > >The developers work hard and they don't need such a negative response and > >shouldn't be expected to drop everything and fix your problem. > > > >Please provide useful information and I am sure if it is a critical bug, it > >will be fixed in due time. > > > >Are you paying for support? or are you demanding things from volunteers? > > > >Would you treat providers of other services that you get such as Internet > or > >Phone, etc. the same way? > > > >Best Regards, > >Todd > > > Todd, > > I don't know who you are or what your involvement with Ubuntu is, but > anyone who is involved in Ubuntu development (as Cory is) and has been on > IRC in the last several hours is well aware of exactly what is wrong. None > of those details are particularly needed. One thing this, and some other events, has made me think about is - how are new community members supposed to know who someone is and what their contributions to Ubuntu have been? We have a developer responsibilities wiki page[1] perhaps we should publicize it more and flesh it out. As I personally have a hard time keeping people's irc nicks, launchpad usernames and real names connected, I'm adding irc nicks to that page too. What other ways can we help new community members identify people involved in Ubuntu development? [1] https://wiki.ubuntu.com/DeveloperResponsibilities -- 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
