Tried the suggestion in comment #9 and that produced the error message
"Invalid client RPC password. Try reinstalling BOINC."
I already did a reinstall using aptitude.
I also found a version of the file at a higher level, but messing with
that one didn't help, either.
--
You received this bug
The minimal solution of comment #4 did not work for me. I also tried
manually changing the permissions of the file to make it "Read and
write", but I didn't look for the BOINC group, so I'm going to try that
next...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Not sure why it's marked incomplete at this late date, but if I remember
correctly the problem was fixed not long after I reported it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/492995
Title:
Okay, after the latest update (from the 0-13 kernel) it now seems to be
booting normally. I hope that means the problem has been corrected and
this bug can be closed. Perhaps some kind of regression bug?
If anyone over there wants me to collect any additional information
about what was going on,
I am unable to run that command under the afflicted kernel because the
machine cannot boot under that kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815258
Title:
4.18.0-14-generic
The robotic message tells me to change the status to confirmed after
adding the previous comment, but the instructions there say that the
confirmed status is supposed to be done by someone else.
By the way, my current theory (based on weak understanding) is that
there might be some logs of the
** Description changed:
After the update for the 4.18.0-14-generic kernel the machine freezes on
booting. Machine still books under the 0-13 kernel. Booting in Recovery
Mode seems go normally to the Recovery Menu. At that point it reports
- "Starting Avahi mDNS-SD Stack" and gets and OK.
Public bug reported:
After the update for the 4.18.0-14-generic kernel the machine freezes on
booting. Machine still books under the 0-13 kernel. Booting in Recovery
Mode seems go normally to the Recovery Menu. At that point it reports
"Starting Avahi mDNS-SD Stack" and gets and OK. That is
Correction: "when away" should be "went away".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532226
Title:
No menu bar in gtk apps on fresh boot
To manage notifications about this bug go to:
@Ian (ian-bradley)
You say it makes a lot of sense, but not to me, so I must have been unclear in
my description of what does not make sense.
The Title bar where the menus will appear is there and taking up screen
real estate whether or not you are hovering over it. The new feature (if
I
How do we know if this problem has gone away?
Anyway, I'm pretty sure that disabling the hover for menus was
sufficient to eliminate the problem on my machine. )However I can't
imagine why anyone would want such a feature in the first place. Just
because Microsoft uses a similar feature in
*** This bug is a duplicate of bug 1532226 ***
https://bugs.launchpad.net/bugs/1532226
At this time I'm inclined to regard this as a separate bug not directly
related to the gdk menu bar problem. They appeared at the same time, but
that was just because of the upgrade. Not sure how to prove
About 90% sure this is the same as a bug I tried to report earlier, but
is there any test to be sure? I have a couple of peculiar observations
that might help in the diagnosis and cure...
Suspending seemed to fix it, at least temporarily. Before that there was
nothing random about it. There were
*** This bug is a duplicate of bug 1532226 ***
https://bugs.launchpad.net/bugs/1532226
Is there any way to confirm that I am 90% sure that Bug #1532226 is the
proper one for what I reported? (Even better, is there some way I could
have been directed to that bug as I was describing my symptoms
If it is related to the Menu bar bug I reported earlier, then this one
should be folded into that one (Bug 1574160) and the Bug Heat of that
one should be increased. My initial research suggested that was the
primary problem, but I'm not certain that the apparent bug isn't a
design change with an
Public bug reported:
This behavior only began after installing 16.04 a few days ago. Watching
BOINC Manager start with four running tasks, the memory utilization
steadily creeps upward from about 30% and eventually it starts shutting
down tasks, but has to be tricked into resetting the memory
Public bug reported:
The Summary is just the most distinctive symptom now. There seem to be a
number of related pre-release reports, but none of them seemed the
correct link to what I'm seeing. Only Firefox seems to have access to
the Menu bar now. All other programs display only the program
Not sure if it's the same problem, but if so, BOINC is triggering it,
too. GPU is enabled, so that might be related to the video observation
above. Not sure how to include the diagnostic information if that will
help, but right now I'm going to reboot and confirm that the fresh boot
is normal.
Oh
god damn spammer. How is this sort of crap supposed to be reported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197537
Title:
[MASTER] Can't read PDF file with CJK (Chinese/Japanese/Korean) text
Similar problem in the Japanese version--but at this point I'm expecting
Ubuntu to become more useless with each so-called upgrade. I'm just
trying to do the upgrade, and the first question it asks is for a
keyboard, but it does NOT offer ANY option that is recognizably similar
to the keyboard
I think I'm seeing this problem in the upgrade causing it to ask me to
select a keyboard when there should be no change in the keyboard
configuration--but at this point I'm expecting Ubuntu to become more
useless and troublesome with each so-called upgrade. Look, I'm just
trying to do the upgrade,
I think this bug is affecting me because I cannot install ANY keyboard
for my ThinkPad--but at this point I'm expecting Ubuntu to become more
useless and troublesome with each so-called upgrade. Look, I'm just
trying to do the upgrade, and the first question it asks is for a
keyboard, but it does
I'll just note that I'm still seeing it, but quite rarely now. In
contrast, the new Firefox shutdown problem has become quite frequent...
--
Crash to white screen of death (possibly Firefox?)
https://bugs.launchpad.net/bugs/159594
You received this bug notification because you are a member of
Just stopped by to see if anyone else has reported it. Amusingly enough,
I asked the other local user of Ubuntu about it, and he said his Firefox
does it, too--but he's never bothered to report it. He just figured it
was because he has too many Firefox windows open, which got me to try
the
Sorry I've been kind of busy and haven't gotten back to you on this. I
really do appreciate your attempt to follow up on it, and I value your
technical acumen, but like many people, I have competing priorities.
I've already noted why Ubuntu has become a relatively low one for me.
More importantly,
WA70:~$ lspci -vvnn
00:00.0 Host bridge [0600]: ATI Technologies Inc RS480 Host Bridge [1002:5950]
(rev 01)
Subsystem: Sharp corporation Device [13bd:104c]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap-
The attempt to add the basic Report a Problem... information failed,
as did the attempt to use the apport-collect 612131. This was after the
first unprovoked shutdown of the evening, which was actually quite slow
--already over an hour.
--
Unprovoked shutdowns of Firefox
Working on a reliable Windows computer now, so I can comment in a bit
more detail. Sad to report it, but I used to think of Ubuntu as more
reliable than Windows.
Because this shutdown bug was so annoying and unpredictable and
undiagnosable, I finally decided to upgrade the machine in question
Thank you (Mr Gersten) for linking from the other bug. If I can at least
temporarily overcome my increasingly hopeless feelings towards Ubuntu, I
may also attempt the steps recommended by madbiologist (since the
backtrace approach failed (and going even farther by the way, the
backtrace had
Public bug reported:
Binary package hint: firefox-3.5
will it even save the bug report this time?
guess what. I don't care.
ProblemType: Bug
Architecture: i386
Date: Sun Aug 8 08:35:41 2010
DistroRelease: Ubuntu 9.10
Package: firefox 3.6.8+build1+nobinonly-0ubuntu0.9.10.1
ProcEnviron:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/53252772/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/53252773/XsessionErrors.txt
--
Unprovoked shutdowns of Firefox
https://bugs.launchpad.net/bugs/614861
You received this bug
No, I cannot do that because your (Micah Gersten's) instructions (in the
previous message and in the linked webpage) are incomplete or incorrect.
I have just wasted another half hour or so trying to figure out various
combinations of the most likely corrections.
I made that much effort in an
By the way, even if I had succeeded, I still do not have any reliable
mechanism with which to trigger the bug. It happens when it feels like
happening. The last time just happened to be when I was looking at the
email that told me you had posted your comment to Launchpad. Sometimes
it happens
Whoops. This is obviously not the bug I'm looking for, though it sounded
very similar...
--
firefox-3.0 shutdown automatically when i open web page
https://bugs.launchpad.net/bugs/316586
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: firefox-3.0
This is in Firefox 3.6.8, but may have begun with 3.6.7 under Ubuntu
9.04. (Later versions of Ubuntu have been tested on the machine, but
this seems to be the most stable. The main stability problem is probably
related to some kind of display
Thanks to whoever provided the useful reminder about the tab setting in
response to the previous spleen venting.
I don' t know if this is really the same bug I'm seeing--and I don't
care anymore. After several years of using Ubuntu, I am now convinced
that it is going down the toilet and cannot
Oh yeah. One more point of annoyance. A bug-reporting system that
strongly depends on a buggy piece of software is not worth much.
However, I've already suggested the obvious REAL improvement directed at
the root of increasing the regression testing.
--
[MASTER] various unrelated crashes for
I don't mind discussing thing, but it seems pretty pointless. Actually,
on the two machines that I normally run under Ubuntu, I also am forced
to use older versions of Ubuntu because the newer versions are NOT
reliable enough. I am running the newest version experimentally on three
machines--but I
I have (at least twice) already used the supposedly automatic system to
collect and submit the information that is supposed to diagnose these
new Firefox problems. In the past, before I lost hope for Ubuntu, I also
volunteered to undertake additional diagnostic measures or to run
additional tests
I was getting too afraid to continue pending the next crash, but so far
it's been stable... knock on wood
I really want viable alternatives to Windows. I believe that freedom is
a good thing and that freedom depends on meaningful choice. Linux could
be such a choice, but so far it has remained a
With regards to the earlier comment about Windows, I believe there was
only one time in my life when I freely purchased a copy of Windows,
though there were a couple of times when I chose to buy other Microsoft
products. Long time ago.
I'm still forced to use Microsoft products--because their
Public bug reported:
Binary package hint: firefox-3.0
Actually several of those existing bug reports are probably the same,
but at this point I don't care enough about Firefox to worry about it.
I'm only writing this because the new bugs are just SO fucked up and
they AGAIN clearly show the need
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52446667/Dependencies.txt
--
Lots of problems with new Firefox
https://bugs.launchpad.net/bugs/609593
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Upon reflection, I think that #3 should be the utter mangling of the
form and search history data. It USED to be a useful feature in
Firefox.
--
Lots of problems with new Firefox
https://bugs.launchpad.net/bugs/609593
You received this bug notification because you are a member of Ubuntu
Bugs,
Oh yes. Apologies for the profanity. I tried to keep it calm, but one
word slipped through. Not really a defense of my transgression, but if I
wasn't so annoyed, I wouldn't have wasted the time in the first place.
Overall, I'm just venting my frustration at the failure of Ubuntu, which
long ago
I couldn't remember this discussion after a couple of years, but I was
amused by the comment and depressed to see that after two (more) years
things have NOT turned around. I still want alternatives to Microsoft's
awful software, but the major change of the last few years is that
Microsoft has
Congratulations on figuring out the new hoops to jump through to report
a bug. I couldn't figure it out, but at this point I don't care enough
about Ubuntu to worry about it. I'm just stalling and waiting for a
better alternative, perhaps Chrome? (My employer favors RHEL, but I can
barely stand
I don't object to your closing it, but I feel obliged to let you know
you that I think this bug is still present in Koala. However, the
release before Koala seems to be good enough, and that's where I've been
staying with the machine for most of the time. I'm going to go ahead and
install the new
Should I do this from the J or K version? Or maybe wait for L? I have
both J and K installed here, but Koala had so many problems with the
sound card that I still regard it as experimental and I normally run
from J.
The problem has become quite infrequent under J, however, so I wasn't
too worried
I finally got this bug into a can yesterday. I thought it had gone away,
but it started showing up again, though very rarely. Then yesterday, I
found a way to reproduce it. At least it worked twice in a row. If
someone will tell me what to do, maybe it will be possible to diagnose
it now.
The
I wanted to check the status of this ancient bug, but on this particular
machine I only have a VMware Player with Ubuntu as a guest OS. It runs,
but I am unable to get the Japanese support to work properly for
Japanese input now that I have upgraded it to the newest version of
Ubuntu. I can
This bug is listed as a duplicate of a different bug report that more
accurately described the symptoms that I am seeing. In my machines. What
I see is total sound failure (apart from a few intermittent clicks at
boot time) on machines that worked fine with 9.04. That includes three
machines from
Whoops, I meant to say at least 3 machines, but I think I may have
tested it on as many as five machines that failed, and found only one
machine where the sound worked properly (from the live CD, as I recall).
--
pulseaudio crackle/distortion with cs46xx on latest update
I'm afraid to say anything, since I haven't seen the bug in a long time.
Let me knock on some wood before continuing...
However, from looking at this thread now, I'm pretty sure you were
talking to someone else, probably Bryce Harrington. Do you want me to
try to run the same information? I don't
Sorry I'm slow getting back to you on this. I sort of hoped it was just
the usual glitches (even though they're supposed to be ready to release
the software when they release it)... However, it appears the sound-
related problems are much more serious than I understood at the time,
and much more
I'm seeing related problems in two machines, but I can say that Firefox
is not involved in my case... The machines worked well until Koala
upgrades apparently destroyed the sound capabilities...
(Mostly commenting here so that (I think) I'll be subscribed for updated
information on this bug in
Different Shannon here... I think I'm confirming this bug for two
machines and hoping to see updates. However, so far I'm mostly just
overwhelmed by noise and a feeling of hopelessness. This seems to be a
pretty basic level of functionality.
About the only things I can see to add to the
I'm pretty sure I've been seeing the same problem for several weeks now,
but only on one machine. It's a Sharp running the Jackalope version of
Ubuntu, and is reported almost every boot, and sometimes twice, when it
apparently tries to upgrade the extension version. The error message
says to
Public bug reported:
Binary package hint: totem
My main audio use of Ubuntu was for streaming MP3 audio, and it's been
working fine (for perhaps a year or two on this machine) until the Koala
upgrade. It seems to be attempting to do something, but there's no sound
and I can't find any way to get
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35352536/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/35352537/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/35352538/ProcStatus.txt
--
Totem
I'm the original reporter, but I'm unsure how to check it. I can say
that it does sound plausible as the explanation for what I saw. If so,
then what I did with the Windows internal (chkdsk?) disk checking
utility (whatever it is in the tools from the disk properties?) was
actually resetting or
I've had trouble with that new bug reporting feature you mentioned, so I
have mostly been bypassing it. I should try to go back to it to see if
the bugs have been worked out of the bug reporting...
As regards this bug, I just installed Firefox 3.5, and I can confirm
that the same problem exists
Just had another one, but that's only the second time since switching to
Jackelope, so I feel like it's mostly cured. However, I'll say this was
an especially nasty one to fix. The automatic recovery did not work and
after several failed iterations, I remembered to try a manual fsck,
which seems
Well, now I can't find the other bug report that I prepared, but the
problem is more complicated than it appears, and it only affects
Firefox. Since I can't find that bug, I'll go ahead and summarize the
critical details here, and attach the NTTPC certificate that is supposed
to use GlobalSign.
I'm still confused why it works for IE but not Firefox, but this doesn't
seem to be the right venue for that discussion in detail. I did try to
find out what was going on, but obviously didn't get the right
reference. Can you post a URL for an explanation focusing on the
specific problem you
Well, whatever is going on is rather more complicated, but I'm going to
report those details over in a newer bug report. However, what I can say
is that there is definitely something wrong with the way Firefox is
handling this Certificate Authority, even though the appropriate root
authority is
More data: There appear to be two GlobalSign root certificates--and they
are already installed. Here is a case-by-case report of what I know:
In Ubuntu (with Firefox, of course), the NTTPC certificate fails,
reporting that GlobalSign is not known. Looking in the list of installed
certificates, it
Figured out how to read it, though not how to cut and paste it into this
system (though I'd think some expert there should be able to figure it
out from the file I attached?). So here is the scoop on the anti-Firefox
security certificate:
Common Name: GlobalSign Domain Validation CA
Organization:
I ran into this same certificate authority being used by NTTPC, a
subsidiary of NTT, the main phone company of Japan. IE accepts it, but I
don't think it's pure anti-Firefox behavior, just typical mindless
incompetence from the NTT zombies.
The status of this bug seems to claim the bug has been
Public bug reported:
Not sure exactly where to report this, but the problem is really a kind
of anti-Firefox problem. The security certificate is supported by IE,
but returns the error message below from Firefox. I've tested it both in
Ubuntu and under Windows (in the same machine where IE
** Attachment added: www.nttpc.ne.jp
http://launchpadlibrarian.net/28438182/www.nttpc.ne.jp
--
Security Certificate only valid for IE
https://bugs.launchpad.net/bugs/392691
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I should have known better to say anything...
It's back! Unprovoked and unexplained white screen of death.
Oh well. Overall I still think Jaunty Jackalope is generally better than
the last few releases of Ubuntu for this troublesome machine. Time to
try a complete install from scratch?
--
Knocking on wood, but it seems that Jackalope has fixed this bug. I
haven't seen any of these crashes since I upgraded to Jackalope.
--
Crash to white screen of death (possibly Firefox?)
https://bugs.launchpad.net/bugs/159594
You received this bug notification because you are a member of Ubuntu
Public bug reported:
No warning messages or anything, but NetworkManager is unable to share a
connection unless dnsmasq-base is installed. When you select the option
to share the connection Shared to other computers, it should obviously
warn you if dnsmasq-base is not installed.
I saw some
Public bug reported:
This D02HW is a Chinese-made USB device, but will not connect through
NetworkManager. I've been told that eMobile has configured their network
in such a way that this problem affects many of the other devices they
supply for use with their wireless network. (The eMobile
Seems pointless to note that I'm another victim of this bug, closed or
not. Main reason I'm replying is because this particular description of
the problem seems to match my own particular version of the problem more
closely than the various other bug reports I've looked at. I would say
so far, but
Me, too, on the death of sound. Tried many of the things in this thread,
followed some of the links and tried lots of the things in those places,
too. Already spent way too much time on this, so I'm giving up, but just
feel obliged to note that it seems to be another example of Ubuntu not
being
With poppler-data installed it shows garbage characters all over the
place. Some of them were graphic characters, and others looked like
numbers from Unicode. Seems like xpdf is still the solution.
Thanks for the suggestion.
--
Can't read PDF file with Japanese text
Well, I just checked the latest Japanese file, and it's still broken,
and xpdf still works properly.
--
Can't read PDF file with Japanese text
https://bugs.launchpad.net/bugs/197537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Whoops. I forgot to note that I'm running Ibix 8.10 now, and with all of
the latest updates.
--
Can't read PDF file with Japanese text
https://bugs.launchpad.net/bugs/197537
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Seems to be worse than usual now. Already two crashes this morning.
At this point I'm teetering on giving up Ubuntu. It's not very useful
when the machine can crash at any moment, is it?
I suppose the alternative would be to try a different computer, but that
sort of cancels the argument that
I'll just note that I ran into some of these problems again in
conjunction with some more upgrades. I'm getting much too familiar with
the internal GRUB commands to find partitions and to find and display
files.
I feel like the proper solution would be a graphic repair interface for
GRUB. In
I have just confirmed that it continues to exist in Ibex, but I still
have no real idea about the real cause and I'm still unwilling (and
regard myself as basically technically incompetent) to tackle the
complicated backtrace procedures.
Currently what I have done is disable the proprietary
Bug has survived the transition to Ibex, apparently. I initially did the
upgrade to a scratch partition and ran it for a few days without seeing
the crash, but as soon as I upgraded my main working partition, it
returned. At least twice in the last few days since I did the upgrade.
I noticed that
Mostly just noting that I ran into this too, and think it should have a
high priority for repair. Many, or perhaps most people will never even
notice that it's hung up.
I also wish someone would modify the misleading directions. Being too
enthusiastic, I used the version that said to detach from
The frequency of the crashes is increasing again after a low-crash
period. Lovely pastel death this morning.
Right now I have to regard the machine when running under Ubuntu as
unsuitable for any serious work (unless the working program includes a
Gmail-like remote backup every few minutes). This
I haven't been willing to try Intrepid yet, but I'm still seeing it on
one machine. I actually have a highly reproducible version on that
machine. Do you want me to try to get some diagnostics, or can it be
regarded as a moot point as Intrepid arrives?
--
There was an error starting the GNOME
Well, I can now confirm that the .gnomerc approach did not solve the
problem. There was one crash since I added that file. Just to confirm I
did it right, here is the cat result:
[EMAIL PROTECTED]:~$ cat .gnomerc
export WINDOW_MANAGER=metacity
I need to run another memory check from GRUB, but I
Getting really bad these days, with increasingly frequent crashes. Minor
variant is that not all of them are white screens now, but sometimes
pastel colors of various types.
--
Crash to white screen of death (possibly Firefox?)
https://bugs.launchpad.net/bugs/159594
You received this bug
There is no .gnomerc file here, and I have upgraded to Hardy. The
problem is rather sporadic, and so far I haven't been able to spot any
sure-fire trigger. Sometimes it doesn't appear for weeks, and other
times it will happen several times within a few hours.
--
Crash to white screen of death
Just had another one. At least three or four crashes in the last few
hours...
I'm trying your .gnomerc solution, though I'm not happy about the idea
of winding up in a unique configuration that I don't really know how to
maintain
--
Crash to white screen of death (possibly Firefox?)
What new information did you ask for? The bug still existed the last
time I checked, but you never asked for anything else. I understand you
want to close the open bug reports, but shouldn't you fix the bugs
first?
Would it help to remind you that Microsoft Office does print tategaki
correctly?
Just had another one, and there was a day last week when I had about
three of them in just a few hours. Seems like it's getting worse again.
However, it also seems like no one else is seeing it... Not sure what
that signifies, but I don't feel like this is an especially odd machine.
Perhaps the
Not sure which way you're handling this, but the bug is still present in
the default document viewer as of today. However, my workaround was to
install the xpdf viewer, and it handles the Japanese without any
problems.
--
Can't read PDF file with Japanese text
Hadn't seen it for a while, but just had one a few minutes ago. Still
don't know what diagnostic information to collect, and still can't stop
any particular trigger event.
--
Crash to white screen of death (possibly Firefox?)
https://bugs.launchpad.net/bugs/159594
You received this bug
Mostly I'm running Hardy now, and I haven't attempted to use Java on my
last Gutsy machines. However, I concur that the bug is probably
closeable, but still don't know how to do it.
--
gcj plugin broken and won't uninstall
https://bugs.launchpad.net/bugs/159649
You received this bug notification
I still see it sometimes, but more rarely. It's become one of those
things that's fluttering at the edge of traceability. That machine
actually has two versions of Ubuntu on it right now. My feeling is that
the problem is less common with Hardy Heron, but more common with Gutsy.
When it does
No one else has reported a similar problem on this bug, and I haven't
seen it in a long time, so I think it can be closed on the belief it was
related to some software that was upgraded later on. However, I don't
see any way for me to close it.
Wait, maybe I found it...
--
Can't quit Firefox or
Seems to be the only thing I can mark it with, though it's basically
just a guess that the bug was fixed by something somewhere.
** Changed in: firefox (Ubuntu)
Status: Invalid = Fix Released
--
Can't quit Firefox or shutdown computer
https://bugs.launchpad.net/bugs/229425
You received
Nope. I see where I can add new statuses, but none of the available
options seems to be the correct one for it.
--
Can't quit Firefox or shutdown computer
https://bugs.launchpad.net/bugs/229425
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1 - 100 of 207 matches
Mail list logo
