[Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-12 Thread Jonathan Hartley
For others with similar problems, I'm keeping my findings up to date
here: https://www.tartley.com/dina-as-otf

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

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

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

[Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-05 Thread Jonathan Hartley
I succeeded with the process of converting a bitmap font into a vector
format with embedded bitmaps, which Pango will display. It took me hours
to figure out, so for anyone else:

Use fontforge, as described here:
https://gitlab.gnome.org/GNOME/pango/issues/386#note_570411

The gotcha is that once you've installed the resulting font, then it
displays invisibly in font selection dialogs. However, don't give up
there! If you click around blindly to select the font you want, then the
font displays correctly in gnome-terminal, including all size
variations, with bold and italic variants.

There is some residual weirdness in that selecting a font size that is
not defined in the bitmap (e.g. when using 'ctrl-+'), the terminal goes
completely blank instead of falling back to another font.

For me, using fonttosfnt, as also described in that thread, had many
serious issues (eg the resulting font only preserved the bitmap's
smallest size variant)

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

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

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

[Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-03 Thread Jonathan Hartley
Thanks for talking me through it Sebastien. Fair enough, I defer to your
experience on that.

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

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

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

[Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-02 Thread Jonathan Hartley
I don't think 'fix released' is the right status.

Could Focal use a slightly older version of Pango, to keep bitmap fonts
working for another 6 months, hoping it becomes clearer how to continue
supporting them going forward?

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

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

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

[Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-01-31 Thread Jonathan Hartley
I'm speculating that pango 1.44 dropping support for bitmap fonts might
be a cause: https://gitlab.gnome.org/GNOME/pango/issues/386

** Package changed: fontconfig (Ubuntu) => pango1.0 (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/pango/issues #386
   https://gitlab.gnome.org/GNOME/pango/issues/386

** Description changed:

  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.
  
  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7
  
  I have always installed it using a script:
  
  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip
  
  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf
  
  # rebuild the cache
  fc-cache -f -v
  
  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"
  
  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.
  
  I installed Focal today, using `sudo do-release-upgrade -d`.
  
  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)
  
- I cannot run 'gnome-font-viewer' to check things out, presumably due to some 
variant of:
+ ~~I cannot run 'gnome-font-viewer' to check things out, presumably due to 
some variant of:
  https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819
- (the window displays but immediately locks up.)
+ (the window displays but immediately locks up.)~~
+ UPDATE: gnome-font-viewer runs fine today. All bitmap fonts are not present.
  
  While trying to find a fix, I tried a few changes to the above script,
  which did not help:
  
  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:
  
  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )
  
    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

** Description changed:

  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.
  
  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7
  
  I have always installed it using a script:
  
  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip
  
  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf
  
  # rebuild the cache
  fc-cache -f -v
  
  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"
  
  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.
  
  I installed Focal today, using `sudo do-release-upgrade -d`.
  
  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)
  
- ~~I cannot run 'gnome-font-viewer' to check things out, presumably due to 
some variant of:
- https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819
- (the window displays but immediately locks up.)~~
- UPDATE: gnome-font-viewer runs fine today. All bitmap fonts are not present.
+ gnome-font-viewer does not list any of the installed bitmap fonts.
  
  While trying to find a fix, I tried a few changes to the above script,
  which did not help:
  
  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:
  
  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )
  
    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1861340/+subscriptions

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

[Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-01-31 Thread Jonathan Hartley
I semi-guessed at package 'fontconfig' to associate. Advice welcome.

** Package changed: ubuntu => fontconfig (Ubuntu)

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

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

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

[Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-01-31 Thread Jonathan Hartley
** Summary changed:

- All bitmap fonts no longer visible on upgrade 19.10 -> Focal (development)
+ All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

** Description changed:

  For years I've installed a bitmap font for my terminals, but since I
- upgraded to Focal (development branch) today, it no longer works.
+ upgraded to Focal (development branch) today, it (and other bitmap
+ fonts) no longer work.
  
  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7
  
  I have always installed it using a script:
  
- # install dina
- sudo mkdir -p /usr/share/fonts/Dina
- cd /usr/share/fonts/Dina
- sudo unzip ~/Downloads/Dina.zip
- 
- # enable bitmap fonts
- sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf
- 
- # rebuild the cache
- fc-cache -f -v
- 
- # Set as default mono font
- gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"
-
+ # install dina
+ sudo mkdir -p /usr/share/fonts/Dina
+ cd /usr/share/fonts/Dina
+ sudo unzip ~/Downloads/Dina.zip
+ 
+ # enable bitmap fonts
+ sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf
+ 
+ # rebuild the cache
+ fc-cache -f -v
+ 
+ # Set as default mono font
+ gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"
  
  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.
  
  I installed Focal today, using `sudo do-release-upgrade -d`.
  
  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)
  
  I cannot run 'gnome-font-viewer' to check things out, presumably due to some 
variant of:
  https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819
  (the window displays but immediately locks up.)
  
  While trying to find a fix, I tried a few changes to the above script,
  which did not help:
  
  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:
  
- (
- cd /etc/fonts/conf.d
- sudo rm -f 70-no-bitmaps.conf
- sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
- )
+ (
+ cd /etc/fonts/conf.d
+ sudo rm -f 70-no-bitmaps.conf
+ sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
+ )
  
-   (tried with both 'yes-bitmaps' and 'force-bitmaps')
+   (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

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

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

[Bug 1861340] Re: Bitmap fonts no longer visible on upgrade 19.10 -> Focal (development)

2020-01-31 Thread Jonathan Hartley
I can see the installed bitmap fonts with fc-list:

$ fc-list | grep dina
/usr/share/fonts/bitmap/dina/Dina_r400-9.bdf: Dina:style=Regular
/usr/share/fonts/bitmap/dina/Dina_r400-8.bdf: Dina:style=Regular
[... etc]


** Summary changed:

- Bitmap font no longer useable on upgrade 19.10 -> Focal (development)
+ Bitmap fonts no longer visible on upgrade 19.10 -> Focal (development)

** Summary changed:

- Bitmap fonts no longer visible on upgrade 19.10 -> Focal (development)
+ All bitmap fonts no longer visible on upgrade 19.10 -> Focal (development)

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

Title:
  All bitmap fonts no longer visible on upgrade 19.10 -> Focal
  (development)

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

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

[Bug 1861340] Re: Bitmap font no longer useable on upgrade 19.10 -> Focal (development)

2020-01-30 Thread Jonathan Hartley
I have the same problem with other bitmaps fonts, such as those at
https://github.com/Tecate/bitmap-fonts. They appear to install fine,
"fc-cache" reports finding them, but they are not visible in font
selection dialogs.

`sudo dpkg-reconfigure fontconfig` does not help.

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

Title:
  Bitmap font no longer useable on upgrade 19.10 -> Focal (development)

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

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

[Bug 1861340] [NEW] Bitmap font no longer useable on upgrade 19.10 -> Focal (development)

2020-01-29 Thread Jonathan Hartley
Public bug reported:

For years I've installed a bitmap font for my terminals, but since I
upgraded to Focal (development branch) today, it no longer works.

The font is 'Dina', from here:
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7

I have always installed it using a script:

# install dina
sudo mkdir -p /usr/share/fonts/Dina
cd /usr/share/fonts/Dina
sudo unzip ~/Downloads/Dina.zip

# enable bitmap fonts
sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf

# rebuild the cache
fc-cache -f -v

# Set as default mono font
gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"
   

This has always worked in the past, through many versions of Ubuntu,
including 19.10.

I installed Focal today, using `sudo do-release-upgrade -d`.

Now the above script does not make Dina visible in font selectors such
as that produced by the Tweaks / Fonts / [Monospace Text] button.
Terminals that were previously configured to use that font now display
the "box of hex digits" characters (what are they called?)

I cannot run 'gnome-font-viewer' to check things out, presumably due to some 
variant of:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819
(the window displays but immediately locks up.)

While trying to find a fix, I tried a few changes to the above script,
which did not help:

* Unzip to "$HOME/.fonts" instead
* Trying other symlinks in the fonts config.d:

(
cd /etc/fonts/conf.d
sudo rm -f 70-no-bitmaps.conf
sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
)

  (tried with both 'yes-bitmaps' and 'force-bitmaps')
* fc-cache -r # "really" force cache re-creation

** 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/1861340

Title:
  Bitmap font no longer useable on upgrade 19.10 -> Focal (development)

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

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

[Bug 1587154] Re: --working-directory does not work anymore

2019-11-21 Thread Jonathan Hartley
Works for me now too, for both absolute and relative paths (gnome-
terminal 3.34.2)

Marking as complete.

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  --working-directory does not work anymore

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

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

[Bug 1682820] Re: While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-14 Thread Jonathan Hartley
Apologies, the comment above should have read:

$ sudo apt install synaptic
[sudo] password for jhartley:
Reading package lists... Done
Building dependency tree   
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies.
 python3 : PreDepends: python3-minimal (= 3.5.1-4) but 3.5.3-1 is to be 
installed
   Depends: libpython3-stdlib (= 3.5.1-4) but 3.5.3-1 is to be installed
 python3-dev : Depends: python3 (= 3.5.3-1) but 3.5.1-4 is to be installed
 synaptic : Depends: libept1.5.0 but it is not going to be installed
Recommends: rarian-compat but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

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

Title:
  While upgrading to 17.04: package python3 3.5.1-4 failed to
  install/upgrade: pre-dependency problem - not installing python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1682820/+subscriptions

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


[Bug 1682820] Re: While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-14 Thread Jonathan Hartley
Other potentially useful apt commands also fail with the same error:

apt --fix-broken install
apt autoremove

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

Title:
  While upgrading to 17.04: package python3 3.5.1-4 failed to
  install/upgrade: pre-dependency problem - not installing python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1682820/+subscriptions

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


[Bug 1682820] Re: While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-14 Thread Jonathan Hartley
I can't install synaptic, or anything else, because 'apt' fails to run,
with:

$ apt-cache policy python3-minimal
python3-minimal:
  Installed: 3.5.3-1
  Candidate: 3.5.3-1
  Version table:
 *** 3.5.3-1 500
500 http://gb.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status


Is there another way I can do the cleaning?

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

Title:
  While upgrading to 17.04: package python3 3.5.1-4 failed to
  install/upgrade: pre-dependency problem - not installing python3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1682820/+subscriptions

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


[Bug 1682820] [NEW] While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-14 Thread Jonathan Hartley
Public bug reported:

I got this error while upgrading from 16.10 to 17.04, along with the
same Python traceback as below. After a reboot, I seem to now be on
17.04.

I had just successfully upgraded from 16.04 to 16.10 with no problems.

When the error occurred, I was advised by a dialog to try the following
command, which produced a very similar error, with traceback.

$ sudo apt-get install -f
[sudo] password for jhartley: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  account-plugin-tools account-plugin-ubuntuone cgmanager comerr-dev
  dns-root-data dnsmasq-base gdebi-core gir1.2-accounts-1.0 gir1.2-signon-1.0
  hwdata imagemagick-common krb5-multidev libavcodec-ffmpeg-extra56
  libavfilter-ffmpeg5 libavformat-ffmpeg56 libavresample-ffmpeg2
  libavutil-ffmpeg54 libbasicusageenvironment1 libbluray1 libbonobo2-0
  libbonobo2-common libbonoboui2-0 libbonoboui2-common
  libboost-date-time1.61.0 libboost-filesystem1.61.0 libboost-iostreams1.61.0
  libboost-locale1.61.0 libboost-log1.61.0 libboost-program-options1.61.0
  libboost-regex1.61.0 libboost-serialization1.61.0 libboost-thread1.61.0
  libcddb2 libchromaprint0 libdirectfb-1.2-9 libdvbpsi10 libebml4v5 libfwup0
  libglade2-0 libglew1.13 libgnome-2-0 libgnome2-0 libgnome2-bin
  libgnome2-common libgnomecanvas2-0 libgnomecanvas2-common libgnomeui-0
  libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgroupsock8
  libgssrpc4 libiso9660-8 libjasper1 libjson-c3:i386 libjsoncpp1
  libkadm5clnt-mit10 libkadm5clnt-mit11 libkadm5srv-mit10 libkadm5srv-mit11
  libkdb5-8 liblircclient0 liblivemedia52 liblivemedia57 libllvm3.8
  libllvm3.8:i386 liblouis10 libmatroska6v5 libmimic0 libmircommon6
  libmirplatform13 libmirserver41 libonig2 libopencv-contrib2.4v5
  libopencv-legacy2.4v5 libopencv-ml2.4v5 libopenjpeg5 libopenmpt-modplug1
  liborbit-2-0 liborcus-0.11-0 libpam-cgfs libpay2 libperl5.22 libpoppler61
  libpostproc-ffmpeg53 libraw15 libreoffice-style-human libresid-builder0c2a
  libsidplay2v5 libswresample-ffmpeg1 libswscale-ffmpeg3 libubuntu-app-launch3
  libubuntuoneauth-2.0-0 libupnp6 libusageenvironment3 libvcdinfo0 libvlc-bin
  libvlc5 libvpx3 libwebp5 libx265-79 libx86-1 libxapian22v5
  linux-image-4.4.0-72-generic linux-image-extra-4.4.0-72-generic lp-solve
  mir-platform-graphics-mesa-kms10 mir-platform-graphics-mesa-x10
  mir-platform-input-evdev5 oxygen5-icon-theme pay-service pay-ui
  perl-modules-5.22 pm-utils qml-module-ubuntuone
  qtdeclarative5-ubuntu-web-plugin snap-confine system-config-printer-gnome
  ubuntu-push-client ubuntuone-credentials-common unity-scope-click vbetool
  vlc-bin vlc-data vlc-nox vlc-plugin-base
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  python3
Suggested packages:
  python3-doc python3-tk python3-venv
The following packages will be upgraded:
  python3
1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
12 not fully installed or removed.
Need to get 0 B/8,696 B of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up python3.5-minimal (3.5.3-1) ...
Traceback (most recent call last):
  File "/usr/lib/python3.5/py_compile.py", line 6, in 
import importlib._bootstrap_external
  File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
import types
  File "/usr/lib/python3.5/types.py", line 166, in 
import functools as _functools
  File "/usr/lib/python3.5/functools.py", line 23, in 
from weakref import WeakKeyDictionary
  File "/usr/lib/python3.5/weakref.py", line 12, in 
from _weakref import (
ImportError: cannot import name '_remove_dead_weakref'
dpkg: error processing package python3.5-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3-minimal:
 python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
  Package python3.5-minimal is not configured yet.

dpkg: error processing package python3-minimal (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up 
error from a previous failure.
Errors were encountered while processing:
 python3.5-minimal
 python3-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)


And, FWIW:

$ apt-cache policy python3-minimal
python3-minimal:
  Installed: 3.5.3-1
  Candidate: 3.5.3-1
  Version table:
 *** 3.5.3-1 500
500 http://gb.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3 3.5.1-4
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64

[Bug 1587154] Re: --working-directory does not work anymore

2016-09-27 Thread Jonathan Hartley
Apologies if this is a dumb question but does Daniel Alves 'no longer
affects' annotation mean that this bug has been fixed in trunk/master,
and we should expect a release at some point? Or something else? Thanks
for helping me understand the process.

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

Title:
  --working-directory does not work anymore

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

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


[Bug 1587154] Re: --working-directory does not work anymore

2016-09-14 Thread Jonathan Hartley
...and I'm using
$ gnome-terminal --version
GNOME Terminal 3.18.3
(in Ubuntu 16.04)

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

Title:
  --working-directory does not work anymore

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

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


[Bug 1587154] Re: --working-directory does not work anymore

2016-09-14 Thread Jonathan Hartley
This problem manifests for me if I modify my gnome-terminal profile to
start a custom command (e.g. '/bin/bash')

If I uncheck that option in the profile, to run the my default shell
instead, then --working-directory=/ works fine.

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

Title:
  --working-directory does not work anymore

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

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


[Bug 1563155] Re: No Application Data Found

2016-05-03 Thread Jonathan Hartley
$ sudo appstreamcli refresh --force --verbose
[sudo] password for jhartley: 
** (appstreamcli:3435): DEBUG: Refreshing AppStream cache
** (appstreamcli:3435): DEBUG: Reading: 
/usr/share/app-info/xmls/org.freedesktop.fwupd.xml
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_main_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-updates_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-security_main_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-security_restricted_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-security_universe_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: 
/var/lib/app-info/yaml/archive.ubuntu.com_ubuntu_dists_xenial-security_multiverse_dep11_Components-amd64.yml.gz
** (appstreamcli:3435): DEBUG: Reading: /var/cache/app-info/xmls/fwupd.xml
** (appstreamcli:3435): DEBUG: Detected colliding ids: plan.desktop was already 
added with the same priority.
** (appstreamcli:3435): DEBUG: Detected colliding ids: flcheckers.desktop was 
already added with the same priority.
** (appstreamcli:3435): DEBUG: Detected colliding ids: flblocks.desktop was 
already added with the same priority.
** (appstreamcli:3435): DEBUG: Detected colliding ids: flsudoku.desktop was 
already added with the same priority.
** (appstreamcli:3435): DEBUG: Replaced 'language-selector.desktop' with data 
of higher priority.
** (appstreamcli:3435): DEBUG: zathura-pdf-poppler.desktop extends 
zathura.desktop, but zathura.desktop was not found.
** (appstreamcli:3435): DEBUG: WARNING: Skipped component 
'com.steelseries.rival-legacy.firmware': The component is invalid.
** (appstreamcli:3435): DEBUG: Removing old rebuild-dir from previous database 
rebuild.
AppStream cache update completed, but some metadata was ignored due to errors.
22:14:53:~
$ appstreamcli status
AppStream Status:
Version: 0.9.4

Distribution metadata:
 /usr/share/app-info
  - XML:  1
  - No icons.

 /var/lib/app-info
  - YAML: 12
  - Iconsets:
 ubuntu-xenial-main
 ubuntu-xenial-universe
 ubuntu-xenial-multiverse
 ubuntu-xenial-updates-main

 /var/cache/app-info
  - XML:  1
  - No icons.

Upstream metadata:
  - Found 50 components in legacy paths.

Summary:
The system metadata cache exists.
We have information on 1822 software components.

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

Title:
  No Application Data Found

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

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


[Bug 1563155] Re: No Application Data Found

2016-05-03 Thread Jonathan Hartley
Holy carp! Ignore my lengthy post above: The issue is now fixed for me!
Ubuntu Software window is now full of things!

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

Title:
  No Application Data Found

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

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


[Bug 1559308] Re: Plugging HDMI screen in causes system hang

2016-04-28 Thread Jonathan Hartley
I reported earlier that the crash only happens for me when I move the
mouse pointer from my external monitor to the laptop primary display. I
just reproduced again when moving the mouse pointer the other way: It
was fine with the mouse cursor on the laptop primary display for a while
(2 minutes, while using the machine normally) then crashed immediately
the first time I moved the mouse to the external monitor.

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

Title:
  Plugging HDMI screen in causes system hang

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

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


[Bug 1559308] Re: Plugging HDMI screen in causes system hang

2016-04-28 Thread Jonathan Hartley
@Scott: This bug only started happening for me when I upgraded from
15.10 to 16.04. You could try installing 15.10 and maybe it will be fine
for you, and you can use that until a fix appears.

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

Title:
  Plugging HDMI screen in causes system hang

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

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


[Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus

2016-04-28 Thread Jonathan Hartley
@shinyblue: Very nice work.

Does the ticket title need updating to reflect it isn't just Nvidia
drivers?

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

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers on a laptop with Optimus

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

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


[Bug 1559308] Re: Plugging HDMI screen in causes system hang

2016-04-28 Thread Jonathan Hartley
It crosses my mind that as well as the HDMI output, my laptop also has a
mini display port. Does anyone have a feel for whether it's worth buying
an mini display port adaptor or cable to test whether that behaves the
same?

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

Title:
  Plugging HDMI screen in causes system hang

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

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


[Bug 1559308] Re: Plugging HDMI screen in causes system hang

2016-04-27 Thread Jonathan Hartley
If I have an external monitor, then I get a crash when when I move my
mouse cursor on to the primary (laptop) display. I get the same
traceback in my syslog as that posted above by @shinyblue.

My graphics card is the integrated Intel HD Graphics 520 Mobile, i5
6200U, using driver i915_bpo.

My whole system crashes, not just X - I cannot ctrl-alt-f1 to get to
virtual terminals. I have to hold down the power button to recover.

During login, both displays work fine. If I keep my mouse cursor on the
external monitor, everything is fine. With no external monitor,
everything is fine.

This just started when I upgraded to Ubuntu 16.04. On 15.10, everything
was fine.

Lenovo Thinkpad T460, Ubu Intel HD Graphics 520 Mobile, i5 6200U, driver
i915_bpo, Ubuntu 16.04.

There are a few people with the same problem here:
http://askubuntu.com/questions/762373/laptop-freezes-after-connecting-
external-monitor-since-16-04-update

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

Title:
  Plugging HDMI screen in causes system hang

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

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


[Bug 1290847] Re: pyvenv fails due to mising ensurepip module

2014-06-09 Thread Jonathan Hartley
Apologies for the noise but also: Thanks for working on a thoughtfully-
derived correct fix.

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

Title:
  pyvenv fails due to mising ensurepip module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions

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


[Bug 210738] Re: Printing GUI does not open

2008-10-28 Thread Jonathan Hartley
I had the same problem, it was caused because I had installed python2.6.
Removing the 'python' executable from /usr/local/bin (leaving only the
identical python2.6 executable) fixed it, since 'python' now refers to
the default ubuntu /usr/bin/python2.5.

-- 
Printing GUI does not open
https://bugs.launchpad.net/bugs/210738
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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