Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
(In reply to Matthias Versen [:Matti] from comment #1)
The global private browsing mode got replaced by a per window private
browsing mode.
Could you test a nightly build from mozilla.org ?
I tested it on the nightly build and the bug is occurring there as well.
--
You received this bug
Confirmed this in Firefox 19.0.2 in Kubuntu 12.04. This behavior is
present both with Never remember history set in preferences and if
Private Browsing is entered while Remember history is set in
preferences. I also checked this on my Windows 7 install (also running
Firefox 19.0.2), and this does
This appears to be affecting upstream since I tested the download from
Firefox's website and the issue occurred there as well. Marked as
affecting Mozilla Firefox, but need to eat before I can file a bug
report in their tracker.
** Also affects: firefox
Importance: Undecided
Status: New
** Bug watch added: Mozilla Bugzilla #851816
https://bugzilla.mozilla.org/show_bug.cgi?id=851816
** Changed in: firefox
Importance: Undecided = Unknown
** Changed in: firefox
Status: New = Unknown
** Changed in: firefox
Remote watch: None = Mozilla Bugzilla #851816
--
You
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
Looks like the typos that caused this were fixed in 0.9.7-0ubuntu7.7.
Marking Fix Released since this only affected -proposed to begin with.
** Changed in: jockey (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1068818 ***
https://bugs.launchpad.net/bugs/1068818
Sorry, didn't catch this before but this particular bug has already been
reported and is a duplicate of bug 1068818, so it is being marked as
such. Please look at the other bug report to see if there is any
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please add the log files from '/var/log/dist-upgrade/'
to this bug report as separate attachments? Thanks in advance.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed = Incomplete
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please add the log files from '/var/log/dist-upgrade/'
to this bug report as separate attachments? Thanks in advance.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New = Incomplete
--
You
*** This bug is a duplicate of bug 1087457 ***
https://bugs.launchpad.net/bugs/1087457
Based on the error log, this looks like the same problem as Bug
#1087457. Marking as a duplicate.
** This bug has been marked a duplicate of bug 1087457
jockey-text and jockey-gui crash with failed
** Branch linked: lp:ubuntu/precise-proposed/jockey
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087457
Title:
jockey-text and jockey-gui crash with failed assertions
To manage notifications
I was able to get Jockey working again by removing a comma from line 24
of fglrx.py that appeared to be left over from a couple of strings being
cut/pasted in revision 153 in precise-proposed.
** Patch added: Patch to remove comma causing problem.
*** This bug is a duplicate of bug 1087457 ***
https://bugs.launchpad.net/bugs/1087457
** This bug has been marked a duplicate of bug 1087457
jockey-text and jockey-gui crash with failed assertions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: jockey (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093042
Title:
Jockey crashed when launching it
To manage notifications about this bug go
This report does not give any useful information. No details about the
crash or what release it happened on were given. You can right-click a
crash file with jockey in it in the /var/crash folder in the file
system to upload information about this crash for the developers to look
at.
--
You
20 matches
Mail list logo
