[Desktop-packages] [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 Desktop
Packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1861340

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

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  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?)

  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

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1861340

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

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  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?)

  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

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1861340

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

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  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?)

  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

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1861340

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

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  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?)

  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

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1861340

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

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  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:
  

[Desktop-packages] [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 Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1861340

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

Status in fontconfig package in Ubuntu:
  New

Bug description:
  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.)

  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

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1587154

Title:
  --working-directory does not work anymore

Status in gnome-terminal package in Ubuntu:
  Fix Released

Bug description:
  
  After upgrading from ubuntu 14.04 to 16.04 one of my script the uses 
--working-directory option stopped working.

  Simply running:

  gnome-terminal --working-directory=/tmp

  Starts the terminal in my home directory. Changing the command to
  gnome-terminal.real does not solve my problem either.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1587154

Title:
  --working-directory does not work anymore

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  
  After upgrading from ubuntu 14.04 to 16.04 one of my script the uses 
--working-directory option stopped working.

  Simply running:

  gnome-terminal --working-directory=/tmp

  Starts the terminal in my home directory. Changing the command to
  gnome-terminal.real does not solve my problem either.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1587154

Title:
  --working-directory does not work anymore

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  
  After upgrading from ubuntu 14.04 to 16.04 one of my script the uses 
--working-directory option stopped working.

  Simply running:

  gnome-terminal --working-directory=/tmp

  Starts the terminal in my home directory. Changing the command to
  gnome-terminal.real does not solve my problem either.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1587154

Title:
  --working-directory does not work anymore

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  
  After upgrading from ubuntu 14.04 to 16.04 one of my script the uses 
--working-directory option stopped working.

  Simply running:

  gnome-terminal --working-directory=/tmp

  Starts the terminal in my home directory. Changing the command to
  gnome-terminal.real does not solve my problem either.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1563155

Title:
  No Application Data Found

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I installed ubuntu 16.04 and when I go to the gnome software, it says
  "No Application Data Found". It is all greyed out and no apps are
  available for download.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1563155

Title:
  No Application Data Found

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I installed ubuntu 16.04 and when I go to the gnome software, it says
  "No Application Data Found". It is all greyed out and no apps are
  available for download.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1559308

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1559308

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1559308

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1559308

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

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

-- 
Mailing list: