I have just now re-installed the system while unticking the option
"Download upgrades while installing" during the installation. And then
proceeded to do "sudo apt install build-essential gcc g++" and it worked
just fine. Then I did "sudo apt update ; sudo apt upgrade" and
everything is working fin
** Changed in: build-essential (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920753
Title:
Cannot install build-essential on fresh Ubuntu 20.04.2 installat
Ok, here is all the information you requested:
$ dpkg -l gcc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Descript
The version of gcc has been indicated in the initial bug report, please read it.
The output of 'apt policy g++' will be produced when I boot into that
installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Oh, I have some good news. I just couldn't believe that Ubuntu 20 is so
badly broken that it is impossible to compile anything (surely, it would
be noticed by someone!) so I installed it in a VM inside the VirtualBox
and "build-essential" was installable without any problems (and gcc
compiles progr
Just wanted to add that it is not just build-essential, but lots of
other packages required for development that cannot be installed, e.g.
this:
sudo apt-get install libwxbase3.0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages coul
Also, I confirm that there are no held packages, i.e. dpkg --get-
selections | grep hold shows nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920753
Title:
Cannot install build-essential on
I have indicated in the bug report that I have done "sudo apt update ;
sudo apt upgrade", so, yes the package lists have been updated, of
course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920753
And yes, I have executed the "apport-collect 1920753" as you suggested.
** Changed in: build-essential (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920753
Public bug reported:
After a fresh install of Ubuntu 20.04.2 (followed by upgrade to the very
latest packages) I installed gcc and then wanted to install build-
essential, but it fails with the following error message:
$ sudo apt install build-essential
Reading package lists... Done
Building depe
The link to https://bugzilla.gnome.org/show_bug.cgi?id=786511 doesn't
allow leaving comments because no account can be created in this system
(called "bugzilla" or something --- I vaguely remember maybe 15-20 years
ago it was working, but now it doesn't). I tried to create an account in
order to le
I agree with Serge that disabling support for single-page DjVu files is
a mistake. There is no valid reason to do so whatsoever.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778088
Title:
DjVu Fil
The single-page format is not old or deprecated because that is what is
created by the current versions of c44/cjb2 utilities and there is no
way to change it. So, if your document happens to consist of a single
page, then what you get is a single page djvu. In fact, even if you
explicitly use the
UPDATE: No, removing djvulibre-desktop solved the problem only for the
_multipage_ DjVu files, but not for the single-page ones. So, for a
single-page djvu files I still get the above-mentioned error message,
unless I manually add "image/vnd.djvu" to the end of MimeTypes in
/usr/lib/x86_64-linux-gn
Oh sorry, I forgot to include the info you requested. I am using Ubuntu
Linux 18.04.2 and I don't use "nautilus". I always open djvu files using
the command "evince filename,djvu" from within terminal. Well, sometimes
I use "djview filename.djvu" (when I want to find out the resolution),
but normal
Also, here is some useful info for you:
$ apt list --installed | grep djvu
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
djvubind/bionic,bionic,now 1.2.1-5 all [installed]
djvulibre-bin/bionic,now 3.5.27.1-8 amd64 [installed,automatic]
djvulibre-desktop/bionic,b
Oops, typo in the previous comment: I wrote "evince filename,djvu" but
of course I meant "evince filename.djvu", i.e. with dot "." rather than
comma ",".
** Bug watch added: Debian Bug tracker #876710
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710
** Bug watch added: Red Hat Bugzilla
Here are the links to the posts where this bug is mentioned:
https://ubuntuforums.org/showthread.php?t=2390953&page=2
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710
https://bugzilla.redhat.com/show_bug.cgi?id=1507305
--
You received this bug notification because you are a member of U
Public bug reported:
Every time I upgrade evince (as part of "sudo apt update; sudo apt
upgrade") I have to remember to edit the file /usr/lib/x86_64-linux-
gnu/evince/4/backends/djvudocument.evince-backend and add
"image/vnd.djvu" to the end of MimeType list. If I don't do this then
evince is una
Curiously, if I view the image via display(1) command of ImageMagick or
via the eog viewer used by GNOME file manager, then it displays with the
checked background. But if I view it via file:/// protocol in Chrome,
then the background shown is correct.
--
You received this bug notification becaus
Public bug reported:
The background colour of the terminal doesn't match the one shown on the
screenshot, please see the file attached. This happens even with built-
in colour schemes like "Solarised light".
** Affects: gnome-screenshot (Ubuntu)
Importance: Undecided
Status: New
**
I forgot to mention that this is on Ubuntu 18.04, kernel 4.15.0-32 and
all packages up to date.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787934
Title:
Checkered background in a screenshot
To
I went on irc for help and alexwolf provided the following workaround
which fixed the problem:
Open ~/.stellarium/config.ini and change all three instances of
http://stellarium... to https://www.stellarium...
After making this change stellarium works absolutely fine. Thank you.
--
You received
Public bug reported:
After the recent upgrade Stellarium crashes every time (even after rm
-rf ~/.stellarium) about 15 seconds (plus/minus 0.75 seconds) after
starting up with the following error message:
Failure getting IP-based location:
"Error transferring http://freegeoip.net/json/
I don't use apport infrastructure because I always uninstall such things
("security" etc) after installation of Ubuntu, which makes it boot about
20 times faster (0.9 seconds vs 15 seconds).
However, I am a Linux kernel developer with more than 20 years'
experience, so I am sure I can provide all
I would like to add that in Ubuntu 18.04 this problem does NOT exist.
However, at the moment I am not able to upgrade to 18.04 because of many
other problems with 18.04 (e.g. printing doesn't work etc etc). These
are not insurmountable problems, but will take some time to fix and then
I should be a
Public bug reported:
I am using Ubuntu 16.04.4 LTS. Since the original release two years ago
it was working absolutely fine on a variety of machines. Now, on this
particular machine I have two monitors:
1. Dell 24" 1200x1920 (portrait) connected via D-SUB/VGA port
2. AOC 28" 1920x1080 (landscape)
Six years later, this is still a problem in Ubuntu 16.04.3:
$ ps -ef | grep cups
root 478 1 0 14:31 ?00:00:00 /usr/sbin/cupsd -l
lp 584 478 0 14:31 ?00:00:00 /usr/lib/cups/notifier/dbus
dbus://
lp 585 478 0 14:31 ?00:00:00 /usr/lib/cups/not
UPDATE: with recent upgrades the problem mentioned in the Subject of
this bug disappeared, i.e. the theme is no longer reset to Ambiance even
when the second monitor is initialised in the wrong resolution.
But the problem of the resolution being dependent on the order of
monitors discovered by BIO
Hi Hans,
Thank you for taking your time to look into this. When you say "I tried
to reproduce this issue on Ubuntu 16.04" you probably mean "Ubuntu
16.04.3", because I also succeeded installing libsndfile1-dev package on
Ubuntu 16.04.3 without any problems. But if you tried on Ubuntu 16.04.2
you w
Could this be related to which monitor was declared by the BIOS to be
"primary"? This guess is based on the fact that it seems to be
unpredictable, i.e. sometimes it boots in the correct resolution (and
the top panel is correct "Radiance") and sometimes in the wrong
resolution (and the top panel is
I may have found a workaround. I looked at my grub.cf and the default
"Ubuntu" entry looked like this:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-ff6d751f-0284-4831-8972-db64642e66a2' {
recordfail
load_video
gfxmode
Public bug reported:
On all my machines with a single monitor this bug is absent, i.e. it is
specific to a dual monitor configuration only.
One of my desktops is connected to a Dell 24" (1200x1920 i.e. portrait
mode, useful for editing source code) via VGA and AOC 28" (1920x1080)
via DVI (btw, I
I would like to mention that if you enable the option "Use transparency
from system theme" then the flickering is even easier to reproduce just
by typing SPACE in gnome-terminal --- you will that the cursor leaves a
shadow/ghost behind itself which disappears after a couple of seconds.
Also, execut
Public bug reported:
Trying to install libsndfile1-dev fails:
$ sudo apt install libsndfile1-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or i
35 matches
Mail list logo
