From noreply at ubuntu.com Tue Oct 4 19:03:59 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Tue, 04 Oct 2011 19:03:59 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?=
=?utf-8?q?till-kamppeter?=
Message-ID: <20111004190359.13617.34384@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "DebuggingPrintingProblems" page has been changed by till-kamppeter:
http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=61&rev2=62
1. Make sure that the printer is connected to your system and powered on.
2. Open a terminal/console and check if the usb kernel modules are loaded: <
> {{{$ lsmod | grep usb}}}
- 3. Unplug the USB printer cable from your computer and enter this command: <
> {{{$ tail -f /var/log/messages }}}
+ 3. Unplug the USB printer cable from your computer and enter this command: <
> {{{$ tail -f /var/log/syslog }}}
4. Reconnect the USB printer cable, you should see some messages appearing.
5. Press Ctrl-C to stop the logging.
6. Check whether the printer gets correctly detected by the USB subsystem and determine its USB vendor/product IDs and the USB bus and device addresses: <
> {{{$ lsusb}}} <
> Note: The USB bus and device addresses change if you turn off or unplug the printer. Please re-run this command if needed.
From noreply at ubuntu.com Tue Oct 4 21:03:45 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Tue, 04 Oct 2011 21:03:45 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_alexlauni?=
Message-ID: <20111004210345.10469.14794@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Unity/FilingBugs" page has been changed by alexlauni:
http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=46&rev2=47
|| Bug reported from clutter based Unity || This bug was reported against an old version of Unity. The new version of Unity is almost an entire rewrite based on very different technologies. Could you please check if this issue is present in the current version, and if it is reopen the bug to a NEW status. || Set the bug to WONTFIX, and let the user reopen it ||
|| Bug report on a development snapshot or with no recent activity || This bug was reported on a development snapshot of Unity but lacks elements for it to be actionable:<
>- there seems to be no reports of further occurences of the issue<
>- the bug cannot be reproduced reliably<
>- the information provided is not sufficient to track down the issue to a particular programming error.<
>Could you please check if this issue is present in the current version, and if it is reopen the bug to a NEW status. || Set the bug to INVALID, and let the user reopen it ||
|| Bugs that don't appear to be Unity related at all || The issue you're describing doesn't sound related to Unity. Could you log into a classic gnome session and see if this issue persists? || ||
- || Crashers for which you'd like the user to get a stack trace || Could you please follow the instructions on https://wiki.ubuntu.com/Unity/FilingBugs#Getting%20a%20stack%20trace and attach unity.log to this bug report? || ||
+ || Crashers for which you'd like the user to get a stack trace || Could you please follow the instructions on https://wiki.ubuntu.com/Unity/FilingBugs#Getting_a_stack_trace and attach unity.log to this bug report? || ||
= Canned "Call for Help" Template =
From hggdh2 at ubuntu.com Wed Oct 5 19:05:03 2011
From: hggdh2 at ubuntu.com (C de-Avillez)
Date: Wed, 05 Oct 2011 14:05:03 -0500
Subject: Feedback from current mentees
Message-ID: <4E8CAA5F.9070007@ubuntu.com>
I sent an email to the mentorship-alpha team on Sep 8th:
"We would like to have the feedback of the current mentees:
1. What are you doing now in regard to the mentorship programme?
2. Since you started, how many bugs have you worked on? Give an
estimate -- 1, 10, 100, 1000, etc.
3. What did you expect from the mentorship programme? Please be as
detailed as possible.
4. What did you *get* from the mentorship programme? Again, please
be as detailed as poosible.
I intend to query LP for the activities of each of your, as another
datum we will use for analysis."
This team, currently, has 17 active members: 10 mentors, and 7 mentees.
I received 5 responses from mentees to the email; a summary follows:
* of the five, 1 has worked on 100-200 bugs, one did not specify, and 3 have worked on 10 or less bugs;
* All comment (or agree with somebody else's comment) that the mentorship process is confused;
* there is an expectation of a more active involvement from the mentors;
* documentation should be pointed out (my words);
* the sheer amount of bugs and packages involved makes startup more challenging;
* there is need for a communications venue (mailing list, etc).
* mentors should be more proactive (as opposed to basically reactive, as of now).
MY VIEW
I agree and disagree (as, I guess, could be expected) with these positions; right now, though, I do agree that the programme needs to be reviewed, and either adjusted or terminated. Here it is why, in no specific order:
1. there is a confusing message we pass over everywhere: "triaging is easy", "this is how you start, then you go to more difficult things, like development", etc.
These are very wrong messages to pass.
To begin with, triaging is NOT easy: one must understand the program being used, sieve the actual issue out of an usually confusing babble, decide if it is indeed a bug, verify documentation attached, etc, etc, etc. Secondly, there are thousands of packages; even if one restricts work to a few of them, it will still be a daunting task. Add to the above all the packaging details, interaction with multiple -- and some rather different -- upstreams, and we have the perfect recipe for the confusion the mentees allude to.As the cream on the top, add the common difficulties of dealing with people that are aggressive, or lack communication skills, or that what they state is lost in translation.
2. There is another miscommunication going on: although we did state on the welcoming email, that the mentorship-alpha ML was one media to be used, we do not see much from mentees, neither on the ML, nor on IRC.
3. we have very few requirements on accepting a mentee; most importantly, I think we miss a critical requirement: the mentee *must* work on bugs; not doing so will be delaying access to other to-be mentees.
4. I still think the ML is a good idea; I think most of the folks beginning here are afraid (or, perhaps better, worried of being considered incapable) if they ask "dumb" questions. So, a ML that is restricted to those in the same boat should help. But it still seems not to work... perhaps we need to make it crystal clear that there are no such thing as a dumb question, and that we all were born ignorant.
5. We also need to make it crystal clear that when we give an opinion, this opinion is (more often than not) correct. As an example, some old mentees I had wanted to start by working on complex packages -- Evolution, the kernel, etc --, of which they had no experience. Although I tried to be very clear that these were potentially complex issues, and more experience would be needed, they usually would not listen... and I had, then, to correct mistakes, and smooth feathers; perhaps this should be more clear, this message "start with something you use and understand (as long as it is not Firefox or Evolution, or X)".
6. We should look again at the documentation pages we have for triaging; there certainly are thing we can Make Better(TM), since it is difficult for starting people, in general, to find and follow them.
7. Somehow, we need a more active mentorship. I am unsure on what we can do, though...
This is it, for now. I am pretty sure I will keep on thinking about it, and I may send additional emails later.
Cheers,
..C..
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL:
From fco.plj at gmail.com Wed Oct 5 23:00:45 2011
From: fco.plj at gmail.com (P.L. Francisco Javier)
Date: Wed, 5 Oct 2011 18:00:45 -0500
Subject: Feedback from current mentees
In-Reply-To: <4E8CAA5F.9070007@ubuntu.com>
References: <4E8CAA5F.9070007@ubuntu.com>
Message-ID:
Hi there, I'm one of those mentes who got confused and lost interest in the
mentorship program (although I'm still very interested in helping out with
Ubuntu and with triaging -I've organizated a UGJ locally). And even when I
know I've no right to demand anything, since every people who is here just
do it for fun or pleasure, I'd like to share the experience in hope to
improve it and to not terminate such a wonderful idea.
When I heard for the first time about the mentoring a thought it could
something much more 'easy to follow', I mean I expected private talks for
the group (somekind the UDW), todo lists, exercises and so on. I know this
may sounds lame because I basically expected that the mentors could be
'teachers' who could give us lots of tips and assign us at first, easy tasks
and from there, we could have started to move forward. Now I know they
expected the same from us, they wanted we *for ourselves* find our way to
start triaging and just ask for precise questions, but in that case, I would
just do it for IRC (it's faster, and people is always willing to help,
they've answered my questions every time).
So I thing the right thing to do (at least for a mentoring program), is to
have a specific shedule (where it could be showed how long could take
different stages (1 week for reading documentation, 1 week for working on
specific bugs -where everybody could work on the same type to get in touch
between us and talk about the same topics, after 2 weeks or something like
that we could start to triage X bugs for week, etc). I thing a mentoring
program can be rigid, because if we enroll ourselves to a mentoring program
is because we really have no idea where to start or still don't have
favorite packages, if we already knew what we want we will just jump into
the IRC channels to ask questions. It's just my idea.
I think we could had had a stadistic page who could had showed us how well
we were doing and assign points or something to keep us motivated, just
while we reached the scape velocity to get enough confidence to continue for
ourselves, in which case we would just start to hanging out in the IRC
channel, and the mentoring program could start another cicle.
On Wed, Oct 5, 2011 at 2:05 PM, C de-Avillez wrote:
> I sent an email to the mentorship-alpha team on Sep 8th:
>
> "We would like to have the feedback of the current mentees:
>
> 1. What are you doing now in regard to the mentorship programme?
>
> 2. Since you started, how many bugs have you worked on? Give an
> estimate -- 1, 10, 100, 1000, etc.
>
> 3. What did you expect from the mentorship programme? Please be as
> detailed as possible.
>
> 4. What did you *get* from the mentorship programme? Again, please
> be as detailed as poosible.
>
> I intend to query LP for the activities of each of your, as another
> datum we will use for analysis."
>
> This team, currently, has 17 active members: 10 mentors, and 7 mentees.
>
> I received 5 responses from mentees to the email; a summary follows:
>
> * of the five, 1 has worked on 100-200 bugs, one did not specify, and 3
> have worked on 10 or less bugs;
> * All comment (or agree with somebody else's comment) that the mentorship
> process is confused;
> * there is an expectation of a more active involvement from the mentors;
> * documentation should be pointed out (my words);
> * the sheer amount of bugs and packages involved makes startup more
> challenging;
> * there is need for a communications venue (mailing list, etc).
> * mentors should be more proactive (as opposed to basically reactive, as of
> now).
>
> MY VIEW
>
> I agree and disagree (as, I guess, could be expected) with these positions;
> right now, though, I do agree that the programme needs to be reviewed, and
> either adjusted or terminated. Here it is why, in no specific order:
>
> 1. there is a confusing message we pass over everywhere: "triaging is
> easy", "this is how you start, then you go to more difficult things, like
> development", etc.
>
> These are very wrong messages to pass.
>
> To begin with, triaging is NOT easy: one must understand the program being
> used, sieve the actual issue out of an usually confusing babble, decide if
> it is indeed a bug, verify documentation attached, etc, etc, etc. Secondly,
> there are thousands of packages; even if one restricts work to a few of
> them, it will still be a daunting task. Add to the above all the packaging
> details, interaction with multiple -- and some rather different --
> upstreams, and we have the perfect recipe for the confusion the mentees
> allude to.As the cream on the top, add the common difficulties of dealing
> with people that are aggressive, or lack communication skills, or that what
> they state is lost in translation.
>
> 2. There is another miscommunication going on: although we did state on the
> welcoming email, that the mentorship-alpha ML was one media to be used, we
> do not see much from mentees, neither on the ML, nor on IRC.
>
> 3. we have very few requirements on accepting a mentee; most importantly, I
> think we miss a critical requirement: the mentee *must* work on bugs; not
> doing so will be delaying access to other to-be mentees.
>
> 4. I still think the ML is a good idea; I think most of the folks beginning
> here are afraid (or, perhaps better, worried of being considered incapable)
> if they ask "dumb" questions. So, a ML that is restricted to those in the
> same boat should help. But it still seems not to work... perhaps we need to
> make it crystal clear that there are no such thing as a dumb question, and
> that we all were born ignorant.
>
> 5. We also need to make it crystal clear that when we give an opinion, this
> opinion is (more often than not) correct. As an example, some old mentees I
> had wanted to start by working on complex packages -- Evolution, the kernel,
> etc --, of which they had no experience. Although I tried to be very clear
> that these were potentially complex issues, and more experience would be
> needed, they usually would not listen... and I had, then, to correct
> mistakes, and smooth feathers; perhaps this should be more clear, this
> message "start with something you use and understand (as long as it is not
> Firefox or Evolution, or X)".
>
> 6. We should look again at the documentation pages we have for triaging;
> there certainly are thing we can Make Better(TM), since it is difficult for
> starting people, in general, to find and follow them.
>
> 7. Somehow, we need a more active mentorship. I am unsure on what we can
> do, though...
>
> This is it, for now. I am pretty sure I will keep on thinking about it, and
> I may send additional emails later.
>
> Cheers,
>
> ..C..
>
>
>
>
> --
> Ubuntu-bugsquad mailing list
> Ubuntu-bugsquad at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From gordon.dey at happydeys.ca Fri Oct 7 02:19:52 2011
From: gordon.dey at happydeys.ca (Gordon Dey)
Date: Thu, 06 Oct 2011 22:19:52 -0400
Subject: Ubuntu-bugsquad Digest, Vol 64, Issue 2
In-Reply-To:
References:
Message-ID: <4E8E61C8.9000401@happydeys.ca>
On 11-10-06 08:00 AM, ubuntu-bugsquad-request at lists.ubuntu.com wrote:
[edited]
> 3. What did you expect from the mentorship programme? Please be as
> detailed as possible.
A simple web search to "define mentor program", for me, turns up many
cite-able articles describing what to expect. Just two of the many
example articles: the Medical Services Corps' abbreviated guide, at
http://www.au.af.mil/au/awc/awcgate/mentor/mentor.htm , or "Making a
Mentoring Relationship Work: What is Required for Organizational
Success", by Lisa Kahle-Piasecki, at
http://www.na-businesspress.com/JABE/PiaseckiWeb.pdf.
The recurring theme, or key, seems to be in actively forming a
relationship. That means consistent, intentional communications about
every part: expectations, goals, coaching and review. I think we can
look for opportunities here.
From aha5262 at yahoo.com Fri Oct 7 15:29:53 2011
From: aha5262 at yahoo.com (a b)
Date: Fri, 7 Oct 2011 08:29:53 -0700 (PDT)
Subject: Bug in Ubntu 10.10 OpenOffice
Message-ID: <1318001393.49976.YahooMailClassic@web39323.mail.mud.yahoo.com>
No spell-check in OpenOffice.
When I boot from Live-CD I can perform spell-check in OpenOffice,
After Ubuntu is installed to my HD the spell-check dont work (No errors reported, only say Spell-Check finished)
My locale after install is English Philippines
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From mutant.john at hotmail.com Wed Oct 12 03:29:45 2011
From: mutant.john at hotmail.com (Chris Mazakas)
Date: Tue, 11 Oct 2011 20:29:45 -0700
Subject: With humility and grace...
Message-ID:
Hello Ubuntu Team,
Before I sent a rather angry email but you're right, foul language will get me nowhere. I'd like to begin by apologizing for my tone. I am trying not to balance getting decent grades, everyday shenanigans and a live-in girlfriend who is also just as stressed about school as I am. So when I wake up this morning and discover that my computer wants to play with me, I get a tad annoyed. And I was ironically enough guessing when I assumed you were all PhD's and professionals. I just assumed that amateurs wouldn't be making linux and if computer science/ engineering is anything like physics then you can't do much without a PhD or a lot of experience in the field.
So I have high expectations for you guys. I think you do good work. I was very impressed with 11.04 and I was very excited for 11.10. I posted about my issues to the Ubuntu forums and they were actually very helpful for getting my GUI back. Actually, it was them that told me what was wrong. Somehow while messing around with CompizConfig 'cause your alt-tab feature don't work for full-screen games such as Heroes of Newerth so I tried to force it to work 'cause I heard you could use that Compiz software or whatever it's called, I didn't have much time to experiment with it before my computer froze. But basically, it seems as though my GUI doesn't want to work for me.
My disks are healthy, all files are intact but it's just that the all GUI features are missing so there's no task bar and nothing in the upper right-hand corner. It's pretty cool though because I'm good enough with the command line now that I don't actually need a GUI but as we both know, GUI are better user-interfaces and that makes it a better operating system as it's more inclusive and I wanna use the best operating system which means I also get to use the best, most current GUI and that's what I'm missing.
Now, let me share with you something that's a tad odd. My GUI has only vanished in my main account. The solution on the forums was to create a new user account and then just log in with that. Funny thing is though, it totally worked. Here's a link to the thread I posted:
http://ubuntuforums.org/showthread.php?t=1858037
Let me know if the link doesn't work.
So if it works for one user account, why does it not work for the other? It must be somewhere in my user-defined settings then, right?
Either way, kudos though. I wasn't aware that a GUI could fail to load which means that the GUI is an upper layer while the command line stuff is below that, isn't it? I only recently learned that computers are built in layers or figurative conceptual layers which is pretty cool 'cause to be honest, I actually like not having a GUI. It makes me feel so much cooler.
And while I'm still here, how long do you think it'll take Wine to be advanced enough so that I can max Windows games on it? Or can you guys please just put into Ubuntu whatever it is that Windows requires to run games 'cause that'd be really nice. How else am I supposed to troll the newbs online while smugly mention my linux-using superiority?
-Christian Allen Mazakas
P.S.
If you look at thread you might notice that I finally spilled the beans.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From hggdh2 at ubuntu.com Wed Oct 12 03:45:11 2011
From: hggdh2 at ubuntu.com (C de-Avillez)
Date: Tue, 11 Oct 2011 22:45:11 -0500
Subject: email from mutant_john
Message-ID: <4E950D47.2090501@ubuntu.com>
All,
I have just approved for the ML an email from mutant_john, titled
"With humility and grace". I would like all triagers to read the
Forum's thread pointed to in it, and follow the adventure -- and
provide input to him on what might have gone wrong.
On a side project, it might be quite interesting to find what could
be done (if anything) to protect from a similar disaster.
Although this is not a bug (at least as of now), this does not
strictly follow a _triage_, per se. But it does show a real case
scenario of a user that suddenly finds himself with a non-working
(Ubuntu) system -- and how this can impact the user.
Please -- no comments like "you were running Beta, it is unstable".
He knows it. I know it. Everybody knows it. BTW, I am about 80%+
confident that he would have been hit by the same thing after release.
For the record, this email came after a rather strong one from him,
that I rejected, and asked for a bit of civility. I am immensely
glad he accepted, and pretty much as proud that I can accept in the
ML the new version.
Cheers,
..C..
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL:
From webmaster at ubuntu.com Thu Oct 13 16:33:28 2011
From: webmaster at ubuntu.com (Help Ubuntu)
Date: Thu, 13 Oct 2011 16:33:28 -0000
Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?=
=?utf-8?q?=22_by_kate=2Estewart?=
Message-ID: <20111013163328.11420.44267@jostaberry.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification.
The "ReportingBugs" page has been changed by kate.stewart:
http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=160&rev2=161
== 3. Make sure the bug hasn't already been reported ==
When filing a bug, please make sure it has not already been reported by searching through the [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]] and the release notes for your version of Ubuntu:
- * [[https://wiki.ubuntu.com/DapperReleaseNotes| Ubuntu 6.06 LTS (Dapper Drake)]]
* [[http://www.ubuntu.com/getubuntu/releasenotes/804|Ubuntu 8.04 LTS (Hardy Heron)]]
* [[http://www.ubuntu.com/getubuntu/releasenotes/1004|Ubuntu 10.04 LTS (Lucid Lynx)]]
* [[http://www.ubuntu.com/getubuntu/releasenotes/1010|Ubuntu 10.10 (Maverick Meerkat)]]
* [[http://www.ubuntu.com/getubuntu/releasenotes/1104|Ubuntu 11.04 (Natty Narwhal)]]
+ * [[http://www.ubuntu.com/getubuntu/releasenotes/1110|Ubuntu 11.10 (Oneiric Ocelot)]]
If you have further information about an already reported bug, add this information to the existing report, rather than opening a new one.
From pedro at ubuntu.com Wed Oct 19 11:53:45 2011
From: pedro at ubuntu.com (Pedro Villavicencio)
Date: Wed, 19 Oct 2011 08:53:45 -0300
Subject: Announcing the Next Ubuntu Bug Day! - Thursday 20 October 2011
Message-ID: <4E9EBA49.6050303@ubuntu.com>
Fellow Ubuntu Triagers!
This week's Bug Day target is *drum roll please* Bugs without a package!
* 50 New bugs need a hug
* 47 Incomplete bugs need a status check
* 50 Confirmed bugs need a review
Bookmark it, add it to your calendars, turn over those egg-timers!
* Thursday 20 October 2011
* https://wiki.ubuntu.com/UbuntuBugDay/20111020
Are you looking for a way to start giving some love back to your
adorable Ubuntu Project?
Did you ever wonder what Triage is? Want to learn about that?
This is a perfect time!, Everybody can help in a Bug Day!
open your IRC Client and go to #ubuntu-bugs (FreeNode)
the BugSquad will be happy to help you to start contributing!
Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
work your name could be listed at the top 5-A-Day Contributors in the
Ubuntu Hall of Fame page!
We are always looking for new tasks or ideas for the Bug Days, if you have one
add it to the Planning pagehttps://wiki.ubuntu.com/UbuntuBugDay/Planning
If you're new to all this, head to
http://wiki.ubuntu.com/Bugs
Have a nice day,
pedro.
From D-Partmann at gmx.net Tue Oct 18 19:41:00 2011
From: D-Partmann at gmx.net (D-Partmann at gmx.net)
Date: Tue, 18 Oct 2011 21:41:00 +0200
Subject: Downgrade problem from 10.10 to 10.04
Message-ID: <20111018194100.256730@gmx.net>
Hello
in attachment is the problem, how can i fix?
Thx...
Greetz
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: partman
Type: application/octet-stream
Size: 110580 bytes
Desc: not available
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syslog
Type: application/octet-stream
Size: 110807 bytes
Desc: not available
URL:
From noreply at ubuntu.com Wed Oct 19 11:52:19 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 19 Oct 2011 11:52:19 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?=
Message-ID: <20111019115219.3556.12435@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/Events" page has been changed by pvillavi:
http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=258&rev2=259
|| '''Name''' || '''Tag used''' ||
## StartHugDayParsing
+ || [[UbuntuBugDay/20111020| Bugs without a package]] || hugday-20111020 ||
|| [[UbuntuBugDay/20110908| Bugs without a package]] || hugday-20110908 ||
|| [[UbuntuBugDay/20110728| Banshee]] || hugday-20110728 ||
|| [[UbuntuBugDay/20110721| Banshee]] || hugday-20110721 ||
From cjk at teamcharliesangels.com Wed Oct 19 18:16:34 2011
From: cjk at teamcharliesangels.com (Charlie Kravetz)
Date: Wed, 19 Oct 2011 12:16:34 -0600
Subject: Downgrade problem from 10.10 to 10.04
In-Reply-To: <20111018194100.256730@gmx.net>
References: <20111018194100.256730@gmx.net>
Message-ID: <20111019121634.11e4d93e@teamcharliesangels.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 18 Oct 2011 21:41:00 +0200
D-Partmann at gmx.net wrote:
> Hello
>
> in attachment is the problem, how can i fix?
>
> Thx...
>
> Greetz
This was an unsupported downgrade. The best way to fix this would be to
reinstall Ubuntu 10.04, if that is the desired release.
- --
Charlie Kravetz
Linux Registered User Number 425914 [http://counter.li.org/]
Never let anyone steal your DREAM. [http://keepingdreams.com]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJOnxQDAAoJEFNEIRz9dxbAP1cH/iqrcK6iFP0Wbv4/5vTmjiEw
gPXna+PI0IrOjXPOU2zn0GZpGjUY5FsoI67ZaCiQatzgl9wf2JIcpoWfB2m0e4Zv
MoXuHSL8UpoyRrKOXt//unpwe4zb5iHu/VAn8vaNnTJPdnTw4E9cMHe4BxSwleXX
u3iglDQ6lo388FQtOJqCJnGAQHrxw2Mi9MBhYP61OqVwtVBV+OiPw89q8xcaa8GO
KKVEJ8KdqtH7GAWGGhRyzknSkFi+0+Sh3MWjbV9xJhXZX/z9ZK7uWlxMURYtM1/S
MLe+/Z8Ub2hKSWm+xUAtEdvddJIqlvMJQb/+FaJ8g25UQXM31oLHl22C+F+Vkvk=
=cryK
-----END PGP SIGNATURE-----
From noreply at ubuntu.com Wed Oct 19 17:36:25 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 19 Oct 2011 17:36:25 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_kirkland?=
Message-ID: <20111019173625.25288.2483@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/Importance" page has been changed by kirkland:
http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=29&rev2=30
Comment:
added a few more guidelines, per discussion on the ubuntu-platform mailing list
* '''Wishlist''': a request to add a new feature to one of the programs in Ubuntu.
* These aren't always bugs, but can be ideas for new features which do not yet exist.
* These can also be requests to have software packaged for Ubuntu.
- * If it is non-trivial to implement, it should rather be written as a feature specification, see FeatureSpecifications
+ * If it is non-trivial to implement, it should rather be written as a feature specification, see FeatureSpecifications.
+ * These can be bugs that affect an experimental extension or non-essential feature of a given package/project.
+ * Bugs that would only be fixed on a best-effort or outside-contribution basis might also be considered ''wishlist''.
* '''Low''': Bugs which affect functionality, but to a lesser extent than most bugs, examples are:
- * A bug that has an easy [[http://www.merriam-webster.com/dictionary/work-around|work-around]]
+ * Bugs that have easy [[http://www.merriam-webster.com/dictionary/work-around|work-arounds]]
- * Ones that affect unusual configurations or uncommon hardware
+ * Bugs that affect unusual end-user configurations or uncommon hardware
+ * Bugs that affect a non-essential aspect and limited scope of the application
- * A bug that has a moderate impact on a non-core application
+ * Bugs that have a moderate impact on a non-core application
- * A cosmetic/usability issue that does not limit the functionality of a non-core application
+ * Cosmetic/usability issues that does not limit the functionality of a non-core application
+ * Non-ideal default configurations
* '''Medium''': most bugs are of medium importance, examples are:
* A bug that has a moderate impact on a core application.
* A bug that has a severe impact on a non-core application.
@@ -31, +35 @@
* For example, if the system fails to boot, or X fails to start, on a certain make and model of computer
* A problem with an essential hardware component (disk controller, laptop built-in wireless, video card, keyboard, mouse)
* Has a moderate impact on a large portion of Ubuntu users (estimated)
+ * Prevents the application or any dependencies from functioning correctly at all
+ * Renders essential features or functionality of the application or dependencies broken or ineffective
- * A bug which impacts accessibility of a core application
+ * Impacts accessibility of a core application
* '''Critical''': A bug which has a severe impact on a large portion of Ubuntu users
+ * Causes data corruption
+ * Crashes the entire operating system
+ * Renders the system temporarily or permanently unusable
+ * Severely affects applications beyond the package responsible for the root cause
||{{attachment:IconHelp2.png}}If you're not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member, you'll have to ask someone who is to do it for you.Paste the bug number in {{{#ubuntu-bugs}}} channel at [[https://wiki.ubuntu.com/FreeNode|FreeNode]] and say you think the bug should be set to importance 'Wishlist / Low / Medium / High / Critical'. Someone will notice your comment and set it for you, although not necessarily immediately.||
----
From macoafi at gmail.com Thu Oct 20 15:17:49 2011
From: macoafi at gmail.com (Mackenzie Morgan)
Date: Thu, 20 Oct 2011 11:17:49 -0400
Subject: Announcing the Next Ubuntu Bug Day! - Thursday 20 October 2011
In-Reply-To: <4E9EBA49.6050303@ubuntu.com>
References: <4E9EBA49.6050303@ubuntu.com>
Message-ID:
On Wed, Oct 19, 2011 at 7:53 AM, Pedro Villavicencio wrote:
> Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
> work your name could be listed at the top 5-A-Day Contributors in the
> Ubuntu Hall of Fame page!
Given the Hall of Fame doesn't exist anymore, maybe it's time to
update the email template.
--
Mackenzie Morgan
From noreply at ubuntu.com Thu Oct 20 19:35:49 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Thu, 20 Oct 2011 19:35:49 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingGNOMEPowerManager=22_by?=
=?utf-8?q?_pvillavi?=
Message-ID: <20111020193549.28322.4647@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "DebuggingGNOMEPowerManager" page has been changed by pvillavi:
http://wiki.ubuntu.com/DebuggingGNOMEPowerManager?action=diff&rev1=33&rev2=34
<>
||<>||
- == Introduction ==
+
+ == Oneiric ==
+
+ If you're running Oneiric you'll notice that the Power Management was moved to GNOME Settings Daemon, thus all the bugs affecting GNOME Power Manager in Oneiric are about the statistics ui and not the daemon. If you're having issues with Power Management in Oneiric please use this method to report bugs to GNOME Settings Daemon:
+
+ Run g-s-d as:
+
+ {{{gnome-settings-daemon --no-daemon --debug &> g-s-d-debug.txt}}}
+
+ Then reproduce the bug and file it to gnome-settings-daemon.
+
+ == Natty Version or previous ==
Bugs relating to GNOME Power Manager (g-p-m) typically fall into 2 categories:
1. '''User interface bugs''': require a detailed description of the issue, steps to reproduce and screen captures where appropriate.
@@ -72, +83 @@
=== Querying Battery Info ===
- ==== Under HAL (9.04 and before) ====
-
- To get a list of all the batteries in the system you can use HAL:
-
- {{{
- $ hal-find-by-capability --capability "battery"
- }}}
-
- You can then discover the settings of each of the batteries including information like model numbers by doing this:
-
- {{{
- $ hal-find-by-capability --capability "battery" | xargs -n 1 hal-device
- }}}
-
- This provides all the possible information, but sometimes it is easier to look for specific information through the command line. For instance, if you wanted to look and see if the batteries are being seen as recharging:
-
- {{{
- $ hal-find-by-capability --capability "battery" | xargs -t -n 1 hal-get-property --key battery.rechargeable.is_charging --udi
- }}}
-
==== Under upower and DeviceKit-power (9.10+) ====
Battery information can be take directly from upower using the following command:
@@ -106, +97 @@
If g-p-m is having trouble shutting down, hibernating, or suspending, you can send commands directly to ensure that g-p-m is not getting in the way. (Copy+paste is recommended.)
'''Note:''' These should only be used for debugging. Do not use them during regular operation of your computer.
-
- ==== Under HAL ====
-
- || '''Reboot''' || {{{$ dbus-send --system --print-reply --dest="org.freedesktop.Hal" /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Reboot}}} ||
- || '''Shutdown''' || {{{$ dbus-send --system --print-reply --dest="org.freedesktop.Hal" /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Shutdown}}} ||
- || '''Hibernate''' || {{{$ dbus-send --system --print-reply --dest="org.freedesktop.Hal" /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate}}} ||
- || '''Suspend''' || {{{$ dbus-send --system --print-reply --dest="org.freedesktop.Hal" /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0}}} ||
==== Under DeviceKit-Power (Ubuntu 9.10) ====
From noreply at ubuntu.com Sat Oct 22 06:06:38 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Sat, 22 Oct 2011 06:06:38 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_phil?=
=?utf-8?q?ip=2Ev?=
Message-ID: <20111022060638.2967.91750@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "Bugs/FindRightPackage" page has been changed by philip.v:
http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=114&rev2=115
If you encounter a bug at the login screen, the package is the display manager:
- * In Ubuntu 11.10, it is 'LightDM'. In previous versions of Ubuntu and Edubuntu it was `gdm`.
+ * In Ubuntu 11.10, it is `LightDM`. In previous versions of Ubuntu and Edubuntu it was `gdm`.
* In Kubuntu it is `kdm`.
* In Lubuntu it is `lxdm`.
From watson99 at tpg.com.au Sat Oct 22 10:53:56 2011
From: watson99 at tpg.com.au (rnjwatson)
Date: Sat, 22 Oct 2011 20:53:56 +1000
Subject: bug in Libre Office Calc
Message-ID: <4EA2A0C4.5020006@tpg.com.au>
Hi Guys
I just upgraded to Kubuntu 11.10 and its beautiful. Thanks heaps.
Maybe you know already but there is just one small problem with Libre
Office Calc.
The slide bar along the bottom is partially covered by the spreadsheet
and doesn't work. This makes horizontal navigation difficult.
Not sure if its to do with my screen size which is the old 15.4". I am
using an Acer TravelMate 6410.
This problem was not evident in Kubuntu 11.04 or any earlier versions of
Open Office Calc.
best regards
Rus Watson
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ankarajasekar at gmail.com Sat Oct 22 06:08:32 2011
From: ankarajasekar at gmail.com (G.Rajasekaran)
Date: Sat, 22 Oct 2011 11:38:32 +0530
Subject: Programming error in aptdaemon
Message-ID:
SIR
I HAVE INSTALLED UBUNTU 11.10 IN THIS REGARD I CANT ABLE TO USE
UBUNTU SOFTWARE CENTRE
KINDLY SEE THE ATTACHEMENT I SEEK A SOLUTION FOR Programming error in
aptdaemon
--
*G.RAJASEKARAN*
*INDIA*
*+919940460078**
ankarajasekar at gmail.com
*skype- g.rajasekaran*
***
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot at 2011-10-20 21_34_25.png
Type: image/png
Size: 128534 bytes
Desc: not available
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot at 2011-10-21 08_13_38.png
Type: image/png
Size: 98733 bytes
Desc: not available
URL:
From noreply at ubuntu.com Mon Oct 24 15:10:49 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Mon, 24 Oct 2011 15:10:49 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=22_by_chrisccou?=
=?utf-8?q?lson?=
Message-ID: <20111024151049.3067.87146@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "MozillaTeam/Bugs" page has been changed by chrisccoulson:
http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=66&rev2=67
== Introduction ==
- You can help Ubuntu developers fix Firefox and make the software better by providing them with ''useful'' bug reports. Please realize that we need enough information to confirm it as a *bug* so the initial report must have enough for us to do that. Please see the following link on [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to report Bugs]]
+ You can help Ubuntu developers improve Firefox and Thunderbird by providing them with ''useful'' bug reports. This means that you should provide as much information as possible to describe the bug (please see [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to report Bugs]])
- You will find that you may need to use the Terminal for some of these commands. if you are not sure how to use a terminal, please see the [[https://help.ubuntu.com/6.10/ubuntu/desktopguide/C/terminals.html|Terminal Guide]] for a basic introduction.
+ You may find that you need to use the Terminal for some of these commands. If you are not sure how to use a terminal, please see the [[https://help.ubuntu.com/community/UsingTheTerminal|Terminal Guide]] for a basic introduction.
- Here are some instructions you should follow before filing a bug report on [[https://bugs.launchpad.net/distros/ubuntu/+source/firefox/+filebug|Firefox on Launchpad.net]]:
+ We get a lot of Firefox bug reports from Ubuntu users, and many of those don't contain enough useful information to sufficiently describe the problem or determine the cause of the problem. Please understand that we don't have the manpower available to spend time on every single bug report to continually ask reporters for information that ''could'' be provided up-front. To increase the chances that your bug report attracts the attention of a developer, you '''must''' follow these guidelines.
- == Try with a new profile ==
+ Here are some instructions you should follow before filing a bug report:
- Many bad Firefox behaviors are in fact caused by one of the many third-party 'themes', 'extensions' and 'plugins'. These will go away with a new profile - that is, when Firefox is restored to default settings and without any extensions and themes.
+ == Use Apport ==
- Problems with corrupt profiles are not handled in bug reports: if your problem went away with a new profile, please do not report the problem as a bug.
+ All Firefox and Thunderbird bugs '''must''' be submitted with Apport (unless there is another problem which prevents you from using Apport). For Firefox, you can do this by selecting the "Report a Problem" entry in the Help menu, or pressing Alt+F2 and running `ubuntu-bug firefox`.
- Start Firefox by entering the following command in a terminal: {{{firefox -ProfileManager}}}. You should now see the Profile Manager window.
+ For Thunderbird, please press Alt+F2 and run `ubuntu-bug thunderbird`.
- '''Important note''': From the Profile Manager you are also able to remove and rename profiles. Be very careful when deleting profiles, '''if you created the profile in a directory that already existed, the entire directory will be removed!'''
+ Using Apport attaches a lot of useful information automatically, and saves time by answering a lot of common questions that developers and bug triagers would normally need to ask. Please do not submit Firefox or Thunderbird bugs using the Launchpad interface. In most cases your bug report will not get any attention at all, and if it does receive any attention this will normally be to close it with a comment asking you to resubmit the bug using Apport. Please don't waste developers or bug triagers time by submitting bug reports using the Launchpad interface.
- Click on the 'Create Profile...' button to start the 'Create Profile Wizard'. Click 'Next' and enter a descriptive name for the new profile. Click Finish to have Firefox create the new profile. You should now be taken back to the Profile Manager and the newly created profile should be listed. Select it and click 'Start Firefox'. Try to reproduce the bug with this new profile.
+ == Try running in safe mode ==
- Note: you can go back to your own profile by starting Firefox using the command {{{firefox -ProfileManager}}} again, selecting your own profile, and clicking on 'Start Firefox'.
+ Some problems are caused by third-party themes, addons and plugins, or customization of hidden preferences in about:config. These customizations can be disabled temporarily by running Firefox or Thunderbird in safe mode.
- [[http://www.mozilla.org/support/firefox/profile#new|Link to Mozilla Documentation (Source)]]
+ To run Firefox in safe mode, ensure that you have closed all instances of Firefox, press Alt+F2 and run `firefox -safe-mode`.
+ To run Thunderbird in safe mode, ensure that you have closed all Thunderbird windows, press Alt+F2 and run `thunderbird -safe-mode`.
+
+ If the problem goes away in safe mode then it is caused by one of your addons or customizations. In this case, please do not report the bug to Launchpad. If you have time, you could try to isolate which addon or customization causes your problem, and contact the developer of the problematic addon.
+
+ [[http://support.mozilla.com/en-US/kb/Safe%20Mode|Link to Mozilla Documentation]]
== Be specific ==
- Try to make sure that the developer will be able to reproduce the bug you are seeing. Provide every detail you can regarding the bug, especially an explicit statement of exactly which sequence of user actions are needed to reproduce the bug.
+ Try to make sure that the developer will be able to reproduce the bug you are seeing. Provide every detail you can regarding the bug, especially an explicit statement of exactly which sequence of user actions are needed to reproduce the bug.
- == Use the terminal ==
+ == For problems with specific websites ==
- Start Firefox from a terminal by running {{{firefox}}}. Now you can either run (((firefox 2>&1 | tee /tmp/firefox-errors.txt))) than attach it to bug report you fill find it in /tmp/ dir in filesystem. or you can create a new text file and copy-paste the output in that file, and attach it to your bug report as an attachment. '''Note''' this only works on Firefox 2.0.x; the latest Firefox 3 betas do not leave errors in terminal.
+ If a website does not display correctly in Firefox, you '''must''' provide the following information where possible:
+ * A screenshot clearly showing the problem.
+ * Please remember that the problem may not always be obvious to somebody else who isn't familiar with how the website should normally appear. In this case, please describe exactly what is wrong.
+ * You probably want to remove personal information from any screenshots.
+ * The URL of the page causing the problem (preferably a URL which doesn't require signing in, although we appreciate this is not always possible)
- == Specific Websites ==
+ You might be surprised that we do get reports about websites not displaying correctly without any of this basic information provided.
- If you are having a problem with a website, please include its link, along with the exact problem you experienced on the site. We would truly appreciate if you can also take the time to isolate what on the page is triggering the bug, and include it as an HTML snippet in the bug report if possible. Something else that would be helpful is a screen shot of the problem you are seeing. You may also want to to try reproducing it with Epiphany-browser or a non-xulrunner browser like Konqueror or if you'd rather not install KDE libs or other parts on you Gnome you can try using Galeon.
+ If you have a problem with a website, please also do the following:
+ * Try using the website in another (non-Gecko) browser (eg, Chromium or Epiphany).
+ * Please state which other browsers you tested when submitting your report.
+ * If the website works correctly in other browsers, please provide a screenshot showing what the website should look like.
== Crashes ==
+ === Some things to consider ===
+
+ Please don't assume that just because you experience a crash, that everybody else will be able to easily reproduce it too. All crash reports must be submitted with a complete stacktrace, and a description of the steps required to trigger the crash (if it is reproducible). If the problem occurs on a specific website, please also include a URL.
+
+ As an example, these types of reports are not useful, and are unlikely to receive any developer attention at all:
+
+ Sometimes after I clicked on a link, firefox crashes and the "report this crash to the devellopers" window opens.
+
+ ...and...
+
+ Since my automatic upgrade to Mozilla Firefox browser 7.01. I'm not now able to play promotional videos on websites. When attempting to play a video, firefox browser crashes completely .And then you have to restart firefox.
+
+ (these are real examples)
+
=== Submitting Crashes to Mozilla ===
- The preferred way to submit crash data is to send it directly to Mozilla when the crash dialog appears. To find your submitted crash data, go to about:crashes in the browser. You can provide this crash id in the bug that you reported to Ubuntu.
+ The preferred way to submit crash data is to send it directly to Mozilla when the crash dialog appears. To find your submitted crash data, go to about:crashes in the browser. In most cases it isn't necessary to open a bug in Launchpad when you do this, especially if the crash report you submitted is already linked to a bug report in the upstream Bugzilla, or the crash is being experienced on non-Ubuntu systems (eg, other Linux distros, or even Windows or Mac OS). If the crash you submit appears to be unique to Ubuntu and it doesn't have a bug open in the upstream Bugzilla (or you just feel that Ubuntu developers need to be made aware of it), then feel free to open a bug in Launchpad.
+
+ If you do open a bug report in Launchpad, you '''must''' provide the crash ID of the crash report you submitted.
=== Run Firefox in a Debugger ===
- Install the debugging symbols for firefox (and some other dbg packages like in above point):
+ Install the necessary debugging symbols
+ For Firefox:
{{{
- apt-get install firefox-dbg
+ sudo apt-get install firefox-dbg
- apt-get install libgtk2.0-0-dbg \
- libnss3-0d-dbg \
- libnspr4-0d-dbg \
- libpango1.0-0-dbg \
- libc6-dbg
+ }}}
+ And Thunderbird:
+ {{{
+ sudo apt-get install thunderbird-dbg
+ }}}
+ These symbols will also be useful in most cases for both Firefox and Thunderbird. Please install them:
+ {{{
+ sudo apt-get install libgtk2.0-0-dbg libglib2.0-0-dbg libx11-6-dbg libpango1.0-0-dbg libc6-dbg
}}}
After closing all instances of Firefox, start Firefox from the terminal with the following command: {{{
@@ -74, +106 @@
}}}
2. Now ~/tmp/gdb-firefox.txt will contain the info we need to initially process your crash bug. So, please attach that file to your bug report.
- ==== Thunderbird-3.0 ====
+ Please use the same steps for Thunderbird, but replacing "firefox" with "thunderbird" instead.
- If you had a crash, provide exact steps to reproduce the crash. If you cannot reproduce the crash, provide details of exactly what you were doing prior to the crash. Then, follow these steps:
+ == Specific issues ==
+ === XML errors and broken UI after upgrade ===
- 1. Install debugging symbols by typing the following in a terminal (or install it with Adept or Synaptic): {{{
- # sudo apt-get install thunderbird-3.0-dbg \
- libgtk2.0-0-dbg \
- libnss3-1d-dbg \
- libnspr4-0d-dbg \
- libpango1.0-0-dbg \
- libcairo2-dbg \
- libc6-dbg
- }}}
- After closing all instances of Firefox, start Firefox from the terminal with the following command: {{{
- gdb /usr/lib/thunderbird-3*/thunderbird 2>&1 | tee /tmp/gdb-thunderbird.txt
- ... # someoutput
- (gdb) run
- ... # run and reproduce crash
- (gdb) bt full
- ... # full backtrace output
- (gdb) thread apply all backtrace full
- ... # all threads full backtrace output
- (gdb) quit
- }}}
-
- Now ~/tmp/gdb-thunderbird.txt will contain the info we need to initially process your crash bug. So, please attach that file to your bug report.
-
-
- = Specific issues =
-
- == XML errors and broken UI after upgrade ==
-
- After each release (eg Ubuntu Dapper 6.06, Edgy 6.10 and so on), some of our users report bugs that look a bit like this:
+ After each release, some of our users report bugs that look a bit like this:
{{{
XML Parsing Error: error in processing external entity reference
Location: jar:file:///usr/lib/firefox/chrome/toolkit.jar!/content/global/netError.xhtml
@@ -117, +122 @@
Other symptoms include missing UI elements after an upgrade or other kinds of XML errors in dialogue boxes or on firefox's stderr.
- This is one of the things that typically happens if you don't restart your Firefox after an upgrade. Please do not report this as a bug. (We think it's a bug that you have to restart it but sadly it's beyond our resources to fix it.)
+ This is one of the things that typically happens if you don't restart your Firefox after an upgrade. Please do not report this as a bug. There is already a bug report open about this.
= Closed Bug Reports =
If you find your bug report to be closed, it has been done by someone on our team for specific reasons. If you have a problem or wish to dispute the action, please use the bug report to ask for more information.
From bkerensa at gmail.com Mon Oct 24 20:18:47 2011
From: bkerensa at gmail.com (Benjamin Kerensa)
Date: Mon, 24 Oct 2011 13:18:47 -0700
Subject: Bug #878571 boinc-client bad signature for URL (Needs Attention)
Message-ID:
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/878571
--
Benjamin Kerensa
Tech Pundit & Social Media Guru
Phone: (503) 564-8608
*This message may contain information which is privileged or confidential.
If you are not the named addressee of this message please destroy it without
reading, using, copying or disclosing its contents to any other person.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From george.patterson at gmail.com Tue Oct 25 01:39:28 2011
From: george.patterson at gmail.com (George Patterson)
Date: Tue, 25 Oct 2011 12:39:28 +1100
Subject: Programming error in aptdaemon
In-Reply-To:
References:
Message-ID:
Hi,
This mailing list is not for reporting bugs, rather it's for discussing bugs
and the triaging of bugs.
However, while I haven't experienced this error, a quick google search has a
few solutions.
Regards
George
(Who is still wondering about the creative use of capitalisation)
On 22 October 2011 17:08, G.Rajasekaran wrote:
> SIR
> I HAVE INSTALLED UBUNTU 11.10 IN THIS REGARD I CANT ABLE TO USE
> UBUNTU SOFTWARE CENTRE
> KINDLY SEE THE ATTACHEMENT I SEEK A SOLUTION FOR Programming error in
> aptdaemon
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From pedro at ubuntu.com Wed Oct 26 12:40:48 2011
From: pedro at ubuntu.com (Pedro Villavicencio)
Date: Wed, 26 Oct 2011 09:40:48 -0300
Subject: Announcing the Next Ubuntu Bug Day! - Thursday 27 Oct 2011
Message-ID: <4EA7FFD0.2060302@ubuntu.com>
Fellow Ubuntu Triagers!
This week's Bug Day target is *drum roll please* Nautilus!
* 50 New bugs need a hug
* 50 Incomplete bugs need a status check
* 50 Confirmed bugs need a review
Bookmark it, add it to your calendars, turn over those egg-timers!
* Thursday 27 Oct 2011
* https://wiki.ubuntu.com/UbuntuBugDay/20111027
Are you looking for a way to start giving some love back to your
adorable Ubuntu Project?
Did you ever wonder what Triage is? Want to learn about that?
This is a perfect time!, Everybody can help in a Bug Day!
open your IRC Client and go to #ubuntu-bugs (FreeNode)
the BugSquad will be happy to help you to start contributing!
We are always looking for new tasks or ideas for the Bug Days, if you have one
add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning
If you're new to all this, head to
http://wiki.ubuntu.com/Bugs
Have a nice day,
pedro.
From cyan.spam at gmail.com Thu Oct 27 00:06:22 2011
From: cyan.spam at gmail.com (David Tombs)
Date: Wed, 26 Oct 2011 20:06:22 -0400
Subject: bug in Libre Office Calc
In-Reply-To: <4EA2A0C4.5020006@tpg.com.au>
References: <4EA2A0C4.5020006@tpg.com.au>
Message-ID: <4EA8A07E.5040309@gmail.com>
On 10/22/2011 06:53 AM, rnjwatson wrote:
> Hi Guys
>
> I just upgraded to Kubuntu 11.10 and its beautiful. Thanks heaps.
>
> Maybe you know already but there is just one small problem with Libre
> Office Calc.
>
> The slide bar along the bottom is partially covered by the spreadsheet
> and doesn't work. This makes horizontal navigation difficult.
>
> Not sure if its to do with my screen size which is the old 15.4". I am
> using an Acer TravelMate 6410.
>
> This problem was not evident in Kubuntu 11.04 or any earlier versions of
> Open Office Calc.
>
> best regards
>
> Rus Watson
>
Hi Rus,
Sorry, but this list is not for reporting bugs. Please see instructions
here for reporting bugs:
Thanks,
David
From walter.garcia at upf.edu Thu Oct 27 03:51:02 2011
From: walter.garcia at upf.edu (Walter Garcia-Fontes)
Date: Thu, 27 Oct 2011 05:51:02 +0200
Subject: Changing status to "New" after providing information
Message-ID: <20111027035102.GA30897@upf.edu>
I think it could be a good idea to ask bug reporters to change the
status to "new" again if they provide the information requested by a
triager. For instance something like:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER
Please change the status of the bug to "New" when you finish doing
this. When reporting bugs in the future please use apport by using
'ubuntu-bug' and the name of the package affected. You can learn more
about this functionality at https://wiki.ubuntu.com/ReportingBugs.
Same thing for other standard responses asking for more information.
--
Walter Garcia-Fontes
From timothy.mayoh at gmail.com Thu Oct 27 10:12:00 2011
From: timothy.mayoh at gmail.com (Timothy Mayoh)
Date: Thu, 27 Oct 2011 11:12:00 +0100
Subject: Changing status to "New" after providing information
In-Reply-To: <20111027035102.GA30897@upf.edu>
References: <20111027035102.GA30897@upf.edu>
Message-ID:
Brad Figg's script usually requests that the user changes the status to
"Confirmed" for kernel bugs; I believe that would be a better approach for
the majority of bugs than requesting it be changed to "New", as it shows the
bug likely already has the required logs, whereas many "New" bugs don't have
them.
For example:
>This bug is missing log files that will aid in diagnosing the problem. From
a terminal window please run:
>apport-collect BUGNUMBER
>and then change the status of the bug to 'Confirmed'.
>If, due to the nature of the issue you have encountered, you are unable to
run this command, please add a comment stating that fact and change the bug
status to 'Confirmed'.
>This change has been made by an automated script, maintained by the Ubuntu
Kernel Team.
On 27 October 2011 04:51, Walter Garcia-Fontes wrote:
> I think it could be a good idea to ask bug reporters to change the
> status to "new" again if they provide the information requested by a
> triager. For instance something like:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please execute the following command, as it will
> automatically gather debugging information, in a terminal:
> apport-collect BUGNUMBER
> Please change the status of the bug to "New" when you finish doing
> this. When reporting bugs in the future please use apport by using
> 'ubuntu-bug' and the name of the package affected. You can learn more
> about this functionality at https://wiki.ubuntu.com/ReportingBugs.
>
> Same thing for other standard responses asking for more information.
>
> --
> Walter Garcia-Fontes
>
>
>
> --
> Ubuntu-bugsquad mailing list
> Ubuntu-bugsquad at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From noreply at ubuntu.com Wed Oct 26 18:26:02 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 26 Oct 2011 18:26:02 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=22_by_chrisccou?=
=?utf-8?q?lson?=
Message-ID: <20111026182602.26404.26196@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "MozillaTeam/Bugs" page has been changed by chrisccoulson:
http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=69&rev2=70
In the future, we hope to automate this step.
- Note that debugging memory leaks in Firefox is quite involved. If you're feeling adventurous, please take a look at [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]]
+ Note that debugging memory leaks in Firefox is quite involved. If you're feeling adventurous, please take a look at [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]] and [[https://developer.mozilla.org/en/Debugging_Mozilla_with_Valgrind|Debugging Mozilla with Valgrind]]
== Specific issues ==
From noreply at ubuntu.com Wed Oct 26 17:56:37 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 26 Oct 2011 17:56:37 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=22_by_chrisccou?=
=?utf-8?q?lson?=
Message-ID: <20111026175637.22108.76638@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "MozillaTeam/Bugs" page has been changed by chrisccoulson:
http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=67&rev2=68
Please use the same steps for Thunderbird, but replacing "firefox" with "thunderbird" instead.
+ == Problems launching external applications ==
+
+ Ubuntu ships an Apparmor profile with Firefox, but this is disabled by default. If you have problems opening files in external applications from Firefox, or problems with extensions which need to start external helpers, then please make sure that the Apparmor profile is disabled or in complain mode before reporting a bug.
+
+ To make sure that the profile is not in enforce mode, run `sudo aa-status`. You will see output which looks a bit like this:
+ {{{
+ apparmor module is loaded.
+ 18 profiles are loaded.
+ 18 profiles are in enforce mode.
+ /sbin/dhclient
+ /usr/bin/evince
+ /usr/bin/evince-previewer
+ /usr/bin/evince-thumbnailer
+ /usr/lib/NetworkManager/nm-dhcp-client.action
+ /usr/lib/connman/scripts/dhclient-script
+ /usr/lib/cups/backend/cups-pdf
+ /usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}
+ /usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}//browser_java
+ /usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}//browser_openjdk
+ /usr/lib/lightdm/lightdm-guest-session-wrapper
+ /usr/lib/telepathy/mission-control-5
+ /usr/lib/telepathy/telepathy-*
+ /usr/sbin/cupsd
+ /usr/sbin/dhcpd3
+ /usr/sbin/mysqld-akonadi
+ /usr/sbin/tcpdump
+ /usr/share/gdm/guest-session/Xsession
+ 0 profiles are in complain mode.
+ 6 processes have profiles defined.
+ 6 processes are in enforce mode.
+ /sbin/dhclient (7094)
+ /usr/lib/telepathy/mission-control-5 (2397)
+ /usr/lib/telepathy/telepathy-* (4975)
+ /usr/lib/telepathy/telepathy-* (7101)
+ /usr/lib/telepathy/telepathy-* (7102)
+ /usr/sbin/cupsd (1210)
+ 0 processes are in complain mode.
+ 0 processes are unconfined but have a profile defined.
+ }}}
+
+ If there are entries starting with "/usr/lib/firefox" in the section "profiles are in enforce mode", then the Firefox profile has been enabled and set to enforce mode. In this case, please set it to complain mode and try again. To do this, please run `sudo aa-complain /usr/bin/firefox`. (Note, you will need to install apparmor-utils to do this)
+
+ If this works and the particular executable is from a software package in the Ubuntu archive, then we may consider adding an exception to the Apparmor profile. In this case, please report a bug using Apport. If the executable is from 3rd party software outside of the Ubuntu archive, then you will need to either keep the Apparmor profile disabled, or add an exception locally in /etc/apparmor.d/local/usr.bin.firefox.
+
+ See [[https://help.ubuntu.com/community/AppArmor|AppArmor]]
== Specific issues ==
=== XML errors and broken UI after upgrade ===
From noreply at ubuntu.com Wed Oct 26 18:18:34 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Wed, 26 Oct 2011 18:18:34 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=22_by_chrisccou?=
=?utf-8?q?lson?=
Message-ID: <20111026181834.26392.70667@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "MozillaTeam/Bugs" page has been changed by chrisccoulson:
http://wiki.ubuntu.com/MozillaTeam/Bugs?action=diff&rev1=68&rev2=69
If this works and the particular executable is from a software package in the Ubuntu archive, then we may consider adding an exception to the Apparmor profile. In this case, please report a bug using Apport. If the executable is from 3rd party software outside of the Ubuntu archive, then you will need to either keep the Apparmor profile disabled, or add an exception locally in /etc/apparmor.d/local/usr.bin.firefox.
See [[https://help.ubuntu.com/community/AppArmor|AppArmor]]
+
+ == Check the Error Console ==
+
+ Some bugs may result in unhandled JS exceptions or other error messages being logged to the error console, and these may provide a strong clue as to the cause of a bug. To view these, open the error console from "Tools -> Web Developer -> Error Console", and select "Errors".
+
+ Note, you many need to enable the menuitem to access the error console. To do this, open "about:config", and set "devtools.errorconsole.enabled" to "true"
+
+ == For problems with memory usage ==
+
+ If you are reporting a bug about excessive memory usage, please copy and paste the contents of "about:memory" in to your bug report, once you have reported this with Apport.
+
+ In the future, we hope to automate this step.
+
+ Note that debugging memory leaks in Firefox is quite involved. If you're feeling adventurous, please take a look at [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]]
+
== Specific issues ==
=== XML errors and broken UI after upgrade ===
From brian at ubuntu.com Thu Oct 27 17:05:47 2011
From: brian at ubuntu.com (Brian Murray)
Date: Thu, 27 Oct 2011 10:05:47 -0700
Subject: Changing status to "New" after providing information
In-Reply-To: <20111027035102.GA30897@upf.edu>
References: <20111027035102.GA30897@upf.edu>
Message-ID: <20111027170547.GP3395@murraytwins.com>
On Thu, Oct 27, 2011 at 05:51:02AM +0200, Walter Garcia-Fontes wrote:
> I think it could be a good idea to ask bug reporters to change the
> status to "new" again if they provide the information requested by a
> triager. For instance something like:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please execute the following command, as it will
> automatically gather debugging information, in a terminal:
> apport-collect BUGNUMBER
> Please change the status of the bug to "New" when you finish doing
> this. When reporting bugs in the future please use apport by using
> 'ubuntu-bug' and the name of the package affected. You can learn more
> about this functionality at https://wiki.ubuntu.com/ReportingBugs.
>
> Same thing for other standard responses asking for more information.
I'm not certain what you are trying to accomplish here and would like to
know why you think this is a good idea.
Regardless, I don't like this particular idea for the following reason.
A bug task can actually be Incomplete with response or Incomplete
without a response - the difference being whether or not the bug has had
a comment since being set to Incomplete. It is possible to search using
these two different types of Incomplete and so if I were to be looking
at bugs about a package I would first look at those that are "Incomplete
with response" before looking at "New" ones My thought being that if
someone took the time to reply (the bug had a response) they are willing
to work on debugging the issue - with a random New bug we don't know if
that is the case.
--
Brian Murray
Ubuntu Bug Master
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL:
From brian at ubuntu.com Thu Oct 27 17:14:59 2011
From: brian at ubuntu.com (Brian Murray)
Date: Thu, 27 Oct 2011 10:14:59 -0700
Subject: Changing status to "New" after providing information
In-Reply-To:
References: <20111027035102.GA30897@upf.edu>
Message-ID: <20111027171459.GQ3395@murraytwins.com>
On Thu, Oct 27, 2011 at 11:12:00AM +0100, Timothy Mayoh wrote:
> Brad Figg's script usually requests that the user changes the status to
> "Confirmed" for kernel bugs; I believe that would be a better approach for
> the majority of bugs than requesting it be changed to "New", as it shows the
> bug likely already has the required logs, whereas many "New" bugs don't have
> them.
I believe that leaving the status of the bug task alone, which makes it
"Incomplete w/ response", is the right thing to do. The current
definition of Confirmed is that has been experienced by another person
is quite useful and should not be changed.
> For example:
>
> >This bug is missing log files that will aid in diagnosing the problem. From
> a terminal window please run:
>
> >apport-collect BUGNUMBER
By the way the apport-collect process actually adds a tag,
apport-collected, to the bug report. This is something that you could
search for if you wanted.
Finally, by requiring bug reporters to make a change to a bug task's
status we are introducing a chance for something to go wrong.
--
Brian Murray
Ubuntu Bug Master
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL:
From walter.garcia at upf.edu Fri Oct 28 04:18:35 2011
From: walter.garcia at upf.edu (Walter Garcia-Fontes)
Date: Fri, 28 Oct 2011 06:18:35 +0200
Subject: Changing status to "New" after providing information
In-Reply-To: <20111027171459.GQ3395@murraytwins.com>
References: <20111027035102.GA30897@upf.edu>
<20111027171459.GQ3395@murraytwins.com>
Message-ID: <20111028041835.GE29297@upf.edu>
* Brian Murray [27/10/11 19:08]:
> Finally, by requiring bug reporters to make a change to a bug task's
> status we are introducing a chance for something to go wrong.
But shouldn't there be some reaction to the user answering to the
first request of information by the bug triager? If we leave the bug
as "Incomplete" it seems we didn't react to his/her response.
I was suggesting to instruct the OP to change the bug to "New" after
responding because I thought this is the right thing to do after the
OP has responded. What is the right thing to do? Leave the bug as
"Incomplete" if it cannot be "Confirmed"?
--
Walter Garcia-Fontes
From cjk at teamcharliesangels.com Fri Oct 28 15:25:29 2011
From: cjk at teamcharliesangels.com (Charlie Kravetz)
Date: Fri, 28 Oct 2011 09:25:29 -0600
Subject: Changing status to "New" after providing information
In-Reply-To: <20111028041835.GE29297@upf.edu>
References: <20111027035102.GA30897@upf.edu>
<20111027171459.GQ3395@murraytwins.com>
<20111028041835.GE29297@upf.edu>
Message-ID: <20111028092529.7b027003@teamcharliesangels.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 28 Oct 2011 06:18:35 +0200
Walter Garcia-Fontes wrote:
> * Brian Murray [27/10/11 19:08]:
> > Finally, by requiring bug reporters to make a change to a bug task's
> > status we are introducing a chance for something to go wrong.
>
> But shouldn't there be some reaction to the user answering to the
> first request of information by the bug triager? If we leave the bug
> as "Incomplete" it seems we didn't react to his/her response.
>
> I was suggesting to instruct the OP to change the bug to "New" after
> responding because I thought this is the right thing to do after the
> OP has responded. What is the right thing to do? Leave the bug as
> "Incomplete" if it cannot be "Confirmed"?
>
Seems to me if the triager is following the guidelines, they subscribed
to the bug report when marking it incomplete. If the reporter added
information, the triager then got an email notifying them that the bug
report changed. Why wouldn't they then go look at the bug report, and
verify if all information has been added, so the bug report can be
moved to triaged?
- --
Charlie Kravetz
Linux Registered User Number 425914 [http://counter.li.org/]
Never let anyone steal your DREAM. [http://keepingdreams.com]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJOqslpAAoJEFNEIRz9dxbAuMoIAIBBVY0Ic7RrO3GA0QOLswoq
U2qNw7MXUa3EIyxbG82Y11iMtik2hbHmXBlx485wwYHlZC/dK66Ctalyho/KvwCE
mnrqiQNgyYLc/nyLyp3O90JPC9keLxPxo+P7pSuvC/84FWDqIlP0MI1OsPTQCwZz
ju3pBKZNh6saaOnHcJQl7v15Yp+59hWNPgQpZRS6UZO0ooYNGus7QnxcoUGmEsO2
DU9Hx2yW7F/4DAqQmSeQqoKz+YlzaR1WCvk4NpLSqrd3dOKfQ9D+0dZCaqK3iAQF
e78NB/sL1Vcr7w4FIN/LFrwV/jgoE2bBBjarkl8k0zVsJqg5dSCDNz66SDLYsoo=
=J5qc
-----END PGP SIGNATURE-----
From snskeeter0 at gmail.com Fri Oct 28 15:48:42 2011
From: snskeeter0 at gmail.com (steve nordstrom)
Date: Fri, 28 Oct 2011 10:48:42 -0500
Subject: log on problem
Message-ID: <4EAACEDA.70507@gmail.com>
after new upgrade install to ubuntu 11.10 my logon password changed. I
am unable to log on other than through guest.
From walter.garcia at upf.edu Fri Oct 28 15:49:26 2011
From: walter.garcia at upf.edu (Walter Garcia-Fontes)
Date: Fri, 28 Oct 2011 17:49:26 +0200
Subject: Changing status to "New" after providing information
In-Reply-To: <20111028092529.7b027003@teamcharliesangels.com>
References: <20111027035102.GA30897@upf.edu>
<20111027171459.GQ3395@murraytwins.com>
<20111028041835.GE29297@upf.edu>
<20111028092529.7b027003@teamcharliesangels.com>
Message-ID: <20111028154926.GB26947@upf.edu>
* Charlie Kravetz [28/10/11 17:28]:
> On Fri, 28 Oct 2011 06:18:35 +0200
> Walter Garcia-Fontes wrote:
>
> > * Brian Murray [27/10/11 19:08]:
> > > Finally, by requiring bug reporters to make a change to a bug task's
> > > status we are introducing a chance for something to go wrong.
> >
> > But shouldn't there be some reaction to the user answering to the
> > first request of information by the bug triager? If we leave the bug
> > as "Incomplete" it seems we didn't react to his/her response.
> >
> > I was suggesting to instruct the OP to change the bug to "New" after
> > responding because I thought this is the right thing to do after the
> > OP has responded. What is the right thing to do? Leave the bug as
> > "Incomplete" if it cannot be "Confirmed"?
> >
>
> Seems to me if the triager is following the guidelines, they subscribed
> to the bug report when marking it incomplete. If the reporter added
> information, the triager then got an email notifying them that the bug
> report changed. Why wouldn't they then go look at the bug report, and
> verify if all information has been added, so the bug report can be
> moved to triaged?
The simple reason is that only people in the Ubuntu Bug Control can
mark a bug as "Triaged". Starting triagers as myself cannot do it, but
I feel bad asking a reporter for information, marking the bug as
Incomplete and not giving him/her any feedback when the information is
provided, that is leaving the bug with the "Incomplete" tag despite
the reporter having responded.
I thought the standard procedure for us was to mark the bug again as
"New" if it could not be marked already as "Confirmed", so what I do
is subscribing to the bug and marking it as "New" when I see that the
reporter responded. That's why I was asking if it was good idea to
tell the reporter to do this himself/herself, to save us having to go
back to the bug just to change the tag.
But if it is not recommended to remark the bug as "New" when a
response has been provided and the bug cannot be marked as
"Confirmed", what is the right thing to do?
--
Walter Garcia-Fontes
From lcpak at epoczta.pl Fri Oct 28 15:57:27 2011
From: lcpak at epoczta.pl (=?UTF-8?B?xYF1a2FzeiBPbHN6ZXdza2k=?=)
Date: Fri, 28 Oct 2011 17:57:27 +0200
Subject: log on problem
In-Reply-To: <4EAACEDA.70507@gmail.com>
References: <4EAACEDA.70507@gmail.com>
Message-ID: <4EAAD0E7.8000408@epoczta.pl>
I think that you suffer from a bug described here:
https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/850925
If the instructions provided there help you then please mark this bug as
affecting you as well.
W dniu 28.10.2011 17:48, steve nordstrom pisze:
> after new upgrade install to ubuntu 11.10 my logon password changed. I
> am unable to log on other than through guest.
>
From RedSingularity at gmx.com Fri Oct 28 16:07:06 2011
From: RedSingularity at gmx.com (RedSingularity)
Date: Fri, 28 Oct 2011 12:07:06 -0400
Subject: Changing status to "New" after providing information
In-Reply-To: <20111028154926.GB26947@upf.edu>
References: <20111027035102.GA30897@upf.edu> <20111027171459.GQ3395@murraytwins.com> <20111028041835.GE29297@upf.edu> <20111028092529.7b027003@teamcharliesangels.com>
<20111028154926.GB26947@upf.edu>
Message-ID: <4EAAD32A.1080802@gmx.com>
On 10/28/2011 11:49 AM, Walter Garcia-Fontes wrote:
> * Charlie Kravetz [28/10/11 17:28]:
>> On Fri, 28 Oct 2011 06:18:35 +0200
>> Walter Garcia-Fontes wrote:
>>
>>> * Brian Murray [27/10/11 19:08]:
>>>> Finally, by requiring bug reporters to make a change to a bug task's
>>>> status we are introducing a chance for something to go wrong.
>>> But shouldn't there be some reaction to the user answering to the
>>> first request of information by the bug triager? If we leave the bug
>>> as "Incomplete" it seems we didn't react to his/her response.
>>>
>>> I was suggesting to instruct the OP to change the bug to "New" after
>>> responding because I thought this is the right thing to do after the
>>> OP has responded. What is the right thing to do? Leave the bug as
>>> "Incomplete" if it cannot be "Confirmed"?
>>>
>> Seems to me if the triager is following the guidelines, they subscribed
>> to the bug report when marking it incomplete. If the reporter added
>> information, the triager then got an email notifying them that the bug
>> report changed. Why wouldn't they then go look at the bug report, and
>> verify if all information has been added, so the bug report can be
>> moved to triaged?
> The simple reason is that only people in the Ubuntu Bug Control can
> mark a bug as "Triaged". Starting triagers as myself cannot do it, but
> I feel bad asking a reporter for information, marking the bug as
> Incomplete and not giving him/her any feedback when the information is
> provided, that is leaving the bug with the "Incomplete" tag despite
> the reporter having responded.
>
> I thought the standard procedure for us was to mark the bug again as
> "New" if it could not be marked already as "Confirmed", so what I do
> is subscribing to the bug and marking it as "New" when I see that the
> reporter responded. That's why I was asking if it was good idea to
> tell the reporter to do this himself/herself, to save us having to go
> back to the bug just to change the tag.
>
> But if it is not recommended to remark the bug as "New" when a
> response has been provided and the bug cannot be marked as
> "Confirmed", what is the right thing to do?
>
I would say you follow the bug with the "Incomplete" status until you,
as the triager, have felt that the user has provided enough info. Then
once that is the case, and/or you have seen similar results on a
reproduction test, you mark it "Confirmed". From there, you can give
that bug to a Bug Control member who will mark it "Triaged" if it is
truly ready for that mark. (Be sure to check for duplicates before
handing it off to be marked Triaged)
If you are asking a user for information that may help another triager
'diagnose' the bug BUT don't intend to follow that bug yourself, then it
should be left as "New" so that another triager can see the "New" status
and begin work on it.
Personally, when I mark a bug incomplete, I like to follow it until the
end when I can mark it "Triaged" or "Invalid".
-Tim
(RedSingularity)
From noreply at ubuntu.com Thu Oct 27 20:05:06 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Thu, 27 Oct 2011 20:05:06 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_mte?=
=?utf-8?q?rry?=
Message-ID: <20111027200506.24125.67146@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "DebuggingSoundProblems" page has been changed by mterry:
http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=65&rev2=66
Comment:
Karmic is EOL, don't link to sound fixes for it
{{{
ubuntu-bug audio
}}}
-
- Running Ubuntu Karmic Koala (9.10)? [[https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats|First have a look at this list]] of the most common problems with sound in this release.
-
== Preliminary checks ==
From noreply at ubuntu.com Thu Oct 27 20:10:48 2011
From: noreply at ubuntu.com (Ubuntu Wiki)
Date: Thu, 27 Oct 2011 20:10:48 -0000
Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_mte?=
=?utf-8?q?rry?=
Message-ID: <20111027201048.24143.35417@mangaba.canonical.com>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.
The "DebuggingSoundProblems" page has been changed by mterry:
http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=66&rev2=67
Comment:
Remove some more references to obsolete releases
= Basic troubleshooting =
- Running Lucid (10.04) or later? There is a troubleshooter that checks for some of the most common problems. Open a Terminal (Program -> Accessories -> Terminal), then enter this command:
+ There is a troubleshooter that checks for some of the most common problems. Press Alt+F2, then enter this command:
{{{
ubuntu-bug audio
}}}
== Preliminary checks ==
- 1. Is your sound system plugged in and switched on. I spent an hour trying to diagnose a sound issue when the problem was that I had switched off the speakers to answer a phone call and forgot that I had done so. :-(
+ 1. Is your sound system plugged in and switched on? I spent an hour trying to diagnose a sound issue when the problem was that I had switched off the speakers to answer a phone call and forgot that I had done so. :-(
- 2. Is your speaker or microphone muted? Check here (9.10 and later) :
+ 2. Is your speaker or microphone muted? Check here:
* [[Audio/CheckForMutedSpeakerVolume|Check for muted speaker]]
* [[Audio/CheckForMutedMicrophone|Check for muted microphone]]
== Checking volume levels ==
- Before messing around with uninstalling and installing various sound programs to fix a problem, check your volume levels. It is often the case that a muted channel is the problem, even though the description may not sound immediately relevant. In this regard, muted Surround or Center channels are common culprits. So unmute and raise the volume of one channel at a time and check whether sound is then produced by a running sound application e.g. Rhythmbox.
+ Before messing around with uninstalling and installing various sound programs to fix a problem, check your volume levels. It is often the case that a muted channel is the problem, even though the description may not sound immediately relevant. In this regard, muted Surround or Center channels are common culprits. So unmute and raise the volume of one channel at a time and check whether sound is then produced by a running sound application e.g. Banshee.
You can access the volume levels for the various channels from the command line or the GUI.
@@ -31, +31 @@
1. From GUI: This can be done by running something like ''gnome-alsamixer'' from a terminal window or navigating to your your Volume Control. Then unmute as described above. Also check that your switches are set correctly - for instance that if you use the analog output the analog switch is set ON or that the digital or S/PDIF switch is set OFF. You can select which tracks/switches are visible in Volume Control (see above) under Edit->Preferences.
* Note: These controls have equivalent functionality to alsamixer but with a graphical interface. Checking or unchecking devices in the these accomplishes the exact same thing as unmuting or muting devices, respectively, in alsamixer.
- * Starting with Ubuntu 7.04, the sound volume control is also accessible from Menu->Sound&Video->Volume Control. It may be hidden in your menus but can be shown by going to System > Preferences > Main Menu and under Applications > Sound&Video ticking Volume Control.
+ * The sound volume control is also accessible from Menu->Sound&Video->Volume Control. It may be hidden in your menus but can be shown by going to System > Preferences > Main Menu and under Applications > Sound&Video ticking Volume Control.
== Checking sound device assignment ==
@@ -43, +43 @@
* {{{
options snd slots=,snd-usb-audio
}}}
- The index numbers (0, 1, ... 7) signify the priority of the device, with the highest priority device being 0, then 1, and so forth. In theory, applications should first attempt to use the highest priority device first, but if for some reason the application is unable to use the device, it will use the next highest priority device. For example, if you have a USB sound card that can get picked up with OSS, which browsers, flash, and skype may not output, if you set your USB card at first priority, it will play when using, say, Rhythmbox, but your other applications will play through your other soundcard. For more information see Documentation/sound/alsa/ALSA-Configuration.txt in the kernel source.
+ The index numbers (0, 1, ... 7) signify the priority of the device, with the highest priority device being 0, then 1, and so forth. In theory, applications should first attempt to use the highest priority device first, but if for some reason the application is unable to use the device, it will use the next highest priority device. For example, if you have a USB sound card that can get picked up with OSS, which browsers, flash, and skype may not output, if you set your USB card at first priority, it will play when using, say, Banshee, but your other applications will play through your other soundcard. For more information see Documentation/sound/alsa/ALSA-Configuration.txt in the kernel source.
== Checking permissions and resources ==
@@ -58, +58 @@
Please do not report problems on this page; use the normal support channels instead. See http://www.ubuntu.com/support
If you feel you have encountered a software bug, the way to report it varies between versions.
- For Ubuntu Lucid Lynx (10.04) and later, run the following terminal command:
+ Run the following terminal command:
{{{
ubuntu-bug audio
}}}
- For Ubuntu Karmic (9.10), run the following terminal command:
- {{{
- ubuntu-bug -p alsa-base
- }}}
-
This will submit a detailed bug report with information about your current system.
- For older versions, or if the above fails for some reason, you can file a bug report, then upload alsa-info information [[Audio/AlsaInfo|according to these instructions]].
+ If the above fails for some reason, you can file a bug report, then upload alsa-info information [[Audio/AlsaInfo|according to these instructions]].
== Triaging sound bugs ==