[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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 fine now.

So, it remains a mystery why it was possible to do a simple complete
install resulting in build-essential not installable.

Since I can't reproduce this anymore (I am not going to reinstall with
the option "Download updates while installing") you can close the issue,
if you wish. Or try reproducing it, but then "Download updates while
installing" obviously depends on time, so whatever it was causing a few
days ago it may or may not cause again...

-- 
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 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

** 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 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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 Description
+++-==---=
ii  gcc4:9.3.0-1ubuntu2 amd64GNU C compiler
$ gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ apt policy g++
g++:
  Installed: (none)
  Candidate: 4:9.3.0-1ubuntu2
  Version table:
 4:9.3.0-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

-- 
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 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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.launchpad.net/bugs/1920753

Title:
  Cannot install build-essential on fresh Ubuntu 20.04.2 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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 programs just fine).

Now, the only difference between this install and the one I did in the
morning on the physical SSD is that in the morning I ticked the option
"Download upgrades while installing" (or left it checked). In the VM I
unchecked this box. And also, in the fresh install in the VM I installed
"build-essentials" WITHOUT doing "sudo apt update ; sudo apt upgrade".

So, my guess is that one or both of these two things cause build-
essential breakage:

1. Ticking "Download upgrades during installation" option during install.
2. Doing "sudo apt update ; sudo apt upgrade" BEFORE "sudo apt install 
build-essential"

-- 
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 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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 could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libwxbase3.0-dev : Depends: libc6-dev but it is not going to be installed or
 libc-dev
E: Unable to correct problems, you have held broken packages.

-- 
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 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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 fresh Ubuntu 20.04.2 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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

Title:
  Cannot install build-essential on fresh Ubuntu 20.04.2 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] Re: Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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

Title:
  Cannot install build-essential on fresh Ubuntu 20.04.2 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920753] [NEW] Cannot install build-essential on fresh Ubuntu 20.04.2 installation

[Tigran Aivazian]

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 dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 build-essential : Depends: libc6-dev but it is not going to be installed or
libc-dev
   Depends: g++ (>= 4:9.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

This means that nothing can be compiled, obviously.

Also, g++ cannot be installed either:

$ sudo apt install g++
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 if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 g++ : Depends: g++-9 (>= 9.3.0-3~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
$ gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

** Affects: ubuntu
 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/1920753

Title:
  Cannot install build-essential on fresh Ubuntu 20.04.2 installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1920753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833498] Re: djvulibre mimetype definition is incorrect and not needed

[Tigran Aivazian]

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 leave the comment pointing out the error in their decision to
not support single-page djvu files.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833498

Title:
  djvulibre mimetype definition is incorrect and not needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1833498/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1778088] Re: DjVu Files cannot be opened

[Tigran Aivazian]

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 Files cannot be opened

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1778088/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833498] Re: djvulibre mimetype definition is incorrect and not needed

[Tigran Aivazian]

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 "multipage document manipulation utility" djvm -c
testm.djvu test.djvu, then the resulting file testm.djvu will be
absolutely identical to the original single page test.djvu. Therefore,
it is a serious mistake to consider single-page djvu documents as
"obsolete", as this breaks the functionality with no known workaround
(other than manually editing the evince-backend file). And djview
correctly handles both single and multipage djvu files, so evince should
do as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833498

Title:
  djvulibre mimetype definition is incorrect and not needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/1833498/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833498] Re: Upgrading evince always breaks djvu support

[Tigran Aivazian]

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-gnu/evince/4/backends/djvudocument.evince-backend
file.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833498

Title:
  Upgrading evince always breaks djvu support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833498] Re: Upgrading evince always breaks djvu support

[Tigran Aivazian]

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 normally evince is more convenient.

I thought this bug is well-known because for about a year (or maybe
longer) I saw it mentioned on stackexchange and that is where I learned
about the workaround of adding "image/vnd.djvu" to the end of MimeTypes
in the file /usr/lib/x86_64-linux-gnu/evince/4/backends/djvudocument
.evince-backend.

