>Also on my system when I click the Bookmarks toolbar it
> will randomly choose a menu option, usually the top entry 'bookmark this
> page'.
(Note: I'm assuming you mean the Bookmarks *Menu*, not the Bookmarks
Toolbar)
If it usually selects the top entry, that makes me think that specific
probl
FWIW, I have this exact same problem using VMWare Workstation with this setup:
host = Ubuntu 8.10
guest= Ubuntu 8.04
VMWare Workstation version = 6.5.0 build-118166
In this setup, UpArrow triggers 'save screenshot' (in the guest),
RightControl types out "^[[6~", PageDown triggers context men
@Mitchell:
> in fact there seem to be a bug in the firefox 3 code, so the menu should
> not be released when the right button is pressed, it should be showed
> when it is released
Just to clarify -- the quoted chunk above isn't quite accurate.
The timing of context-menu-appearance in firefox 3 is
>This is preventing other packages (miro in my case) from building.
This same issue prevents the "revelation" password-manager app from
installing (and maybe building?), due to its dependency on "python-
gnome2-extras", which depends on the broken "python-gdl" package.
--
Uninstallable in Karmic
Confirmed, on Ubuntu 9.04 x86.
I did a bit of investigation:
- I examined the menu item for Galculator, and it's set up to use
/usr/share/pixmaps/galculator.png
- This file is a symlink to "galculator/galculator.png", which **doesn't
exist.** (the folder 'galculator' doesn't even exist)
That'
*** This bug is a duplicate of bug 187313 ***
https://bugs.launchpad.net/bugs/187313
Yeah, it's a dupe. Right vs left mouse button isn't relevant -- the
connection is that it's a single-click that opens a menu (whether it be
a left-click opening the bookmarks menu, or a right-click opening a
FWIW, the upstream patch (in Mozilla's bug tracker) has just recently
landed in the repository that Firefox 3.0 is built from -- assuming all
goes well, that means this should be fixed in Firefox 3.0.10. (It also
should be fixed in Firefox 3.5b4)
--
[MASTER] right click (with button release) mig
IAmDaveMyers wrote:
> So I will hover over the menu item, left click
> to open it (to go to a specified bookmark), and I will be offered
> to save the page as a bookmark!
Thanks Dave -- that actually sounds exactly like
https://bugzilla.mozilla.org/show_bug.cgi?id=406646 (one version of this
bug
> First though, can you point me to instructions as to how I can load up the
> "testing" version,
David: there's a lot of ways to load up the testing version -- I'm not sure if
anyone's posted a comprehensive set of directions, but here's one thing you can
do:
- download the "xxx-linux.tar.bz2"
Artem: Please read at least the final few comments before posting on a
bug If you had, you'd see that this bug already has a patch that is
targeted to be in a release very soon. (As mentioned multiple times
above, "me too" comments are un-helpful at this point, and they only
serve to make thi
See also bug 290730 (related, possibly a duplicate)
--
update-initramfs is disabled since running on a live CD but it is running from
a flash drive.
https://bugs.launchpad.net/bugs/292159
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Jean-Baptiste Lallement:
> You can't upgrade the kernel from a live cd.
> I'm closing this report because it is not a bug.
I disagree -- this is indeed a bug.
If it's not possible to upgrade the kernel, that's fine. But in that
case, the kernel version should be locked for live CD / live USB
b
Just in case it's not obvious: this crash happens *before* xorg.conf is
modified. So, there's currently no way to get my "nvidia-settings"
preferences into my xorg.conf, aside from hand-editing it.
--
nvidia-settings crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad
Pako: If your problem was fixed by running nvidia-settings as root, then
you had a different problem from this bug here.
I always run nvidia-settings as root (with 'sudo'), and I still see this
crash in fully up-to-date Ubuntu 8.10 today.
--
nvidia-settings crashed with SIGSEGV in g_cclosure_mar
I hit a related crash in the revelation gnome-panel applet, every time I
unlock / search it -- it's the same underlying problem, crashing at line
1261 in ui.py, on the code "self.image = self.get_children()[1]" with
the error being "IndexError: list index out of range".
I filed an upstream bug ab
Ah, thanks! In any case, my point was that bug 257007 is the same
underlying bug as this one -- it's just another way of hitting it.
--
error when right-clicking password field
https://bugs.launchpad.net/bugs/260293
You received this bug notification because you are a member of Ubuntu
Bugs, which
BTW, I filed an upstream bug on this exact problem a little while back,
at http://svn.codepoet.no/revelation/ticket/405 a while back (though I'm
not sure if upstream code is still being maintained, so I wouldn't
expect a fix to be forthcoming there).
See also bug 260293 -- it's caused by the same
This patch for src/lib/io.py seems to work. It just unquotes any
escaped special characters in file URIs passed to "file_normpath", using
the urllib.unquote() function.
More info at:
http://docs.python.org/lib/module-urllib.html
** Attachment added: "patch for src/lib/io.py"
http://launchpad
> the patch needed to fix the problem does not need approval anymore
I think you misunderstand -- comment 176 on that bug says it doesn't
need approval *to land on the 1.9.1 branch* (for Firefox 3.1 aka 3.5),
since it's already marked as "blocking1.9.1+".
However, it still *does* need approval to
> Looks like it is fixed in 9.04.
I doubt it -- there's no reason that this should already be fixed in Ubuntu
9.0.4. if you can't reproduce it there, I'm guessing that's just due to the
inherently low reproducibility of this bug on many machines. (mine included --
I've only ever encountered thi
> It worked instantly afterwards here.
It worked for me as well. I didn't need to move the file -- I just
edited it and removed the block of 132 lines relating to SanDisk
products (all nodes of the form "...), and then I reconnected my player (an e280
running Rockbox), and it worked.
--
Sandisk
I noticed that this bug says:
Affects Status
linux-source-2.6.17 (Ubuntu)Fix Released
at the very top. Does that mean that the bug would be fixed if I rolled back
to kernel 2.6.17?
(not sure if this is possible in Feisty -- at leas
I agree with Alberto's description of the issue -- I've seen the same behavior
with my 500G FreeAgent.
i.e., the issue happens after the drive shuts off, and then at that point, any
access seems to cause problems.
Also, JrFrost's solution has still been working for me. (although I need
to repeat
KEYofR wrote:
> Also a question about the udev rules [...] if you detect a device by vendor
> foo on scsi
You're right -- some of the udev rules posted above are overly general.
You can make them more specific by specifying the model of drive, or
even the drive serial number if you want to be tha
Hi all,
JrFrost's solution fixes my 500G FreeAgent drive!
(his solution being:
echo 1024 > /sys/block/sdX/device/max_sectors ;
echo 1 > /sys/class/scsi_disk/X\:0\:0\:0/allow_restart
)
However, this setting doesn't persist after I've disconnected the drive
-- I need to run those commands every
@stacktracer's workaround worked for me.
@StephanBeal: That file exists on my Ubuntu Karmic system -- I'm not
sure why it doesn't on yours. "dpkg -S [filename]" says that it's owned
by the package "devicekit-power". Anyway, I'm attaching my copy, for
your benefit. (with the workaround already app
@Martin:
> or be autodetected from the system whether it's capable of suspending
> in the first place (see devkit-power --dump, "can-suspend" and
> "can-hibernate" properties; this part should work fine).
This sounds like it'd still present "Hibernate" as an option on
computers that have encrypte
> WARNING: synergys.cpp,505: cannot listen for clients:
> cannot bind address: Address already in use
That just means you already have synergys running on that machine... Do
"killall synergys" and try again.
--
synergys assert failure: synergys: CArchMultithreadPosix.cpp:286: virtual void
CArc
Chris, I'm not sure what that issue means -- perhaps a firewall /
connectivity problem? -- but in any case, we shouldn't discuss it any
further here. I'd recommend taking that to Google, the ubuntu forums,
or #ubuntu on irc.freenode.net.
This bug page here is for discussion of the specific issue
There's already a mozilla bug on this, actually:
https://bugzilla.mozilla.org/show_bug.cgi?id=485067
As described there, it appears to be a bug in GTK. Filed an upstream Gnome bug
on it today:
https://bugzilla.gnome.org/show_bug.cgi?id=603823
** Bug watch added: Mozilla Bugzilla #485067
http
NetworkManager (aka "nm-applet") is running just fine for me, but I've
rebooted since my "dhclient" invocation -- if you haven't, it's possible
that NetworkManager got confused because you'd already configured your
network since bootup. Try rebooting?
In any case, if your NetworkManager problem p
If you have a root shell, you should be able to auto-configure your network
connection by running:
dhclient eth0
(where "eth0" would be the name of your network interface, as reported by
"ifconfig")
This worked for me earlier today, when I only had a shell with no
networking.
--
Karmic Late
As I noted in comment #92:
***PLEASE*** do not comment on this bug unless you are actively working on it,
and/or unless you've read *all* comments and have determined that your
information is genuinely new and useful. This bug receives way too much "Me
too" spam, and all the comments here just
Unless you have new information about this bug, please don't add "me
too" comments -- instead, just toggle the "this bug affects me too" link
at the top of this page. Thanks!
--
empathy assertion failure:
empathy:ERROR:empathy-tp-chat.c:1391:empathy_tp_chat_acknowledge_message:
assertion faile
Here's a patch that adds the one line that I mention above.
** Attachment added: "patch to modify original xorg.conf, so nvidia-settings
can parse it"
http://launchpadlibrarian.net/33248486/xorg.patch
--
nvidia-settings crashes when user clicks Save To X Configuration File
https://bugs.launc
There's actually a HUGELY simple fix for this.
The error message given indicates that xorg.conf is failing to validate
because "Screen" doesn't reference a device, basically.
You can fix this by adding this line to /etc/X11/xorg.conf, under Section
"Screen":
Device "Default Dev
> This bug seems to be in Empathy and not libindicate itself.
@Ted: I'm confused -- did you read comment #44, where an empathy
developer tracked the problem to a particular chunk of "Ubuntu's
libindicate patch"?
--
empathy assertion failure:
empathy:ERROR:empathy-tp-chat.c:1391:empathy_tp_chat_
> I've noticed this doesn't happens when you upgrade form 9.04 to
> 9.10 but if you install 9.10 from scratch you will see the error
That's expected -- the problem here is that Ubuntu's **default**
xorg.conf file file is missing a line.
If you're upgrading from 9.04 to 9.10, Ubuntu probably keeps
> Why would you have to *save X configuration file* as long as
> the newer nvidia drivers sets out the resolution automatically?
Because nvidia-settings lets you customize much more than just
resolution -- e.g. if you have multiple monitors, nvidia-settings lets
you pick which monitor is on which
** Changed in: empathy (Ubuntu)
Status: Fix Released => Confirmed
--
empathy crashed with SIGSEGV in g_type_check_instance_cast()
https://bugs.launchpad.net/bugs/439732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
(sorry -- the "[1]" link above was from a block of text that I ended up
deleting from my comment. It's the documentation for the -webkit-user-
drag property, for controlling drag-and-drop.)
--
Dragging from the installer Webkit widget crashes Ubiquity
https://bugs.launchpad.net/bugs/434413
You re
This bug actually has a much simpler workaround: use CSS to disable
image-dragging in ubiquity-slideshow-ubuntu. There's no rational reason
that a user would need to drag and drop images from the installer.
The attached patch does this, for all elements in ubiquity-
slideshow-ubuntu. I initially
I've un-duplicated this bug.
Bug 434413 (this one's former duplicate) is about the underlying crash in
pywebkitgtk.
I'm hereby declaring this bug to be about the specific instance of the crash in
ubiquity-slideshow-ubuntu during installation.
This particular instance of the bug is easily fixed b
Since this bug is located in the "pywebkitgtk" component and seems to be
about the underlying crash, I've moved my band-aid patch (from comment
7) to bug 448703. Let's keep this bug here focused on the underlying
crash, while bug 448703 can be about a cosmetic fix to avoid the crash
in ubiquity.
@evand -- I talked to cjwatson in IRC briefly, and he suggested I talk
to you about getting this change checked in. I've just subscribed you
to this bug -- let me know if there's anything else I can help with
here. Thanks!
--
Installer crashs when dragging the slideshow icons
https://bugs.launc
** Attachment removed: "debdiff for ubiquity-slideshow-ubuntu: disable dragging
of images"
http://launchpadlibrarian.net/33560121/disable_drag_and_drop.debdiff
** Attachment added: "debdiff for ubiquity-slideshow-ubuntu: disable dragging
of images"
http://launchpadlibrarian.net/33560523/d
** Summary changed:
- Installer crashs when dragging the slideshow icons
+ Installer crashes when dragging the slideshow icons
** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
Assignee: (unassigned) => Daniel Holbert (dholbert)
--
Installer crashes when dragging the slideshow icons
ht
** Summary changed:
- Dragging from the installer Webkit widget crashes Ubiquity
+ Dragging from the installer Webkit widget crashes Ubiquity [worked around by
bug 448703]
--
Dragging from the installer Webkit widget crashes Ubiquity [worked around by
bug 448703]
https://bugs.launchpad.net/bug
> The first slide, on the other hand ("welcome" and "f-spot")
Sorry -- I meant "The first and third slides" (as examples)
> 237x237 is fine, but 100x237 up to 235x237 will crash.
Smaller widths will crash as well -- I didn't mean to imply that 100 was an
absolute minimum there.
--
Dragging from
FWIW, this bug only seems to happen with non-square images. The second
slide in the slideshow, for Firefox, uses a square PNG file -- and it
doesn't crash if you drag it. The first slide, on the other hand
("welcome" and "f-spot") use rectangular images (taller than they are
wide), and they crash
Patrick Roberts:
>2) Because in Linux a context menu is shown when PRESSING
> the secundairy mouse button, instead of when RELEASING
> the secundairy mouse button.
FWIW, this generalized GTK issue has already been noted above.
(Searching this bug for "nautilus" will give you the relevant comments
The stacktraces don't look very similar to me...
And even if they were similar, bug #437111's patch looks super-targeted
to fix its specific crash. it's a _very_ small fix, which just adds a
return-if-null immediately before that bug's crash. (specifically,
before the call to empathy_account_sett
@Edmond:
> I want to confirm this was a bug, but it has been fixed,
> Thanks Jinx-Wolf, your suggestion worked perfectly.
Just to clarify -- that doesn't sound like this bug "has been fixed".
It sounds like you worked around the bug on your own machine, but the
bug remains in un-worked-around inst
@Eddie:
It sounds like you've got a completely different issue from the problem
described in this bug (crashes on clicking 'save' in nvidia-settings). This bug
already has over 100 comments (and is still unfixed) -- if it turns into a grab
bag of miscellaneous nvidia-settings complaints, it will
FWIW: This worked in Jaunty, so this is a new bug in Karmic.
This is particularly important for people running with encrypted swap
partitions, because hibernate doesn't play nicely with encrypted swap
yet. Whenever I shutdown / suspend / restart, I'm constantly afraid
that I'll accidentally cliic
I didn't file this bug, nor am I sure if it's still reproducible (or how
to reproduce it), so I'm not filing a new bug.
I explained why I reopened it in Comment #5 -- I don't agree with (or
perhaps understand?) your justification for closing it in the first
place. The "fix released" on bug #43711
As noted on the github issue, Fedora doesn't seem to be affected at all
(when testing the same ibus/mutter/Firefox versions as in Ubuntu). So
this is seeming to be Ubuntu-specific, fortunately/unfortunately...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
RE cosmic (replying to
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/comments/52
and
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/comments/55
):
I've installed the proposed gnome-shell-common and gnome-shell package
updates, and I don't see any issues so far (after a r
*** Bug 1538487 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551949
Title:
Printing to PDF file loses URLs/links
To manage notifications about this
*** Bug 1536707 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811105
Title:
Browser hangs when 'open with' dialog opens.
To manage notifications abo
The fix seems good to me!
My verification steps:
- I verified that I could still reproduce the issues in the first post here,
in a stock Ubuntu 18.04.1 installation in a VM (all package at their "freshly
installed" version, including Firefox).
- In doing this, I tested both scenarios from the
Hi Brian. I have been running Cosmic (Ubuntu 18.10) as my main OS since
its release, and I don't think I've ever actually hit the bug on Cosmic.
(I just verified that I have the GTK_IM_MODULE=ibus variable set, too.
So I think I would be hitting this bug, if Cosmic were affected.)
So, my assumpti
(My experience [of Cosmic being unaffected] seems to match what was
reported in comment 44 (
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/comments/44
), too.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Public bug reported:
tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
Firefox, whenever the user tries to focus an
field on a web page. This is not a regression in Firefox, as the same
Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
in ibus, because it only
> the bug might be better placed on https://github.com/ibus/ibus/issues
instead.
Thanks -- I'll file an issue there, too, later today. (I wish I knew how
to test old ibus builds & bisect between them so that I could extra-
confirm that it was an ibus change that broke this, and perhaps bisect
to f
Filed upstream: https://github.com/ibus/ibus/issues/2002
** Bug watch added: github.com/ibus/ibus/issues #2002
https://github.com/ibus/ibus/issues/2002
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
Not sure what happened. I just got a notification that something had
gone wrong after I logged in, and I clicked through to report it.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: software-center 16.01+16.04.20160217
ProcVersionSignature: Ubuntu 4.4.0-10.25-gener
[CC'ing Alexander, Arzhel/xionox, & Chris, who are all listed as
"Contributors" at the top of UpdateNotifier.js, one of the affected JS
files. Hoping one of them can address this or might know who can.]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Great, thanks Chris!
Note: I am not a JS expert, so my suggested replacement in comment 0
might not be exactly right for all cases of this pattern. (I believe
it's correct for code that's iterating over a JS array, but the
semantics might be slightly different for other structures, e.g. whether
y
I installed the kernel with the fix from zesty-proposed
(4.10.0-22-generic #24-Ubuntu), but after ~4 hours of uptime on that
kernel, I hit what felt like the same system lockup again. (Or perhaps
a new version of this lockup that the patch introduces / leaves
unfixed?)
Here's the kern.log from th
Public bug reported:
When starting a Firefox compilation job earlier today, my system locked
up; ctrl-alt-f1 had no effect, etc. (I was able to restart with the
REISUB technique.)
I'm on 64-bit Ubuntu Zesty, and I was running a kernel version that's
currently in zesty-proposed to have the fix for
** Attachment added: "kern.log snippet for lockup"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693357/+attachment/4882914/+files/kern-log-snippet.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
(I initially reported this issue via a comment on another bug, being unsure if
it was that bug or not:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/comments/208
I'm filing this as its own bug as directed there. Let me know if there's
any other information that I can/should captur
apport information
** Tags added: apport-collected zesty
** Description changed:
When starting a Firefox compilation job earlier today, my system locked
up; ctrl-alt-f1 had no effect, etc. (I was able to restart with the
REISUB technique.)
I'm on 64-bit Ubuntu Zesty, and I was running
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882926/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
Title:
Random
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882927/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882928/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
Title:
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882929/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16933
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882930/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
Title:
Rand
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882937/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
Titl
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882935/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/169
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882932/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882936/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882933/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882934/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882938/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
Title:
Ra
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882931/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
Title:
Rand
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882939/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
Title:
Ra
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1693357/+attachment/4882940/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693357
Ti
(Thanks @Rocko - I'd filed
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693357 but I've
now marked that as a duplicate of the bug you mentioned.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
*** This bug is a duplicate of bug 1680904 ***
https://bugs.launchpad.net/bugs/1680904
Over on the bug where I initially brought this up, Rocko tells me:
===
your lockup looks like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904 (and the upstream
bug is https://bugs.freedesktop.
Public bug reported:
On Ubuntu 17.10 Artful (current Ubuntu development version), the Firefox
package is extremely out of date for some reason.
Quoting the package page:
https://packages.ubuntu.com/artful/firefox
"Package: firefox (50.1.0+build2-0ubuntu1)"
Compare to these non-development Ubuntu
OK, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710306
Title:
Ubuntu 17.10 Artful has extremely out of date Firefox package (50.1.0)
To manage notifications about this bug go to:
https:/
As I just discovered & noted in
https://bugzilla.mozilla.org/show_bug.cgi?id=1306425#c10 , this doesn't
actually require any Firefox add-ons -- you can reproduce it in
Firefox's "Certificate Viewer" UI, too.
Anyway -- I'm glad we've got a fix in the pipeline here! Thanks, Martin!
** Bug watch add
Hi Chris! I'm still seeing this issue (in latest Firefox Nightly), BTW.
I'm also noticing that "about:startpage" (the default homepage imposed
by the extension) does not load in affected versions, possibly due to
this same issue.
Also: there's one more step that you need to perform before you can
I'm using Ubuntu 16.10 with latest Firefox & ubufox.
Package versions:
$ apt-cache show xul-ext-ubufox | grep Version
Version: 3.2-0ubuntu1
$ apt-cache show firefox | grep Version
Version: 50.0.2+build1-0ubuntu0.16.10.1
--
You received this bug notification because you are a member of Ubuntu
Bu
Public bug reported:
Firefox Nightly (53) no longer supports the non-standard "for each"
looping construct, as of
https://bugzilla.mozilla.org/show_bug.cgi?id=1293305
Unfortunately, ubufox uses this construct, which causes problems as shown in
the error console at startup:
> SyntaxError: missing
I had this exact problem, and I just figured out what was going wrong.
It turned out to be that I'd passed a nonexistent file to "--part" in my
vmbuilder command. (In the bug-reporter's case -- I'm not sure whether
--part accepts relative paths or not, but if you're sure that
vmbuilder.partition e
> hypervisor.optparser.error("%s parsing --part option: %s" % (errno,
strerror))
My python-fu is not strong, but from looking at the rest of the cli.py
file, I think we want "self.optparser", not "hypervisor.optparser".
Testing that to see if that fixes it locally...
--
You received this bug n
self.optparser didn't work -- tried that because there was one other usage of
that in the file, but it gives me
>AttributeError: 'CLI' object has no attribute 'optparser
So the existing "self.optparser" line is probably just as busted as this bug's
"hypervisor.optparser" line. :)
Trying just pla
1 - 100 of 159 matches
Mail list logo
