[Bug 482103] Re: Submitted Bug Report Disappeared
*** This bug is a duplicate of bug 5977 *** https://bugs.launchpad.net/bugs/5977 ** This bug is no longer a duplicate of bug 1089111 closed bugs are not visible ** This bug has been marked a duplicate of bug 5977 Person's related bugs pages do not show closed / duplicate bug reports -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/482103 Title: Submitted Bug Report Disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/482103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834082] Re: Cannot target a bug to a series from an existing series task
I've QA'ed this and things look fine in terms of everything working correctly in the standard case and being ok to deploy. I'm waiting to hear from Kate about if the her playing on qastaging confirms the bug is fixed for her. ** Tags removed: qa-needstesting ** Tags added: qa-ok -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834082 Title: Cannot target a bug to a series from an existing series task To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/834082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834082] Re: Cannot target a bug to a series from an existing series task
** Branch linked: lp:~deryck/launchpad/target-series-bug-834082 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834082 Title: Cannot target a bug to a series from an existing series task To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/834082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 836935] Re: upload rejected for files with a time stamp too far in the past
FWIW, on the Launchpad side, we do indeed do the rejection on our side, but we'll accept packages dated as far back as 1984. This seems like we're trying to match Debian since Colin notes the same check. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/836935 Title: upload rejected for files with a time stamp too far in the past To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/836935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 836935] Re: upload rejected for files with a time stamp too far in the past
I'm closing the Launchpad task based on Colin's explanation here. Thanks, Colin! ** Changed in: launchpad Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/836935 Title: upload rejected for files with a time stamp too far in the past To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/836935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834082] Re: cannot target to series or update assigned to for oneiric-targeted ubuntu bugs
** Changed in: launchpad Assignee: (unassigned) = Deryck Hodge (deryck) ** Changed in: launchpad Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834082 Title: cannot target to series or update assigned to for oneiric-targeted ubuntu bugs To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/834082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834082] Re: Regression? can not target to series or update assigned to for ubuntu bugs
I spent some time today trying to work out with Kate what's going on. It seems that it's only from series URLs that she's having problems. She can get work done by manually dropping the oneiric from the url and using the distro or source package view of the bug. I've added this to the Orange Squad kanban board for someone to pick up as soon as is possible. ** Summary changed: - Regression? can not target to series or update assigned to for ubuntu bugs + cannot target to series or update assigned to for oneiric-targeted ubuntu bugs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834082 Title: cannot target to series or update assigned to for oneiric-targeted ubuntu bugs To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/834082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 814577] Re: The following packages have unmet dependencies
** Also affects: clamav (Ubuntu) Importance: Undecided Status: New ** Changed in: launchpad Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/814577 Title: The following packages have unmet dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/814577/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 814577] Re: The following packages have unmet dependencies
** Also affects: clamav (Ubuntu) Importance: Undecided Status: New ** Changed in: launchpad Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/814577 Title: The following packages have unmet dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/814577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 813545] Re: Launchpad's package chooser at odds with the Launchpad bug reporter
*** This bug is a duplicate of bug 42298 *** https://bugs.launchpad.net/bugs/42298 ** This bug has been marked a duplicate of bug 42298 package picker lists unpublished (invalid) packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/813545 Title: Launchpad's package chooser at odds with the Launchpad bug reporter To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/813545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562706] Re: On i386, selecting the ubuntu studio packages fails to install
** Changed in: launchpad Status: New = In Progress ** Changed in: launchpad Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/562706 Title: On i386, selecting the ubuntu studio packages fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/562706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 683159] Re: With touchpad browser tab sometimes closes when selected
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Project changed: malone = null -- With touchpad browser tab sometimes closes when selected https://bugs.launchpad.net/bugs/683159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661278] Re: Cannot install linux-image-2.6.35-22-generic_2.6.35-22.34_amd64.deb
** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: malone Status: New = Invalid -- Cannot install linux-image-2.6.35-22-generic_2.6.35-22.34_amd64.deb https://bugs.launchpad.net/bugs/661278 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Presence Service at https://launchpad.net/sugar-presence-service What's going to change --- Right now, the bug expiry option is enabled for Presence Service but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Presence Service. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/sugar-presence-service/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- Ubuntu-sugarteam mailing list Ubuntu-sugarteam@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-sugarteam
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Edgy Backports at https://launchpad.net/edgy-backports What's going to change --- Right now, the bug expiry option is enabled for Edgy Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Edgy Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/edgy-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Breezy Backports at https://launchpad.net/breezy-backports What's going to change --- Right now, the bug expiry option is enabled for Breezy Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Breezy Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/breezy-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Dapper Backports at https://launchpad.net/dapper-backports What's going to change --- Right now, the bug expiry option is enabled for Dapper Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Dapper Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/dapper-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Feisty Backports at https://launchpad.net/feisty-backports What's going to change --- Right now, the bug expiry option is enabled for Feisty Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Feisty Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/feisty-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Intrepid Ibex Backports at https://launchpad.net/intrepid-backports What's going to change --- Right now, the bug expiry option is enabled for Intrepid Ibex Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Intrepid Ibex Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/intrepid-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Edgy Backports at https://launchpad.net/edgy-backports What's going to change --- Right now, the bug expiry option is enabled for Edgy Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Edgy Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/edgy-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Hoary Backports at https://launchpad.net/ubp-hoary What's going to change --- Right now, the bug expiry option is enabled for Hoary Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Hoary Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/ubp-hoary/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project lucid-backports at https://launchpad.net/lucid-backports What's going to change --- Right now, the bug expiry option is enabled for lucid-backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including lucid-backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/lucid-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Feisty Backports at https://launchpad.net/feisty-backports What's going to change --- Right now, the bug expiry option is enabled for Feisty Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Feisty Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/feisty-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Breezy Backports at https://launchpad.net/breezy-backports What's going to change --- Right now, the bug expiry option is enabled for Breezy Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Breezy Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/breezy-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Intrepid Ibex Backports at https://launchpad.net/intrepid-backports What's going to change --- Right now, the bug expiry option is enabled for Intrepid Ibex Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Intrepid Ibex Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/intrepid-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Dapper Backports at https://launchpad.net/dapper-backports What's going to change --- Right now, the bug expiry option is enabled for Dapper Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Dapper Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/dapper-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Jaunty Jackalope Backports at https://launchpad.net/jaunty-backports What's going to change --- Right now, the bug expiry option is enabled for Jaunty Jackalope Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Jaunty Jackalope Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/jaunty-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Hardy Backports at https://launchpad.net/hardy-backports What's going to change --- Right now, the bug expiry option is enabled for Hardy Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Hardy Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/hardy-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Karmic Backports at https://launchpad.net/karmic-backports What's going to change --- Right now, the bug expiry option is enabled for Karmic Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Karmic Backports. What this means for your project If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire Incomplete bug reports when they become inactive' option on this page: https://bugs.launchpad.net/karmic-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this - Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 566255] Re: No network Bug 'Add Comment' error not helpful.
*** This bug is a duplicate of bug 521447 *** https://bugs.launchpad.net/bugs/521447 ** This bug is no longer a duplicate of bug 504112 Incomplete error message when submitting comment fails ** This bug has been marked a duplicate of bug 521447 Uninformative error message * You can subscribe to bug 521447 by following this link: https://bugs.edge.launchpad.net/lazr-js/+bug/521447/+subscribe -- No network Bug 'Add Comment' error not helpful. https://bugs.launchpad.net/bugs/566255 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 618579] Re: Register Ubuntu Forum
This is not a problem with Launchpad, so I'm marking the Launchpad task invalid. I'm not sure where to file the bug against Ubuntu, though. ** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: launchpad Status: New = Invalid -- Register Ubuntu Forum https://bugs.launchpad.net/bugs/618579 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604684] Re: bug subscribe / unsubscribe option dosent work
Can you give me some more info to help reproduce this? How does it not work? Does this happen for every bug? Screenshots might help, too, if something is not firing off correctly in the UI. Cheers, deryck ** Changed in: malone Status: New = Incomplete -- bug subscribe / unsubscribe option dosent work https://bugs.launchpad.net/bugs/604684 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595124] Re: A bug's can_expire attribute is confusing
** Changed in: malone Assignee: (unassigned) = Brian Murray (brian-murray) ** Changed in: malone Status: Triaged = Fix Committed ** Changed in: malone Milestone: None = 10.08 -- A bug's can_expire attribute is confusing https://bugs.launchpad.net/bugs/595124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Fwd: Re: How to use the new Launchpad status?
Hi, Martin. On Thu, Jul 8, 2010 at 1:10 AM, Martin Pitt martin.p...@ubuntu.com wrote: Hello Brian, Micah Gersten [2010-07-07 20:06 -0500]: Forwarding Brian Murray's response from the ubuntu-bugsquad list. As an example there might be a bug about Ubuntu bug reports not being fixed which will not stay in an Invalid status because that issue happens to be an important matter to a lot of people. Â Subsequently, setting a bug like that to Opinion may be a useful thing to do. This seems like a prime example what Opinion should _not_ be. If a bug cannot be fixed, then no amount of but this sucks! exclamations will change this. So that bug should really be Invalid. A better approach to this would IMHO be to make it much harder to reopen bugs which are in a terminal state (fix released, wontfix, invalid). Brian and I have been discussing this offline, and I wanted to jump in here if that's okay. :-) I agree that making bugs in a terminal state more fully closed or locked down is a worthwhile goal. We have plans to do some bits of what people want in this regard, and in fact, at the same time as we began discussing the Opinion status, we accepted a patch to make Won't Fix ACLed so that only bug supervisors can un-set it. If you want to lock the status of a closed bug, you should be using Won't Fix. We aren't going to move ahead with other lock down techniques like this until we finish reviewing the success of the Opinion status on its own merits. Meaning, we don't want to introduce too many changes around closed bug statuses at once, so our stats about the usefulness of Opinion are good. The current plan is to review the effectiveness of this status in 3 months. I agree it's not entirely clear that Opinion is a closed bug status, but it is. It works just like Invalid. It is only named differently, and it is meant to convey the idea that: this bug is closed but a difference of opinion remains. It's a social status, and should be used as such. I agree with Brian's assessment that it should be used rarely or as a last resort. It is for a particular social situation only, i.e. bugs that won't remain closed because of that remaining difference of opinion. Now as to whether or not Ubuntu developers or the bug squad use the status at all, that is, of course, entirely up to you all. If you don't find the status useful, that is another data point about its effectiveness. However, I hope someone will use it, so that we have some data about how effective it is in the situation it's designed for. Cheers, deryck -- Deryck Hodge https://launchpad.net/~deryck http://www.devurandom.org/ -- 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
[Bug 595124] Re: Launchpad's can_expire not being reset when comments added.
I've had a look now. can_expire is a wrapper around findExpirableBugTasks, which only looks at date_last_updated and not date_last_message. We should extend the query in findExpirableBugTasks to consider date_last_message. While I think this is an easy bug to fix, I'm hesitant to tag it trivial, as I have this theory that ultimately no malone bug is trivial. But this is an easy one, definitely. ** Changed in: malone Importance: Undecided = High ** Tags added: dhrb easy ** Changed in: malone Status: New = Triaged -- Launchpad's can_expire not being reset when comments added. https://bugs.launchpad.net/bugs/595124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595124] Re: Launchpad's can_expire not being reset when comments added.
Setting this back to New to make sure I take a look today. ** Changed in: malone Status: Confirmed = New -- Launchpad's can_expire not being reset when comments added. https://bugs.launchpad.net/bugs/595124 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584962] Re: Bugs sidebar overlaps main content
** Tags added: dhrb ** Description changed: launchpad The bug reporting and other tools website launchpad.net doesnt work well in resolution of 1024*768.the menus are getting overlapped.please correct it soon. + + This could be considered when fixing Bug #593015. -- Bugs sidebar overlaps main content https://bugs.launchpad.net/bugs/584962 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 424849] Re: Launchpad should batch attachment notification emails
Thanks for the detailed explanation, Graham. That meshes with my understanding of what we do, too. That is a nice example of the advantage to sending mail from the bug rather than the person, but I think it should be a separate concern and we should consider this bug fixed when we batch attachments from the same person. That's an easy fix and and easy win. We should open a bug about batching comments themselves, assuming we can find a nice way to do that. I would have thought that bug existed, but I cannot find one. Otherwise, as Graham says, we do this genrally okay now. It's just not obvious to people because comments are common, frequent, and can break batching of other changes in unexpected ways. Cheers, deryck -- Launchpad should batch attachment notification emails https://bugs.launchpad.net/bugs/424849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 424849] Re: Launchpad should batch attachment notification emails
Don't we batch in 5 minute (or some such) intervals now? Except for comments and attachments, of course. I thought that was the point of this bug, to enable batching for attachments. -- Launchpad should batch attachment notification emails https://bugs.launchpad.net/bugs/424849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584442] Re: launchpad crashses all the time when I try to submit a bug report
We need more info to debug what's happening. Is this a timeout or some other error? Can you comment and give us the OOPS number that you received? Also, the exact URL when you get the error is helpful, too. Thanks. ** Changed in: malone Status: New = Incomplete -- launchpad crashses all the time when I try to submit a bug report https://bugs.launchpad.net/bugs/584442 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566255] Re: No network Bug 'Add Comment' error not helpful.
*** This bug is a duplicate of bug 504112 *** https://bugs.launchpad.net/bugs/504112 ** This bug has been marked a duplicate of bug 504112 Incomplete error message when submitting comment fails -- No network Bug 'Add Comment' error not helpful. https://bugs.launchpad.net/bugs/566255 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564017] Re: thunderbird will not start
** Also affects: mozilla-thunderbird (Ubuntu) Importance: Undecided Status: New ** Changed in: malone Status: New = Invalid -- thunderbird will not start https://bugs.launchpad.net/bugs/564017 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538097] Re: +storeblob fails with 500 Internal server error on production (works on edge)
** Changed in: malone Status: Confirmed = Triaged ** Changed in: malone Importance: Undecided = High ** Changed in: malone Milestone: None = 10.03 ** Tags added: oops -- +storeblob fails with 500 Internal server error on production (works on edge) https://bugs.launchpad.net/bugs/538097 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532143] Re: apport's ubuntu-bug xserver-xorg-input-wacom creates a bug for nvidia-graphics-drivers
I don't think there's anything for us to do about this on the Launchpad Bugs end of things. If I'm misunderstanding the problem, though, please reopen and help me understand. Cheers, deryck ** Changed in: malone Status: New = Won't Fix -- apport's ubuntu-bug xserver-xorg-input-wacom creates a bug for nvidia-graphics-drivers https://bugs.launchpad.net/bugs/532143 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357358] Re: Apport should make clear to non-technical users what happens when submitting or subscribing to a bug report
The report a bug page language has been deliberately crafted, and I don't think the suggestions here are changes we would make. I think subscribing when you a file a bug is reasonable, though I did filed Bug #485627 about not subscribing people automatically when a bug is marked a dupe. Bug #484291 has some ideas about making sure people are informed about their reply to mails. Also, we recently fixed Bug #48863 to always add an unsubscribe link to emails for direct subscribers. So given that we likely wouldn't do any of point #1's suggestions, and given that all of #2's suggestions are covered by other bugs, I'm closing this as invalid for malone. If there are other concrete ideas here that are missed, feel free to open new bugs about those specific issues. ** Changed in: malone Status: New = Invalid -- Apport should make clear to non-technical users what happens when submitting or subscribing to a bug report https://bugs.launchpad.net/bugs/357358 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 457186] Re: Incomplete Status should not be assigned until attempt to complete is made.
I don't see a bug here. It's a suggestion for how to use the incomplete status, and every project using Launchpad will have different ideas of how to use a given status. ** Changed in: malone Status: New = Invalid -- Incomplete Status should not be assigned until attempt to complete is made. https://bugs.launchpad.net/bugs/457186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 436417] Re: acerhdf: unknown (unsupported) BIOS version Acer /Aspire 7720Z /V1.45
** Also affects: ubuntu Importance: Undecided Status: New ** Project changed: malone = null -- acerhdf: unknown (unsupported) BIOS version Acer /Aspire 7720Z/V1.45 https://bugs.launchpad.net/bugs/436417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 402821] Re: Alt-Tab of a minimized window only shows icon
** Project changed: dead-ayatana = hundredpapercuts -- Alt-Tab of a minimized window only shows icon https://bugs.launchpad.net/bugs/402821 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 29560] Re: drag drop improvement: delay bringing window to front until mouse released
** Project changed: dead-ayatana = hundredpapercuts -- drag drop improvement: delay bringing window to front until mouse released https://bugs.launchpad.net/bugs/29560 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388633] Re: ComboBox has a big blank area above the position of its control
** Project changed: dead-ayatana = hundredpapercuts -- ComboBox has a big blank area above the position of its control https://bugs.launchpad.net/bugs/388633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388593] Re: Wifi auto-connection asks for keyring password
** Project changed: dead-ayatana = hundredpapercuts -- Wifi auto-connection asks for keyring password https://bugs.launchpad.net/bugs/388593 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387573] Re: Drop-down calendar does not close unless you click on it
** Project changed: dead-ayatana = hundredpapercuts -- Drop-down calendar does not close unless you click on it https://bugs.launchpad.net/bugs/387573 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124315] Re: remember window position of applications
** Project changed: dead-ayatana = hundredpapercuts -- remember window position of applications https://bugs.launchpad.net/bugs/124315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421414] Re: Algoscore [needs packaging]
** Also affects: ubuntu Importance: Undecided Status: New ** Project changed: malone = null ** Tags added: needs-packaging -- Algoscore [needs packaging] https://bugs.launchpad.net/bugs/421414 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