As for the file example --- just get ANY djvu file from anywhere you like, e.g. 
from my website:
http://www.bibles.org.uk/guardian-plates.html Of course it fails not only with 
the files produced by myself, but with any other djvu files. The error message 
from evince is always "File type DjVu image (image/vnd.djvu) is not supported".

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833498

Title:
  Upgrading evince always breaks djvu support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833498] Re: Upgrading evince always breaks djvu support

[Tigran Aivazian]

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,bionic,now 3.5.27.1-8 all [installed,automatic]
libdjvulibre-text/bionic,bionic,now 3.5.27.1-8 all [installed]
libdjvulibre21/bionic,now 3.5.27.1-8 amd64 [installed]
libminidjvu0/bionic,now 0.8.svn.2010.05.06+dfsg-5build1 amd64 
[installed,automatic]
minidjvu/bionic,now 0.8.svn.2010.05.06+dfsg-5build1 amd64 [installed,automatic]
pdf2djvu/bionic,now 0.9.8-0ubuntu1 amd64 [installed,automatic]

And, following the suggestion on bugs.debian.org I have uninstalled the
package djvulibre-desktop and this solved the problem, i.e. evince can
open djvu files without the "image/vnd.djvu" at the end of MimeTypes in
/usr/lib/x86_64-linux-gnu/evince/4/backends/djvudocument.evince-backend
file.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833498

Title:
  Upgrading evince always breaks djvu support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833498] Re: Upgrading evince always breaks djvu support

[Tigran Aivazian]

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 #1507305
   https://bugzilla.redhat.com/show_bug.cgi?id=1507305

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833498

Title:
  Upgrading evince always breaks djvu support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833498] Re: Upgrading evince always breaks djvu support

[Tigran Aivazian]

Here are the links to the posts where this bug is mentioned:

https://ubuntuforums.org/showthread.php?t=2390953=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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833498

Title:
  Upgrading evince always breaks djvu support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833498] [NEW] Upgrading evince always breaks djvu support

[Tigran Aivazian]

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 unable to view djvu files. Please add "image/vnd.djvu" to
MimeType in the official version of this file so that I (and presumably
all other millions of Ubuntu Linux users, who are too lazy to open a
bugreport for it) don't have to edit it manually. Thank you.

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  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 unable to view djvu files. Please add "image/vnd.djvu" to
  MimeType in the official version of this file so that I (and presumably
- all other millions of Ubuntu Linux, who are too lazy to open a bugreport
- for it) don't have to edit it manually. Thank you.
+ all other millions of Ubuntu Linux users, who are too lazy to open a
+ bugreport for it) don't have to edit it manually. Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833498

Title:
  Upgrading evince always breaks djvu support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787934] Re: Checkered background in a screenshot

[Tigran Aivazian]

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 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1787934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787934] [NEW] Checkered background in a screenshot

[Tigran Aivazian]

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

** Attachment added: "init-attach-kill.png"
   
https://bugs.launchpad.net/bugs/1787934/+attachment/5177954/+files/init-attach-kill.png

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1787934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787934] Re: Checkered background in a screenshot

[Tigran Aivazian]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1787934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783321] Re: Stellarium crashes 15 seconds after starting up

[Tigran Aivazian]

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 this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783321

Title:
  Stellarium crashes 15 seconds after starting up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stellarium/+bug/1783321/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783321] [NEW] Stellarium crashes 15 seconds after starting up

[Tigran Aivazian]

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/ - server replied: 
Forbidden"
[Exoplanets] Starting update...
terminate called after throwing an instance of 'std::runtime_error'
  what():  illegal value
Aborted

$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

$ apt-cache policy stellarium
stellarium:
  Installed: 0.18.0-1
  Candidate: 0.18.0-1
  Version table:
 *** 0.18.0-1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: stellarium (Ubuntu)
 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/1783321

Title:
  Stellarium crashes 15 seconds after starting up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stellarium/+bug/1783321/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780449] Re: [regression] i965 graphics corruption after recent xenial updates

