I know this has been marked as 'wishlist', and perhaps it's not an issue
for most people, but I've had to revert to using the .deb because this
bug breaks my workflow every day (I receive and open lots of documents
via email and through websites using Firefox).
--
You received this bug
Is this bug still relevant? I have tried the latest ubuntu/xenial64
(v20201104.0.0) and it boots without any problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615579
Title:
Vagrant fails to
The problem is if you have LibreOffice installed as a snap and try to
open an attachment in Thunderbird, LibreOffice will generate an error
message saying that it can open the file because it does not exist (in
reality it does exist but LibreOffice can't read it, so the message is a
bit
Sorry, that should be: LibreOffice will generate an error message saying
that it *can't* open the file
(Launchpad really needs a comment edit function!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In case anyone else hits this problem and is wondering about the root
cause, it seems to be because snaps generally can't access data from
other applications, so when Thunderbird drops a file into /tmp
LibreOffice can't "see" it. This isn't unique to LibreOffice, it causes
problems for other snaps
In case anyone else hits this problem and is wondering about the root
cause, it seems to be because snaps generally can't access data from
other applications, so when Thunderbird drops a file into
This doesn't happen with the non-snap version of LibreOffice distributed
through the Ubuntu archive
Confirmed that this still definitely fails in a clean 16.04 VM. Other
composer commands work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595289
Title:
composer validate can't find
How did you install composer, was it via the Ubuntu package (`apt
install composer`) or via getcomposer.org?
I've just installed the composer package into a clean 18.04 VM and I can
run composer install, composer --version etc.
--
You received this bug notification because you are a member of
Is this bug still valid? 15.10 has been unsupported for over two years
now and 18.04 has a more recent version of Composer (although still
behind upstream, which I'm hoping to fix with a Snap or PPA).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Liz: There are two options towards the top-right of the page, underneath
the list of bug duplicates:
Mute bug mail - Click this to stop any emails from this bug (you'll
remain subscribed so it will show in your list of bugs on Launchpad)
Edit bug mail - Click this to control which emails you
Just as a head's up (since this is the first search result for 'ubuntu
ads-2100e'), this is still broken in 16.10 as well. I've tried reporting
a new bug using 'ubuntu-bug simple-scan' but I get an 'Invalid OpenID
transaction' error when my web browser opens.
--
You received this bug
Is there anything we can do as users to help get this fix pushed out?
Does it need to be tested?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641380
Title:
chromium-browser:
I'm running into this on Lubuntu 16.04.1 too - i386 and amd64 desktop
ISOs (downloaded yesterday). Tried on multiple machines with the same
results, but the workaround fixed the problem.
The error message is: "An unsafe swap space has been detected" (I
couldn't find this bug by copying + pasting
I can't reproduce this on either of my Ubuntu machines, both of which
are running the same version of Vagrant and the Linux kernel.
What happens if you run 'vagrant box update' in the same directory as
the Vagrantfile? It could be that you are running an older box which
doesn't have this issue
What happens if you try the following (this will download a box from
vagrantcloud.com):
vagrant init ubuntu/trusty64
vagrant up
I know that box works, so if you still get the same problem then that
helps narrow it down.
--
You received this bug notification because you are a member of Ubuntu
Can you post the command you ran which resulted in the error message and
your Vagrantfile please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553666
Title:
`validate_options': Missing required
What did you do to cause this error message?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553666
Title:
`validate_options': Missing required arguments: libvirt_uri
(ArgumentError)
To manage
That workaround fixed the problem for me too - turns out the image I was
working with already had gamin installed. Purging gamin also removed
lighttpd, then re-installed lighttpd produced the following:
Setting up lighttpd (1.4.35-4ubuntu1) ...
Job for lighttpd.service failed. See "systemctl
I'm unable to reproduce this problem on a clean install with no
configuration - installing lighttpd and then visiting http://localhost
brings up the default placeholder page.
What happens if you disable all your user-defined configuration files?
Can you get the basic placeholder page up?
--
You
I'm sorry, but I disagree - this *is* a bug, it involves unexpected
behaviour when running an application. That's either a bug with Fluxbox,
the application, or the interaction between the two.
However, if the fix is to pass extra arguments to the Nautilus command,
perhaps a simple way to close
The Chrome argument does not address the problem that if I launch
Nautilus from the menu then I can no longer access the menu, even if I
quit Nautilus using the standard cross icon in the top right corner of
the window. Plus, even if I kill all the Nautilus processes, the
background image has
--no-background isn't a valid argument according to the man page (on
trusty).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/69938
Title:
Fluxbox background disappears on certain events
To manage
** Also affects: fluxbox
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/69938
Title:
Fluxbox background disappears on certain events
To manage
*** This bug is a duplicate of bug 1240198 ***
https://bugs.launchpad.net/bugs/1240198
** This bug has been marked a duplicate of bug 1240198
Wrong keyboard layout active after booting into desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This problem is still occurring in Trusty, it's extremely frustrating as
the inability to get a menu up and running means no programs can be
launched other than through a terminal.
Steps to reproduce:
1. Install Ubuntu Desktop 14.04 from latest ISO image.
2. Install fluxbox using: sudo apt-get
I can confirm this bug occurs for me in 12.04 with the following mysql
version:
mysql Ver 14.14 Distrib 5.5.29, for debian-linux-gnu (x86_64) using
readline 6.2
I did a bit of Googling and found this bug, which might be related:
http://bugs.mysql.com/bug.php?id=65053
The final comment
I can confirm the fix in #6 works for me. Perhaps the Ubuntu package
should just have that option enabled by default as a temporary measure?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001405
Is there anything we can do to help identify what the outstanding
problem is and get this bug fixed? Perhaps it's just that some of us are
running the 'wrong' package or haven't got the update yet (although I'm
running a standard 12.04 installation with no PPAs, all updates
installed etc.).
--
I don't have any libreoffice3.4* packages installed and I'm experiencing
the same problem, seems to have surfaced in the past couple of days for
me (on an up to date 12.04, no PPAs). At present my only workaround is
to fire up an XP VM and read the spreadsheets in Excel.
--
You received this bug
Just to add as a comment to people suggesting editing php.ini, what you
should actually do is edit /etc/php5/conf.d/local.ini, as that will
override any php.ini settings without causing configuration conflicts
when you next upgrade PHP (apt will warn you that the file you are using
differs from
Just to add as a comment to people suggesting editing php.ini, what you
should actually do is edit /etc/php5/conf.d/local.ini, as that will
override any php.ini settings without causing configuration conflicts
when you next upgrade PHP (apt will warn you that the file you are using
differs from
Clicking the little edit icon next to the duplicate number and blanking
out the 'duplicate of' number field removes the duplicate relationship.
I think any logged in user can do this, although you might need a
certain amount of karma.
** This bug is no longer a duplicate of bug 831907
Default
Clicking the little edit icon next to the duplicate number and blanking
out the 'duplicate of' number field removes the duplicate relationship.
I think any logged in user can do this, although you might need a
certain amount of karma.
** This bug is no longer a duplicate of bug 831907
Default
Public bug reported:
The default configuration file for vsftpd (/etc/vsftpd.conf) in natty
contains the following line:
rsa_cert_file=/etc/ssl/private/vsftpd.pem
However, this file does not exist, so any attempt to enable SSL
(ssl_enable=YES) will cause the following error to be logged in
Public bug reported:
The default configuration file for vsftpd (/etc/vsftpd.conf) in natty
contains the following line:
rsa_cert_file=/etc/ssl/private/vsftpd.pem
However, this file does not exist, so any attempt to enable SSL
(ssl_enable=YES) will cause the following error to be logged in
A minor comment on upgrading - I could not add any more Twitter accounts
(or authorise my existing accounts) after an upgrade on Lucid.
Restarting my machine fixed the problem - perhaps gwibber-service was
not restarted automatically after the package had been upgraded?
--
Twitter dropping
Is testing in a VM good enough (I don't want to enable proposed on my
main machine)? If so I will give it a whirl tonight on lucid.
--
Twitter dropping support for basic auth
https://bugs.launchpad.net/bugs/627565
You received this bug notification because you are a member of Ubuntu
Bugs, which
Confirmed working here on a clean (updated to latest packages)
installation of Lucid in a VM.
--
Twitter dropping support for basic auth
https://bugs.launchpad.net/bugs/627565
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Marking this as invalid as it seems to be a general problem with
virtualisation software - VMWare Player freezes up the system in the
same way when virtualisation extensions are enabled.
** Changed in: virtualbox-ose (Ubuntu)
Status: New = Invalid
--
Virtualbox crashes when 64-bit
Public bug reported:
Binary package hint: virtualbox-ose
I have an Intel E6500 processor with virtualisation extensions in a
desktop with 4GB of RAM. I've tried creating 32 and 64 bit guests under
the latest (in the Karmic repositories anyway) version of VirtualBox OSE
and I find the following
40 matches
Mail list logo
