[08:38] <flexiondotorg> bdmurray, I've just joined the bug squad and maintain packages in Debian (that are synced directly with Ubuntu) which have very old bugs for now unsupported versions of Ubuntu.
[08:38] <flexiondotorg> Those bugs are also for old and unsupported versions of the packages too.
[08:39] <flexiondotorg> Is it OK to close those bugs by simply stating they are EOL?
[09:07] <rbasak> flexiondotorg: the bugs might still exist in current versions though?
[09:07] <flexiondotorg> Not likely, the package in questions is gnome-main-menu.
[09:08] <flexiondotorg> Which is now maintained by the MATE team for the MATE Desktop.
[09:08] <flexiondotorg> Some of the bugs relate to technologies no longer present in gnome-main-menu.
[09:08] <rbasak> flexiondotorg: it's frustrating for a bug reporter to report a bug, wait years for an answer, and then have them closed as EOL. So I always try to be friendly in my close messages, invite the user to reopen if it still applies, etc.
[09:08] <rbasak> flexiondotorg: sounds like that might not apply here though
[09:08] <flexiondotorg> Yep, completely agree with the sentiment.
[09:09] <flexiondotorg> And would of course add a "if still present in the current please re-open."
[09:09] <rbasak> flexiondotorg: OTOH, it makes no sense to keep a bug open if no developer is expected to be able to make progress on it. One of Incomplete, Invalid, Won't Fix is better than New and languishing in that case, and I try and explain that in a comment when changing it.
[09:10] <flexiondotorg> OK.
[09:10] <flexiondotorg> rbasak, Anyway, I'm new here so don't want to do the "wrong thing".
[09:11] <flexiondotorg> Baby steps.
[09:12] <rbasak> I think anything is fine as long as you're polite, explain your reasoning, are explicitly open to criticism and reconsider (eg. ask here as you're already doing) if others disagree. So you're doing exactly the right thing :)
[15:18] <goddard> i'm having an issues on wily werewolf but it is never registered as a bug.  Basically the laptop will wake from suspend properly, but then go back into a suspend mode at random intervals.  I have to wake it up by pressing a button on my keyboard and then it will wake up.  Shortly after that it will go into suspend on its own again.  It does this over and over again unless I reboot.
[15:18] <goddard> using a razer blade 2015 with closed drivers
[15:19] <teward> goddard: #ubuntu+1 for wily support
[15:19] <goddard> https://bugs.launchpad.net/ubuntu?field.searchtext=after+waking+up+from+suspend+screen+blacks+out&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&
[15:19] <goddard> field.has_patch=&field.has_no_package=
[15:24] <teward> goddard: #ubuntu+1 is where you're going to have to start.  If the issue is not a bug on Wily, you should file a bug.
[15:24] <teward> See https://help.ubuntu.com/community/ReportingBugs for a starting point on how to report bugs.