[Tigran Aivazian]

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 the information you require
manually. What else do you need to see, other than lspci -vvx and
Xorg.0.log which I have provided already?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780449

Title:
  [regression] i965 graphics corruption after recent xenial updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780449/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780449] Re: Dual monitor system unusable after xorg+mesa upgrade

[Tigran Aivazian]

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 able to just move to Ubuntu 18.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780449

Title:
  Dual monitor system unusable after xorg+mesa upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1780449/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780449] [NEW] Dual monitor system unusable after xorg+mesa upgrade

[Tigran Aivazian]

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) connected via DVI-D

I have made an upgrade today and the following packages were upgraded:

https://paste.ubuntu.com/p/5cf8hq6JQK/

Note that the list includes mesa libraries and xserver-xorg* packages
which are most suspect.

Here is my /var/log/Xorg.0.log:

https://paste.ubuntu.com/p/tB6yGhDT2S/

Here is the output of "sudo lspci -vvx":

https://paste.ubuntu.com/p/VVctSFwFSm/

As you can see, there is nothing special about this machine: a pretty
vanilla desktop with i5-3570K cpus (NOT overclocked!) and 16GB RAM. Oh,
I forgot to say what actually happens and why the system is unusable:
even if I create a single gnome-terminal window (say on the Dell
monitor) after a couple of seconds (of typing in the terminal) large
size rectangles appear on the other monitor. And if I start Chrome (on a
monitor different from the one gnome-terminal is running on) then bits
of the terminal sometimes appear on one of Chrome's tabs and vice versa,
i.e. bits (rectangular shape) of Chrome's tabs appear on the terminal.
Sometimes the content of the terminal gets corrupted. And all this
happens reasonably quickly (on the order of 5-10 seconds), which means
you can't do any work at all. Also, creating other windows (I started
pavucontrol in the background) makes the mess even worse, i.e. they all
keep overwriting each other's rendering context.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: xorg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780449

Title:
  Dual monitor system unusable after xorg+mesa upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1780449/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 959195] Re: 65 cups notifier processes running

[Tigran Aivazian]

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/notifier/dbus 
dbus://
lp 586   478  0 14:31 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp 587   478  0 14:31 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp 588   478  0 14:31 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp 589   478  0 14:31 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp 590   478  0 14:31 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
tigran2017  1330  0 14:36 pts/900:00:00 grep --color=auto cups

I followed the suggestion in comment #4 and it got rid of the notifier
processes BUT in a short time (a day or two) they came back, about one
or two processes a day. So, the fix does not appear to be working.

Note that this is not just plain "indicator-printers" setup --- I am
running HP notifier "hp-systray" which is part HPLIP (without it my
printer wouldn't work as it is a "windows only" printer LaserJet Pro
M102a).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959195

Title:
  65 cups notifier processes running

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/959195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736723] Re: GTK Theme is reset to Ambience on almost every reboot

[Tigran Aivazian]

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 BIOS (or by Linux?) still remains. To fix this I
run the script shown in my first comment above.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736723

Title:
  GTK Theme is reset to Ambience on almost every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1736723/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1731792] Re: Can't install libsndfile1-dev on Ubuntu 16.04.2 x86_64

[Tigran Aivazian]

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 would have faced the same problem.

