In order to put this mystery of the "missing directory /usr/share/im-
config/data" to complete rest I would like to say that the reason for it
turned out to be my error. Normally I clone a system by "rsync --delete
-ahvHAX", followed by grub-install with appropriate arguments. But this
time I
Your analysis is absolutely correct. On my system the whole directory
/usr/share/im-config/data was missing. So I did "sudo apt install
--reinstall im-config" as you suggested, and, behold, that directory was
restored, including the two 78* files you mentioned. Then I removed my
"return" at the
This is the version of im-config I am using:
$ apt show im-config
Package: im-config
Version: 0.34-1ubuntu1.3
Priority: optional
Section: x11
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Osamu Aoki
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 360 kB
@Gunnar
1. I am still on Ubuntu 18.04.6. I know it sounds strange, but in the
past 5-6 years I was so busy, that I was upgrading only the components I
actually actively use in my research work, namely Wolfram Mathematica,
python (with all scientific modules) etc. But yes, at some point I will
Ok, the reason I left a comment here was very logical: disabling the
code in /etc/profile.d/input-method-config.sh script made the problem
"go away". And in the header of this script there is a reference to this
particular bug number, so that was my first place to go to.
However, I completely
@Gunnar You are assuming that the bug was fixed completely by the code
in /etc/profile.d/input-method-config.sh. Well, in complex entities,
such as the operating systems (even in user-space level) there is no
such thing as "complete, universal bugfix". There will always be some
subtle cases, which
In my /etc/X11/xinit/xinputrc I have these lines:
# im-config(8) generated on Thu, 09 Aug 2018 08:42:10 +0100
run_im none
# im-config signature: d77e0956ffec112e1184abeaf12847c1 -
And the script /etc/profile.d/input-method-config.sh is causing the
following error message in a X11 level dialog
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
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
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
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]
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
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
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
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 Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1787934
Title:
Checkered
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 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
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
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,
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
22 matches
Mail list logo