I opened this bug more than a month ago and since then I have upgraded
all my systems from 16.04.2 to 16.04.3 so I can't try running `apt
policy libsndfile1-dev` as you suggest. And since 16.04.2 is not
supported and everything works fine on 16.04.3, I suppose we can close
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/1731792

Title:
  Can't install libsndfile1-dev on Ubuntu 16.04.2 x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1731792/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736723] Re: GTK Theme is reset to Ambience on almost every reboot

[Tigran Aivazian]

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 reset back to "Ambiance").

There are settings in the BIOS for this but they use strange
abbreviations like IGFX and I don't know what these abbreviations mean.
(I'll try to use Google Internet Search engine and see, maybe that will
be of help, though I doubt it --- Google is all about ads and business,
and not about real knowledge).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736723

Title:
  GTK Theme is reset to Ambience on almost every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1736723/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736723] Re: GTK Theme is reset to Ambience on almost every reboot

[Tigran Aivazian]

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 $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  
ff6d751f-0284-4831-8972-db64642e66a2
else
  search --no-floppy --fs-uuid --set=root 
ff6d751f-0284-4831-8972-db64642e66a2
fi
linux   /boot/vmlinuz-4.10.0-40-generic rootfstype=ext4 root=/dev/sda1 
ro  quiet
initrd  /boot/initrd.img-4.10.0-40-generic
}

I decided that most of the above code is "unnecessary junk" ;) and
reduced it to the following nice and compact entry:

menuentry 'Test' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-ff6d751f-0284-4831-8972-db64642e66a2' {
insmod gzio
insmod part_msdos
insmod ext2
linux   /boot/vmlinuz-4.10.0-40-generic rootfstype=ext4 root=/dev/sda1 ro 
quiet
initrd  /boot/initrd.img-4.10.0-40-generic
}

In the old days I would get rid of initrd as well, but nowadays things
got a little bit more complicated, so I left it there (it would save
only about 1/3 of a second on boot and it is already very fast at less
than 2.5 seconds).

Anyway, the "Test" entry boots absolutely fine and, most importantly,
the Dell monitor is now always at 1920x1200 resolution which means the
top panel in Unity is NOT reset to Ambiance. It stays light, i.e.
remains in the Radiance theme.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736723

Title:
  GTK Theme is reset to Ambience on almost every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1736723/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736723] [NEW] GTK Theme is reset to Ambience on almost every reboot

[Tigran Aivazian]

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 noticed that xrandr says it is connected via HDMI ---
this desktop doesn't even have an HDMI port, only DVI and VGA!). The
Dell monitor is quite old, but of extremely high quality, which is why I
still keep it. Now, being so old, in the last couple of months it has
developed the following symptom: it would boot into 1024x768 (or
768x1024 to be pedantically exact) resolution and as soon as I login to
unity session I would execute a script "fix-resolution.sh" which
contains the following three commands:

xrandr --newmode "1920x1200_60.00" 193.16 1920 2048 2256 2592 1200 1201 1204 
1242 -HSync +Vsync
xrandr --addmode VGA-1 "1920x1200_60.00"
xrandr --output VGA-1 --mode "1920x1200_60.00"

This would fix the resolution and I would continue working normally.
However, even though I previously set the Theme (both GTK Theme and
Window decoration theme in unity-tweak-tool) to "Radiance", the top
panel becomes dark, i.e. as in Ambience. But the window decorations are
light, i.e. as they should be in the "Radiance" theme.

Why did I mention the resolution switch issue above? Because I noticed,
that when the computer boots with the Dell monitor in the correct
resolution (by luck, i.e. maybe EDID info from the monitor gets through
to the OS side?) then the top panel is correct, i.e. light as in
Radiance.

The Ubuntu version is 16.04.3:

$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04
$ unity --version
unity 7.4.0
$ uname -a
Linux brave 4.10.0-40-generic #44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

Any ideas on how to fix the GTK Theme to Radiance? I tried setting it
via System Settings/Appearance and via unity-tweak-tool and even via
gnome-tweak-tool. None of the methods is sufficient to force the theme
to remain set to Radiance.

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: gnome-terminal (Ubuntu) => unity (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736723

Title:
  GTK Theme is reset to Ambience on almost every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1736723/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726262] Re: 17.10 - flickering overlay patterns in gnome-terminal

[Tigran Aivazian]

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, executing "ls -l" (in a non-empty directory :) you will see that
as the output scrolls up it leaves a shadow ghost which disappears only
after a few seconds.

This was so EXTREMELY annoying (imagine editing source code in vim and
going mad because of these shadow blocks of code :) that I even thought
of reverting back to 16.04, but fortunately I found this bug report
which provided the workaround to disable "Use transparency from system
theme" which works fine. Thank you!

Oh and yes, this only happens on the second/external monitor connected
via VGA.

Btw, there is another annoying bug here --- when the mouse is on some
areas of the main monitor another duplicate mouse pointer is visible and
moving around on the second monitor. My second monitor is in portrait,
so this "extra" mouse pointer is moving in the perpendicular dimension
which is distracting But I guess this belongs to a separate bug
report.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726262

Title:
  17.10 - flickering overlay patterns in gnome-terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1731792] [NEW] Can't install libsndfile1-dev on Ubuntu 16.04.2 x86_64

[Tigran Aivazian]

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 if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libsndfile1-dev : Depends: libsndfile1 (= 1.0.25-10) but 
1.0.25-10ubuntu0.16.04.1 is to be installed
E: Unable to correct problems, you have held broken packages.

The reason is seen by running apt show -a libsndfile:

$ apt show -a libsndfile1
Package: libsndfile1
Version: 1.0.25-10ubuntu0.16.04.1
Status: install ok installed
Priority: optional
Section: libs
Source: libsndfile
Maintainer: Ubuntu Developers 
Original-Maintainer: Erik de Castro Lopo 
Installed-Size: 510 kB
Depends: libc6 (>= 2.14), libflac8 (>= 1.3.0), libvorbisenc2 (>= 1.1.2)
Homepage: http://www.mega-nerd.com/libsndfile/
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: Library for reading/writing audio files
 libsndfile is a library of C routines for reading and writing files
 containing sampled audio data.
 .
 Various versions of WAV (integer, floating point, GSM, and compressed
 formats); Microsoft PCM, A-law and u-law formats; AIFF, AIFC and RIFX;
 various AU/SND formats (Sun/NeXT, Dec AU, G721 and G723 ADPCM); RAW
 header-less PCM files; Amiga IFF/8SVX/16SV PCM files; Ensoniq PARIS
 (.PAF); Apple's Core Audio Format (CAF) and others.

Package: libsndfile1
Version: 1.0.25-10
Priority: optional
Section: libs
Source: libsndfile
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Erik de Castro Lopo 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 511 kB
Depends: libc6 (>= 2.14), libflac8 (>= 1.3.0), libvorbisenc2 (>= 1.1.2)
Homepage: http://www.mega-nerd.com/libsndfile/
Task: virt-host, ubuntu-desktop, ubuntu-usb, kubuntu-desktop, edubuntu-desktop, 
edubuntu-usb, xubuntu-core, xubuntu-desktop, mythbuntu-frontend, 
mythbuntu-desktop, mythbuntu-backend-slave, mythbuntu-backend-master, 
lubuntu-desktop, ubuntustudio-video, ubuntustudio-audio, ubuntu-gnome-desktop, 
ubuntu-sdk-libs, ubuntu-touch, ubuntukylin-desktop, ubuntu-mate-core, 
ubuntu-mate-desktop, ubuntu-mate-cloudtop
Supported: 5y
Download-Size: 137 kB
APT-Sources: http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Description: Library for reading/writing audio files
 libsndfile is a library of C routines for reading and writing files
 containing sampled audio data.
 .
 Various versions of WAV (integer, floating point, GSM, and compressed
 formats); Microsoft PCM, A-law and u-law formats; AIFF, AIFC and RIFX;
 various AU/SND formats (Sun/NeXT, Dec AU, G721 and G723 ADPCM); RAW
 header-less PCM files; Amiga IFF/8SVX/16SV PCM files; Ensoniq PARIS
 (.PAF); Apple's Core Audio Format (CAF) and others.


$ lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04

What do I do now? I opened an issue with libsndfile maintainer here:

https://github.com/erikd/libsndfile/issues/337

But he closed it referring me here.

** Affects: libsndfile (Ubuntu)
 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/1731792

Title:
  Can't install libsndfile1-dev on Ubuntu 16.04.2 x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1731792/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs