[Desktop-packages] [Bug 1741928] Re: Automatic time zone not working

2018-01-09 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => Confirmed

** Changed in: gnome-control-center
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1741928

Title:
  Automatic time zone not working

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  I have just arrived to Singapore from Spain, and the automatic time zone 
setting in gnome shell is not having any effect.
  I will keep it as is for 1 or 2 days before forcing it manually, but it'd be 
nice for an advertised feature to work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 17:29:46 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-25 (1870 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1741928/+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 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

2018-01-09 Thread RégisC
> Do you have a keyboard backlight at all? Or an external keyboard
plugged in?

Yes my keyboard has some automatic backlight

> What does your journalctl output say after that? Can you paste it
here?

Will attach the full output, I think the culprit is:

janv. 10 07:54:48 hephaistos gnome-session[2639]: gnome-session-binary[2639]: 
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de 
l’appel de StartServiceByName pour org.gnome.ScreenSaver : Le délai d’attente 
est dépassé
janv. 10 07:54:48 hephaistos gnome-session-binary[2639]: CRITICAL: Unable to 
create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de 
StartServiceByName pour org.gnome.ScreenSaver : Le délai d’attente est dépassé
janv. 10 07:54:48 hephaistos gnome-screensav[2776]: Couldn't get presence 
status: The name org.gnome.SessionManager was not provided by any .service files
janv. 10 07:54:48 hephaistos dbus-daemon[2632]: Successfully activated service 
'org.gnome.ScreenSaver'

Thanks for your help :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730458

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+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 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

2018-01-09 Thread RégisC
Full output of journactl, the freeze is between janv. 10 07:54:23 and
janv. 10 07:54:48

** Attachment added: "journalctl output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+attachment/5034104/+files/output.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730458

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+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 1741928] Re: Automatic time zone not working

2018-01-09 Thread Daniel van Vugt
Ah yes. It appears that issue has already been reported:
https://bugzilla.gnome.org/show_bug.cgi?id=788714

** Bug watch added: GNOME Bug Tracker #788714
   https://bugzilla.gnome.org/show_bug.cgi?id=788714

** Package changed: gnome-shell (Ubuntu) => gnome-control-center
(Ubuntu)

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=788714
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1741928

Title:
  Automatic time zone not working

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  I have just arrived to Singapore from Spain, and the automatic time zone 
setting in gnome shell is not having any effect.
  I will keep it as is for 1 or 2 days before forcing it manually, but it'd be 
nice for an advertised feature to work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 17:29:46 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-25 (1870 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1741928/+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 1741928] Re: Automatic time zone not working

2018-01-09 Thread shankao
That solved the problem, but... shouldn't the automatic timezone option
be grayed out or warn about it not working when Location Services is
turned off?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1741928

Title:
  Automatic time zone not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have just arrived to Singapore from Spain, and the automatic time zone 
setting in gnome shell is not having any effect.
  I will keep it as is for 1 or 2 days before forcing it manually, but it'd be 
nice for an advertised feature to work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 17:29:46 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-25 (1870 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741928/+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 1742251] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de o

2018-01-09 Thread dino99
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1742251

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: a tentar sobreescrever
  '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras
  instâncias do pacote libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I tried to install brazillian bank security module, but I can't.
  Show error: dconf-waring and dconf-critical

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Jan  9 14:58:23 2018
  ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
  InstallationDate: Installed on 2018-01-09 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1742251/+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 1742358] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-01-09 Thread dino99
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1742358

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Crap

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Jan 10 08:18:46 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Tf3rTB/134-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1742358/+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 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

2018-01-09 Thread Daniel van Vugt
Actually, no it's not related. You say your problem is with gnome-shell
logins and the above is about Unity7 only...

Please try:
 1. sudo apt install openssh-server
 2. Log in from a second machine via ssh, and run: journalctl -f
 3. On the original machine log in locally and reproduce the freeze.
 4. What does your journalctl output say after that? Can you paste it here?

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730458

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+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 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

2018-01-09 Thread Daniel van Vugt
I don't know how the KbdBackLight interface is meant to work. It seems
to be defined in package 'upower'. And that error seems to be from code
in unity-settings-daemon where it fails to change the keyboard backlight
brightness, because something isn't implementing "SetBrightness". And
even then, the error only seems to occur when unity-settings-daemon
changes to GSD_POWER_IDLE_MODE_BLANK. So I wouldn't expect that to be
related to logging in, probably.

Do you have a keyboard backlight at all? Or an external keyboard plugged
in?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730458

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+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 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

2018-01-09 Thread RégisC
HI Da

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730458

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+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 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

2018-01-09 Thread RégisC
Hi Daniel,

Thanks for the analysis, can I do something by myself to prevent that
delay?

Regards

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730458

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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


Re: [Desktop-packages] [Bug 1713371] Re: when I open chromium-browser in ubuntu 14.04 LTS

2018-01-09 Thread Mas Drajat
Over all its fixed in my PC with latest version, Thanks for your
response.

2018-01-09 1:41 GMT+07:00 Olivier Tilloy :

> Is this issue still happening with the latest update
> (63.0.3239.84-0ubuntu0.14.04.1)?
>
> Does it also happen if you start with a fresh profile:
>
> chromium-browser --user-data-dir=/tmp/test-profile
>
> Can you please run the following command in a terminal, this will attach
> useful information to the bug report?
>
> apport-collect 1713371
>
> ** Changed in: chromium-browser (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1713371
>
> Title:
>   when I open chromium-browser in ubuntu 14.04 LTS
>
> Status in chromium-browser package in Ubuntu:
>   Incomplete
>
> Bug description:
>   when I open chromium-browser in ubuntu 14.04 LTS, I have stuck and in
>   my chromium-browser give me "Yah" error
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1713371/+
> subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1713371

Title:
  when I open chromium-browser in ubuntu 14.04 LTS

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  when I open chromium-browser in ubuntu 14.04 LTS, I have stuck and in
  my chromium-browser give me "Yah" error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1713371/+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 1742365] [NEW] built-in display problem

2018-01-09 Thread Susheel Rajagolkar
Public bug reported:

display not minimize, its shows built-in display

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jan 10 10:52:50 2018
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.16.0-30-generic, x86_64: installed
 virtualbox, 4.3.36, 3.16.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6222]
InstallationDate: Installed on 2016-03-01 (679 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Dell Inc. Vostro 3900
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=1d25c27f-72f7-40dd-a53e-0b28eecc57c8 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UdevLog:
 
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0T1D10
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/08/2015:svnDellInc.:pnVostro3900:pvr:rvnDellInc.:rn0T1D10:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 3900
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Jan 10 10:15:15 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPixArt USB Optical Mouse MOUSE, id 8
 inputDell Dell USB Entry Keyboard KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

** Attachment added: "Screenshot from 2018-01-10 10:56:42.png"
   
https://bugs.launchpad.net/bugs/1742365/+attachment/5034071/+files/Screenshot%20from%202018-01-10%2010%3A56%3A42.png

-- 
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/1742365

Title:
  built-in display problem

Status in xorg package in Ubuntu:
  New

Bug description:
  display not minimize, its shows built-in display

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jan 10 10:52:50 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-30-generic, x86_64: installed
   virtualbox, 4.3.36, 3.16.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6222]
  InstallationDate: Installed on 2016-03-01 (679 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Vostro 3900
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=1d25c27f-72f7-40dd-a53e-0b28eecc57c8 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0T1D10
  dmi.board.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

2018-01-09 Thread Gord Kunz
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

ppa:paulo-miguel-dias/pkppa worked for me. No problems since.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741447

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1714886] Re: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()

2018-01-09 Thread Daniel van Vugt
Judging by all the duplicate bugs and the global error reports
(https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7),
this particular bug stopped happening with the introduction of gnome-
shell version 3.26.1.

So if you continue to experience any problems, please open new bugs.

** Changed in: mutter (Ubuntu)
 Assignee: Sam Spilsbury (smspillaz) => (unassigned)

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714886

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_is_on_primary_monitor()

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

  ---

  This crash appears after login in, when gnome-shell restarts it seems
  to be stable.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 09:18:43 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-03 (153 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7ff4e23f8b24 :  
mov0x2c(%rax),%eax
   PC (0x7ff4e23f8b24) ok
   source "0x2c(%rax)" (0x002c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_is_on_primary_monitor () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_on_all_workspaces_changed () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_update_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()
  UpgradeStatus: Upgraded to artful on 2017-08-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1714886/+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 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

2018-01-09 Thread Derek L
Is an SRU fixing this likely to get pushed to artful?  It bites me
several times a week (it's filling my syslog with errors as I write
this).

-- 
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/1723362

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  In Progress

Bug description:
  gnome-software spams this message to journald:

  Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: 
assertion 'index_ + length <= array->len' failed
  Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 10:58:38 2017
  InstallationDate: Installed on 2016-10-25 (352 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1723362/+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 1742358] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-01-09 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1742358

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Crap

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Jan 10 08:18:46 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Tf3rTB/134-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1742358/+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 1742358] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-01-09 Thread Vaibhav Agrawal
Public bug reported:

Crap

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Wed Jan 10 08:18:46 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-Tf3rTB/134-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-01-09 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1742358

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Crap

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Jan 10 08:18:46 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Tf3rTB/134-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1742358/+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 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off

2018-01-09 Thread Po-Hsu Lin
Tested with Bionic Daily build image, gnome-shell 3.26.2
this issue still exist.

** Tags added: artful bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1595695

Title:
  Bluetooth indicator disappears every time bluetooth is being turned
  off

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon 
disappears from the top panel.
  Each time I have to re-enable it by system setting or via dash.

  I expect it to behave in a same way as network indicator instead of
  disappearing.

  Here is the link with some info which could be helpful 
  https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1595695/+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 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2018-01-09 Thread James Donald
Thanks for providing the stack trace, Lars.

This shows the illegal instruction is happening in Skia, specifically
SkJumper's implementation of _sk_xor__vfp4. To run with Skia disabled,
edit your user profile at ~/.mozilla/firefox/*.default/prefs.js and add
the following line:

user_pref("gfx.content.azure.backends", "");

Firefox 32-bit will then launch on Raspbian Stretch. Or if you have more
than one user, you can instead edit /usr/lib/firefox/defaults/pref
/vendor-gre.js

I expect rendering performance is taking a hit with Skia disabled. For a
proper fix we should figure out what's going on with the illegal
instruction(s) in SkJumper_generated.S. This file is auto-generated so
from what I can tell the armv7 version isn't readily available via git.
I have yet to set up a build environment for Firefox, but if someone
here has done so for Arch Linux and another for Ubuntu, we can diff and
track this down.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1711337

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1711337/+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 1714886] Re: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()

2018-01-09 Thread Daniel van Vugt
I'm really not sure we're linking to the right upstream bugs still, or
that we've captured all the right error reports from errors.ubuntu.com.

Possibly this is related and is in progress:
https://bugzilla.gnome.org/show_bug.cgi?id=72

As for Ubuntu crash reports, the only link we have suggests this
particular crash in meta_window_is_on_primary_monitor universally
stopped happening after artful gnome-shell version 3.26.0-0ubuntu2, and
never happened in bionic:

https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

So _if_ this is the right bug for us to be commenting on then we
probably need to find a different but similar error report. Otherwise
we're all commenting on the wrong bug right now.

** Bug watch added: GNOME Bug Tracker #72
   https://bugzilla.gnome.org/show_bug.cgi?id=72

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714886

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_is_on_primary_monitor()

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

  ---

  This crash appears after login in, when gnome-shell restarts it seems
  to be stable.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 09:18:43 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-03 (153 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7ff4e23f8b24 :  
mov0x2c(%rax),%eax
   PC (0x7ff4e23f8b24) ok
   source "0x2c(%rax)" (0x002c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_is_on_primary_monitor () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_on_all_workspaces_changed () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_update_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()
  UpgradeStatus: Upgraded to artful on 2017-08-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1714886/+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 1714886] Re: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()

2018-01-09 Thread Rocko
So is there any progress on this? I can't use gnome-shell because of it,
even with Ubuntu 18.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714886

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_is_on_primary_monitor()

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

  ---

  This crash appears after login in, when gnome-shell restarts it seems
  to be stable.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 09:18:43 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-03 (153 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7ff4e23f8b24 :  
mov0x2c(%rax),%eax
   PC (0x7ff4e23f8b24) ok
   source "0x2c(%rax)" (0x002c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_is_on_primary_monitor () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_on_all_workspaces_changed () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_update_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()
  UpgradeStatus: Upgraded to artful on 2017-08-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1714886/+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 1741843] Re: caribou (gnome-shell osk): special characters not working

2018-01-09 Thread Bug Watch Updater
** Changed in: caribou
   Status: Unknown => In Progress

** Changed in: caribou
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1741843

Title:
  caribou (gnome-shell osk): special characters not working

Status in Caribou:
  In Progress
Status in caribou package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm on Ubuntu 17.10 (fully updated, including Gnome-Shell). Hardware
  is a Lenovo X1 Carbon Laptop with Touchscreen. I've reproduced this
  issue on both Wayland and XOrg. I've reproduced this issue on the
  17.10 live CD (Xorg) and on a fresh 17.10 (Wayland) install in VBox.

  Bug: Caribou/Gnome-Shell Wayland support for Caribou does not display
  the vast majority of special characters (the ones that you long press
  on vowels to get). Nor do the upside down question and exclamation
  marks work on it either. Nor do the Euro or Sterling signs work. This
  makes it impossible to use when writing in any other languages than
  English.

  
  1)  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2) package version:

  caribou:
Installed: 0.4.21-2
Candidate: 0.4.21-2
Version table:
   *** 0.4.21-2 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-shell:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu4 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3) What do I expect to happen: I expect that when I long press on e and get 
the popup and select ê, ë that these letter appear
  4) they do not. nothing happens

To manage notifications about this bug go to:
https://bugs.launchpad.net/caribou/+bug/1741843/+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 1735363] Re: inkscape: Port to Python 3

2018-01-09 Thread Eduard Braun
One thing we'd need to consider is that some more or less basic Inkscape 
functionality currently relies on Python extensions, e.g.
- Several templates
- Help links
  although I already wondered if this was even really necessary -
  I assume there are better solutions available to open a link from GTK
- Export/Import extensions
  They are not strictly Inkscape core but a lot of users are not aware
  they might be running an extension to export to their favorite format.

Second important questions is if this would only affect packaging or if we 
really want to split out the extension code from the Inkscape source repository 
into a more or less self sufficient sub-project.
In the latter case I fear that the bundled extensions - which are in a pretty 
desolate state even now - might bit-rot even faster (less users, less 
developers having the repo on their radar, less obvious affiliation with the 
core program).
If we could achieve to make the extensions into a "community project" (that is 
a lot more user driven, allowing easy contributions and additions of new 
extensions with well-organized categorization and documentation) that could 
also improve upon the status-quo but as a start this would require a "core 
team" of people who would be willing to do the necessary maintenance (not sure 
we have that right now...).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1735363

Title:
  inkscape: Port to Python 3

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  Confirmed

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+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 1741843] Re: caribou (gnome-shell osk): special characters not working

2018-01-09 Thread Daniel van Vugt
** Changed in: caribou
   Importance: Medium => Unknown

** Changed in: caribou
   Status: Confirmed => Unknown

** Changed in: caribou
 Remote watch: GNOME Bug Tracker #777468 => GNOME Bug Tracker #604585

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1741843

Title:
  caribou (gnome-shell osk): special characters not working

Status in Caribou:
  Unknown
Status in caribou package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm on Ubuntu 17.10 (fully updated, including Gnome-Shell). Hardware
  is a Lenovo X1 Carbon Laptop with Touchscreen. I've reproduced this
  issue on both Wayland and XOrg. I've reproduced this issue on the
  17.10 live CD (Xorg) and on a fresh 17.10 (Wayland) install in VBox.

  Bug: Caribou/Gnome-Shell Wayland support for Caribou does not display
  the vast majority of special characters (the ones that you long press
  on vowels to get). Nor do the upside down question and exclamation
  marks work on it either. Nor do the Euro or Sterling signs work. This
  makes it impossible to use when writing in any other languages than
  English.

  
  1)  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2) package version:

  caribou:
Installed: 0.4.21-2
Candidate: 0.4.21-2
Version table:
   *** 0.4.21-2 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  gnome-shell:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu4 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3) What do I expect to happen: I expect that when I long press on e and get 
the popup and select ê, ë that these letter appear
  4) they do not. nothing happens

To manage notifications about this bug go to:
https://bugs.launchpad.net/caribou/+bug/1741843/+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 1726156] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from construct

2018-01-09 Thread Daniel van Vugt
This issue is also being tracked in:
https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc

** Description changed:

+ https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc
+ 
+ ---
+ 
  gnome-shell-portal-helper crashed with SIGABRT
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 17:19:12 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  InstallationDate: Installed on 2017-06-08 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1726156

Title:
  gnome-shell-portal-helper crashed with SIGABRT in
  g_assertion_message() from g_assertion_message_expr("assertion failed:
  (priv->label_box == NULL)") from construct_label_box()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc

  ---

  gnome-shell-portal-helper crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 17:19:12 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  InstallationDate: Installed on 2017-06-08 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726156/+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 1742339] Re: gnome-shell crashed with signal 5

2018-01-09 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409

** This bug is no longer a duplicate of private bug 1742278
** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1742339

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  Uname: Linux 4.15.0-041500rc5-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Jan  9 12:05:16 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-08 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-20 (50 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742339/+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 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

2018-01-09 Thread Daniel van Vugt
Yes, sorry about that. I experience the same on my development machine.
I have no idea why that's happening.

Suggestion: Remove the two empty files *.upload and *.uploaded and then
in a terminal re-upload the existing crash file:

  ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

That will take a minute or two to complete but then you will be directed
either to an existing bug report, or asked to make a new one. Either
way, please let us know here what web page you end up with.

When I say "directed" I mean that ubuntu-bug will print a link for you
to copy and paste.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1741886

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1742344] Re: /usr/lib/gnome-shell/gnome-shell-portal-helper:6:g_assertion_message:g_assertion_message_expr:construct_label_box:gtk_header_bar_init:g_type_create_instance

2018-01-09 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1726156 ***
https://bugs.launchpad.net/bugs/1726156

** This bug has been marked a duplicate of bug 1726156
   gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from 
g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from 
construct_label_box()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1742344

Title:
  /usr/lib/gnome-shell/gnome-shell-portal-
  
helper:6:g_assertion_message:g_assertion_message_expr:construct_label_box:gtk_header_bar_init:g_type_create_instance

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742344/+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 1742344] [NEW] /usr/lib/gnome-shell/gnome-shell-portal-helper:6:g_assertion_message:g_assertion_message_expr:construct_label_box:gtk_header_bar_init:g_type_create_instance

2018-01-09 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1726156 ***
https://bugs.launchpad.net/bugs/1726156

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1742344

Title:
  /usr/lib/gnome-shell/gnome-shell-portal-
  
helper:6:g_assertion_message:g_assertion_message_expr:construct_label_box:gtk_header_bar_init:g_type_create_instance

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/a039119a90b52c4a5ec06f28324629c364aeb0cc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742344/+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 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-09 Thread Daniel van Vugt
Great. But just a warning; 17.04 reaches end of life this month:
https://wiki.ubuntu.com/Releases

So you will need to upgrade again soon. If you're using gnome-shell then
we recommend 17.10 right now. And before May 2018 we will have 18.04
ready too.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1739525

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  As requested by vanvugt in #1580605, submitting a crash unique to my
  user.

  This isn't fun, several times per day a crash:
  {{{
  $ dmesg -T | grep seg
  [Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip 
7fd954f6d6a2 sp 7ffe04425eb8 error 4 in 
libgdk-3.so.0.1800.9[7fd954f3+d4000]
  [Thu Nov 9 10:11:16 2017] dota2[22006]: segfault at 0 ip 7fef2866683a sp 
7fff560539a0 error 6 in libtier0.so[7fef2863+8]
  [Thu Nov 9 13:04:18 2017] gnome-shell[1356]: segfault at e8 ip 
7f15ccddd6a2 sp 7fff9ecf47f8 error 4 in 
libgdk-3.so.0.1800.9[7f15ccda+d4000]
  [Thu Nov 9 17:16:45 2017] gnome-shell[14440]: segfault at e8 ip 
7f196afdd6a2 sp 7ffea13b5948 error 4 in 
libgdk-3.so.0.1800.9[7f196afa+d4000]
  [Thu Nov 9 17:16:52 2017] dconf worker[18015]: segfault at 52c ip 
004a133c sp 7f351f7e6170 error 4 in perl[40+1cf000]
  [Thu Nov 9 20:35:24 2017] gnome-shell[32271]: segfault at e8 ip 
7fd6ef0256a2 sp 7ffebb0d3608 error 4 in 
libgdk-3.so.0.1800.9[7fd6eefe8000+d4000]
  [Thu Nov 9 20:42:09 2017] gnome-shell[11070]: segfault at 23 ip 
7fc2bd8687bf sp 7fffcc3bc680 error 4 in 
libgnome-desktop-3.so.12.0.0[7fc2bd848000+39000]
  [Thu Nov 9 23:13:09 2017] gnome-shell[24832]: segfault at 6 ip 
7fb95e624818 sp 7ffc656ced30 error 4 in 
libgio-2.0.so.0.4800.2[7fb95e56+18]
  [Thu Nov 9 23:51:17 2017] gnome-shell[3253]: segfault at e8 ip 
7f2d1f4756a2 sp 7fff455b3128 error 4 in 
libgdk-3.so.0.1800.9[7f2d1f438000+d4000]
  [Fri Nov 10 01:09:27 2017] gnome-shell[31134]: segfault at e8 ip 
7f3b923756a2 sp 7fff91dea558 error 4 in 
libgdk-3.so.0.1800.9[7f3b92338000+d4000]
  [Fri Nov 10 01:12:43 2017] gnome-shell[9188]: segfault at e8 ip 
7f683370d6a2 sp 7ca20198 error 4 in 
libgdk-3.so.0.1800.9[7f68336d+d4000]
  [Fri Nov 10 03:40:54 2017] gnome-shell[25978]: segfault at e8 ip 
7f8af06ed6a2 sp 7ffdf3c5cfc8 error 4 in 
libgdk-3.so.0.1800.9[7f8af06b+d4000]
  [Sat Nov 11 00:49:59 2017] gnome-shell[31566]: segfault at e8 ip 
7ffab7ae56a2 sp 7fff76561338 error 4 in 
libgdk-3.so.0.1800.9[7ffab7aa8000+d4000]
  [Sat Nov 11 20:01:10 2017] gnome-shell[23459]: segfault at e8 ip 
7f6a4c1dd6a2 sp 7ffdfcd62008 error 4 in 
libgdk-3.so.0.1800.9[7f6a4c1a+d4000]
  [Sat Nov 11 21:05:36 2017] gnome-shell[28874]: segfault at e8 ip 
7f48523d56a2 sp 7ffd15fbc738 error 4 in 
libgdk-3.so.0.1800.9[7f4852398000+d4000]
  }}}

  My setup:
   * Dual monitors
   * OFTEN switch between users
  a) using the GDM3 "switch user" GUI
  b) using CTRL+ALT+FXX quick flips
   * Daily I suspend the system and resume (Power Management)

  Versions
  {{{
  $ cat /etc/issue
  Ubuntu 16.04.3 LTS \n \l

  $ uname -a
  Linux  4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  
  $ dpkg --list | grep gnome-shell
  ii  chrome-gnome-shell  
9-0ubuntu1~ubuntu16.04.3 all  GNOME Shell 
extensions integration for web browsers
  ii  gnome-shell 
3.18.5-0ubuntu0.3amd64graphical shell for 
the GNOME desktop
  ii  gnome-shell-common  
3.18.5-0ubuntu0.3all  common files for the 
GNOME graphical shell
  ii  gnome-shell-timer   
0.3.12+20140924-3all  GNOME Shell extension 
providing a countdown timer in the top panel

  $ dpkg --list | grep libgdk
  ii  libgdk-pixbuf2.0-0:amd64
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
  ii  libgdk-pixbuf2.0-0:i386 
2.32.2-1ubuntu1.3i386 GDK Pixbuf library
  ii  libgdk-pixbuf2.0-common 
2.32.2-1ubuntu1.3all  GDK Pixbuf library - 
data files
  ii  libgdk-pixbuf2.0-dev
2.32.2-1ubuntu1.3amd64GDK Pixbuf library 
(development files)
  }}}

  Some random snippet:
  {{{
   Dec 6 21:47:44 fermmy gnome-session[9885]: (gnome-shell:10011): 

[Desktop-packages] [Bug 1742339] Re: gnome-shell crashed with signal 5

2018-01-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1742278 ***
https://bugs.launchpad.net/bugs/1742278

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1742278, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1742339/+attachment/5033979/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1742339/+attachment/5033981/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1742339/+attachment/5033984/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1742339/+attachment/5033985/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1742339/+attachment/5033986/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742339/+attachment/5033987/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742339/+attachment/5033988/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1742278

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1742339

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  Uname: Linux 4.15.0-041500rc5-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Jan  9 12:05:16 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-08 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-20 (50 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742339/+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 1716432] Re: With dash to dock enabled, title in window is not centred aligned to clock when the window is maximised

2018-01-09 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1716432

Title:
  With dash to dock enabled, title in window is not centred aligned to
  clock when the window is maximised

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  With the dash-to-dock extension enabled and intelli-hide not enabled,
  the title of applications is not centre aligned with the gnome shell
  clock, as shown here [0].

  Possible solutions are
  1) When the window is maximised to align the title to the monitor centre not 
window centre
  2) When dash-to-dock is enabled move the clock to be slightly off monitor 
centre so it would line up with the window centre
  3) Ignore the alignment issue :-)

  0 - http://imgur.com/a/5cJ47

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1716432/+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 1735363] Re: inkscape: Port to Python 3

2018-01-09 Thread Hachmann
Thank you for the explanation, Bryce and Mattia! But until 2020, this
should be solved, as far as I understand, regardless of this? We've only
got 2 hackfests until then... time flies.

I found that these depend on python scripts, but there may be more, hope
others will fill in the blanks (I've also got no clue of how easy or
hard it's to port these):

- several python export and import routines (that use extensions, e.g.
save as optimized SVG via scour (how's scour doing with Python3,
@Eduard?), dxf. What about uniconvertor? Does it have a python3
version?... We don't include it, but it needs to work with the rest...
:-/ Or I think there was talk about dropping it...?

- the customizable templates (those with dots in the 'New from Template'
dialog).

- everything aside from Tutorials in the Help menu (probably very quick
to port, if anything needs to be done at all)

- couldn't find what 'prepare_file_save_as.py' is currently used for,
weirdly - but I think it was needed for export to dxf...

- there seem to be several i18n-generation scripts in various
subdirectories of the /share/... directory tree - guess they are used to
internationalize the svg files (filters, markers,...) there

- several packaging scripts, for win and some Cmake scripts

- (extension tests)

- dpi switcher extension (not needed when opening files, intended for
switching manually later)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1735363

Title:
  inkscape: Port to Python 3

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  Confirmed

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+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 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

2018-01-09 Thread Daniel van Vugt
Your log shows an 11 second delay each time this happens:

Nov 06 13:57:46 hostname gnome-session-binary[3428]: WARNING: Could not get 
session path for session. Check that logind is properly installed and 
pam_systemd is getting used at login.
Nov 06 13:57:57 hostname unity-settings-[3399]: failed to turn the kbd 
backlight off: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such 
interface 'org.freedesktop.UPower.KbdBacklight' on object at path 
/org/freedesktop/UPower/KbdBacklight

and

Nov 06 15:38:07 hostname gnome-session-binary[3428]: WARNING: Could not get 
session path for session. Check that logind is properly installed and 
pam_systemd is getting used at login.
Nov 06 15:38:18 hostname unity-settings-[3399]: failed to turn the kbd 
backlight off: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such 
interface 'org.freedesktop.UPower.KbdBacklight' on object at path 
/org/freedesktop/UPower/KbdBacklight

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730458

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+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 1735363] Re: inkscape: Port to Python 3

2018-01-09 Thread Mattia Rizzolo
The main → universe move as I see it has more of a logistic change: 
theoretically speaking, as long as it is in main Canonical could be called upon 
providing commercial support if any customer asked for it, as well as providing 
security patches if any security breach appeared, etc.
At any rate, yes, nothing to be concerned about: actually using a Ubuntu 
desktop without universe is just plain impossible anyway.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1735363

Title:
  inkscape: Port to Python 3

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  Confirmed

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+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 1742280] Re: nvidia-340 340.104-0ubuntu2: nvidia-340 kernel module failed to build

2018-01-09 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1741914 ***
https://bugs.launchpad.net/bugs/1741914

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1741914, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1741914
   artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate 
ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel 
or elfutils-libelf-devel]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1742280

Title:
  nvidia-340 340.104-0ubuntu2: nvidia-340 kernel module failed to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  error occured during normal system update with the standard Software-Update 
Tool. 
  Havn't done anything unusual during Update.
  Kodi 17.6 was up and waiting to start something in Main-Menue on 3rd virtual 
Desktop during Update.

  Going to reboot the system after this Kernel Update and see what
  happens.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-340 340.104-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Tue Jan  9 21:39:15 2018
  InstallationDate: Installed on 2015-05-04 (981 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 340.104-0ubuntu2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.104-0ubuntu2: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1742280/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfuti

2018-01-09 Thread Daniel van Vugt
linux (4.13.0-25.29) artful; urgency=low

  * linux: 4.13.0-25.29 -proposed tracker (LP: #1741955)

  * CVE-2017-5754
- Revert "UBUNTU: [Config] updateconfigs to enable PTI"
- [Config] Enable PTI with UNWINDER_FRAME_POINTER


** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5754

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: bbswitch (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bcmwl (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ndiswrapper (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: virtualbox (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: rtl8812au (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: rtl8812au (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1741914

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Invalid
Status in bcmwl package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in ndiswrapper package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid
Status in rtl8812au package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Invalid

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1735363] Re: inkscape: Port to Python 3

2018-01-09 Thread Bryce Harrington
I'd second Ted's suggestion of splitting out python code to a separate
package, that's something we've been pondering doing for other reasons
already.

Do we have a listing of what exactly uses python?

I know the extension programs do, and those could be split out to an
inkscape-extras package.

If there are any utilities or build helpers in python, those should be
redoable in python3 without much fuss.  Give me a list and I can make
sure they all get done.

Is there anything else besides that?  Does Inkscape have any python
bindings internally that are version specific?

@moini, being demoted from main isn't that big of a deal, it's more a
loss against Ubuntu than Inkscape itself.  Most users will have universe
enabled so it's not going to impact them.  It just limits Canonical's
ability to make good use of Inkscape in their own products.  Like Ted
points out, users have many ways to get Inkscape.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1735363

Title:
  inkscape: Port to Python 3

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  Confirmed

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+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 1735363] Re: inkscape: Port to Python 3

2018-01-09 Thread Hachmann
@valavanisalex Sorry, I don't know much about it. su_v is often around
on IRC, please ask her there about the status or send her an email. As
far as I know, there is no other place tracking this.

Do you think this might become one focus for the Hackfest? Being
'demoted' doesn't sound so good in my ears, tbh.

(Found this only by chance, I definitely need to remember to subscribe
here when I comment...)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1735363

Title:
  inkscape: Port to Python 3

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  Confirmed

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+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


Re: [Desktop-packages] [Bug 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

2018-01-09 Thread Austin Hester
I have figured this out as well. It would be nice to be able to use
gnome-network-manager though.

On Jan 9, 2018 18:25, "mash" <1735...@bugs.launchpad.net> wrote:

> The problem occurs when I use network-manager to initiate the VPN.
>
>
> The problem does not occur when I run openconnect from the command line:
>
> sudo openconnect --cafile /etc/ssl/certs/ca-certificates.crt --juniper
> https://vpn.myschool.edu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1735798
>
> Title:
>   Unable to access any subdomain provided by VPN provider until reboot.
>
> Status in network-manager package in Ubuntu:
>   Confirmed
> Status in openconnect package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
>   and any domain hosted by the server. For reference, this is my
>   school's VPN, and I am unable to get on mygateway or even the school's
>   main website after I disconnect from the VPN or the computer sleeps
>   after the VPN has been started. It uses EAP authentication.
>
>   Here is the log after connecting once, turning off, and restarting:
>   LOG:
>   POST https://vpn.myschool.edu/
>   getaddrinfo failed for host 'vpn.myschool.edu': Name or service not
> known
>   Failed to open HTTPS connection to vpn.myschool.edu
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: network-manager 1.8.4-1ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
>   Uname: Linux 4.13.0-17-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Dec  1 11:39:56 2017
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2016-12-02 (364 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   IpRoute:
>default via 192.168.1.1 dev wlp5s0 proto static metric 600
>169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
>192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144
> metric 600
>192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
> linkdown
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: network-manager
>   UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.8.4connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735798/+
> subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1735798

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

Status in network-manager package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my
  school's VPN, and I am unable to get on mygateway or even the school's
  main website after I disconnect from the VPN or the computer sleeps
  after the VPN has been started. It uses EAP authentication.

  Here is the log after connecting once, turning off, and restarting:
  LOG:
  POST https://vpn.myschool.edu/
  getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
  Failed to open HTTPS connection to vpn.myschool.edu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto static metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   

[Desktop-packages] [Bug 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

2018-01-09 Thread mash
The problem occurs when I use network-manager to initiate the VPN.


The problem does not occur when I run openconnect from the command line:

sudo openconnect --cafile /etc/ssl/certs/ca-certificates.crt --juniper
https://vpn.myschool.edu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1735798

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

Status in network-manager package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my
  school's VPN, and I am unable to get on mygateway or even the school's
  main website after I disconnect from the VPN or the computer sleeps
  after the VPN has been started. It uses EAP authentication.

  Here is the log after connecting once, turning off, and restarting:
  LOG:
  POST https://vpn.myschool.edu/
  getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
  Failed to open HTTPS connection to vpn.myschool.edu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto static metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735798/+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 1742306] [NEW] /usr/lib/ibus/ibus-engine-chewing:11:key_sym_get_name:ibus_chewing_engine_process_key_event:_ibus_marshal_BOOLEAN__UINT_UINT_UINT:g_closure_invoke:signal_emit_un

2018-01-09 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
ibus-chewing.  This problem was most recently seen with package version 
1.5.1-1, the problem page at 
https://errors.ubuntu.com/problem/9c4dcff54103d32daf139719b2b37d6ee59ad104 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: ibus-chewing (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful wily xenial yakkety zesty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus-chewing in Ubuntu.
https://bugs.launchpad.net/bugs/1742306

Title:
  /usr/lib/ibus/ibus-engine-
  
chewing:11:key_sym_get_name:ibus_chewing_engine_process_key_event:_ibus_marshal_BOOLEAN__UINT_UINT_UINT:g_closure_invoke:signal_emit_unlocked_R

Status in ibus-chewing package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
ibus-chewing.  This problem was most recently seen with package version 
1.5.1-1, the problem page at 
https://errors.ubuntu.com/problem/9c4dcff54103d32daf139719b2b37d6ee59ad104 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-chewing/+bug/1742306/+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 1070873] Re: kde-telepathy, impossible to connect to gmail accounts

2018-01-09 Thread Florian Fainelli
I can confirm that signon-ui-service
(0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) and signon-ui-x11
(0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) allow me to get past
the Google account error. The account shows up, but going online does
not quite work yet (which I have seen before).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1070873

Title:
  kde-telepathy, impossible to connect to gmail accounts

Status in meta-kde-telepathy package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  Im running ubuntu 12.10 quantal and i have installed kde, when running
  kde-telepathy i have added a gmail account, and after entering the
  password it has revealed impossible to connect to it, it always says
  that the password is wrong when that is false.

  When using empathy, i have removed the gmail account and have added it
  again, now appears a XMLL window asking ubuntu permission to conenct
  to it, and now i was able to conenct to the gmail account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

2018-01-09 Thread Timo Aaltonen
this is a more complete command to install stock hwe stack on 16.04

sudo apt install --install-recommends xserver-xorg xserver-xorg-core
xserver-xorg-video-all xserver-xorg-input-all xserver-xorg-video-intel
xserver-xorg-video-qxl

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1742294] Re: duplicity crashes with memory error

2018-01-09 Thread Scott
ubuntu 16.04 duplicity 0.7.06

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1742294

Title:
  duplicity crashes with memory error

Status in duplicity package in Ubuntu:
  New

Bug description:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1532, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1526, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1380, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1507, in do_backup
  check_last_manifest(col_stats)  # not needed for full backup
File "/usr/bin/duplicity", line 1211, in check_last_manifest
  last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201, 
in check_manifests
  remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 243, 
in get_remote_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
  match = next_vi_string_regexp.search(s[starting_s_index:])
  MemoryError

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1742294/+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 1742294] [NEW] duplicity crashes with memory error

2018-01-09 Thread Scott
Public bug reported:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1532, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1526, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1380, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1507, in do_backup
check_last_manifest(col_stats)  # not needed for full backup
  File "/usr/bin/duplicity", line 1211, in check_last_manifest
last_backup_set.check_manifests()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201, 
in check_manifests
remote_manifest = self.get_remote_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 243, 
in get_remote_manifest
return manifest.Manifest().from_string(manifest_buffer)
  File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
match = next_vi_string_regexp.search(s[starting_s_index:])
MemoryError

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1742294

Title:
  duplicity crashes with memory error

Status in duplicity package in Ubuntu:
  New

Bug description:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1532, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1526, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1380, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1507, in do_backup
  check_last_manifest(col_stats)  # not needed for full backup
File "/usr/bin/duplicity", line 1211, in check_last_manifest
  last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201, 
in check_manifests
  remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 243, 
in get_remote_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
  match = next_vi_string_regexp.search(s[starting_s_index:])
  MemoryError

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1742294/+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 1732012] Re: After turning display (LCD TV) off and then back on, session ends and Ubuntu goes back to the logon screen

2018-01-09 Thread Jonathan Avraham
Thanks for your input, Daniel, but I just easily reproduced it (just
flip the input source bach and forth, no need to even turn the TV off)
and no crash file was created. /var/crash only has 4 crash files, none
of which are from today.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1732012

Title:
  After turning display (LCD TV) off and then back on, session ends and
  Ubuntu goes back to the logon screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  TV is an old Toshiba LCD connected via HDMI. Problem first appeared
  after upgrade to Artful.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,compiztoolbox,imgpng,obs,gnomecompat,vpswitch,regex,resize,move,place,mousepoll,animation,grid,workarounds,session,wobbly,fade,cube,rotate,expo,scale,unitymtgrabhandles,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 21:56:50 2017
  DistUpgraded: 2017-10-21 11:42:55,395 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-38-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6530D] 
[1002:964a] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6530D] 
[1458:d000]
  InstallationDate: Installed on 2012-05-29 (1994 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-D2H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=ce7c3cb8-c699-4b71-8e50-d1a46484f917 ro quiet splash
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-10-21 (23 days ago)
  dmi.bios.date: 11/03/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: GA-A75M-D2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd11/03/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-D2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75M-D2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct 18 21:11:02 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: radeon

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


Re: [Desktop-packages] [Bug 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or el

2018-01-09 Thread James Campbell
Right after reporting this and 3 other bugs all at the same time, I
rebooted and it got cought in a loop right before the login and I had to
reinstall.
Thank you for working on these issues, your way ahead of me.
James


On Tue, Jan 9, 2018 at 5:17 AM, Jacques Koch <1741...@bugs.launchpad.net>
wrote:

> Thanks will definitely go and take a look. Only been on Linux about a month
> or so and really loving it  ,but still finding my feet
>
> On 9 Jan 2018 12:50, "Daniel van Vugt" 
> wrote:
>
> > It looks like this bug is now fixed as of 1 hour ago, in linux
> > 4.13.0-25.29. You had to be unlucky to have an artful system on proposed
> > do an update during the previous day and get the faulty package linux
> > 4.13.0-24. That one doesn't exist any more so this bug should quieten
> > down now.
> >
> > See bug 1741955 for updates.
> >
> > ** Changed in: linux (Ubuntu)
> >Status: Confirmed => Fix Committed
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1742014).
> > https://bugs.launchpad.net/bugs/1741914
> >
> > Title:
> >   artful-proposed 4.13.0-24: kernel module failed to build [Cannot
> >   generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
> >   libelf-dev, libelf-devel or elfutils-libelf-devel]
> >
> > Status in bbswitch package in Ubuntu:
> >   Confirmed
> > Status in bcmwl package in Ubuntu:
> >   Confirmed
> > Status in linux package in Ubuntu:
> >   Fix Committed
> > Status in ndiswrapper package in Ubuntu:
> >   Confirmed
> > Status in nvidia-graphics-drivers-304 package in Ubuntu:
> >   Confirmed
> > Status in nvidia-graphics-drivers-340 package in Ubuntu:
> >   Confirmed
> > Status in nvidia-graphics-drivers-384 package in Ubuntu:
> >   Confirmed
> > Status in virtualbox package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   After update to new kernel (4.13.0-24) the system prompted me with
> >   this.
> >
> >   ProblemType: Package
> >   DistroRelease: Ubuntu 17.10
> >   Package: nvidia-384 384.90-0ubuntu3.17.10.2
> >   ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
> >   Uname: Linux 4.13.0-22-generic x86_64
> >   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
> >   ApportVersion: 2.20.7-0ubuntu3.7
> >   Architecture: amd64
> >   DKMSKernelVersion: 4.13.0-24-generic
> >   Date: Mon Jan  8 16:30:09 2018
> >   PackageVersion: 384.90-0ubuntu3.17.10.2
> >   Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal,
> > 3.6.3-0ubuntu2
> >   PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal,
> > 2.7.14-2ubuntu1
> >   RelatedPackageVersions:
> >dpkg 1.18.24ubuntu1
> >apt  1.5.1
> >   SourcePackage: nvidia-graphics-drivers-384
> >   Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module
> > failed to build
> >   UpgradeStatus: No upgrade log present (probably fresh install)
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/
> > 1741914/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1742039).
> https://bugs.launchpad.net/bugs/1741914
>
> Title:
>   artful-proposed 4.13.0-24: kernel module failed to build [Cannot
>   generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
>   libelf-dev, libelf-devel or elfutils-libelf-devel]
>
> Status in bbswitch package in Ubuntu:
>   Confirmed
> Status in bcmwl package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in ndiswrapper package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-304 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-340 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-384 package in Ubuntu:
>   Confirmed
> Status in virtualbox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After update to new kernel (4.13.0-24) the system prompted me with
>   this.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 17.10
>   Package: nvidia-384 384.90-0ubuntu3.17.10.2
>   ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
>   Uname: Linux 4.13.0-22-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.7-0ubuntu3.7
>   Architecture: amd64
>   DKMSKernelVersion: 4.13.0-24-generic
>   Date: Mon Jan  8 16:30:09 2018
>   PackageVersion: 384.90-0ubuntu3.17.10.2
>   Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal,
> 3.6.3-0ubuntu2
>   PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal,
> 2.7.14-2ubuntu1
>   RelatedPackageVersions:
>dpkg 1.18.24ubuntu1
>apt  1.5.1
>   SourcePackage: nvidia-graphics-drivers-384
>   Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module
> failed to build
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> 

[Desktop-packages] [Bug 1742288] Re: gvfsd-smb-browse crashed with SIGABRT in _talloc_array()

2018-01-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1710770 ***
https://bugs.launchpad.net/bugs/1710770

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1710770, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1742288/+attachment/5033796/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1742288/+attachment/5033798/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1742288/+attachment/5033801/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1742288/+attachment/5033802/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1742288/+attachment/5033803/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742288/+attachment/5033804/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742288/+attachment/5033805/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1710770

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1742288

Title:
  gvfsd-smb-browse crashed with SIGABRT in _talloc_array()

Status in gvfs package in Ubuntu:
  New

Bug description:
  Crach when I open A screenshot via SSH

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.34.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 22:22:29 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2018-01-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180101)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.7 
/org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   LANG=sv_SE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   _talloc_array () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   name_resolve_bcast_send () from /usr/lib/x86_64-linux-gnu/samba/libgse.so.0
   name_resolve_bcast () from /usr/lib/x86_64-linux-gnu/samba/libgse.so.0
   internal_resolve_name () from /usr/lib/x86_64-linux-gnu/samba/libgse.so.0
  Title: gvfsd-smb-browse crashed with SIGABRT in _talloc_array()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev root 
sambashare scanner ssh ssl-cert sudo tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1742288/+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 1741925] Re: Unity launcher disappears on mouse-over launcher

2018-01-09 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

no need to debug anymore, the issue is well known by now and 1735594 has
more information, you should have received my emails about it

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741925

Title:
  Unity launcher disappears on mouse-over launcher

Status in mesa package in Ubuntu:
  New

Bug description:
  Move the mouse over the launcher and the EVERYTHING on the desktop
  disappears for a few seconds. Only the wallpaper remains. Failed
  immediately after the latest update (installed by me on 5 Jan 2018)
  and a reboot. Reboot doesn't help.

  Launcher and the other desktop displays return after a 10 to 30 second
  pause. No disk activity is observed during recovery.

  "ClassicMenu Indicator" is installed and it is the only way to start
  an application.

  Executing the bug and then immediately examining all the /var/log logs
  showed no recorded error or incident in any log.

  uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic
  #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686
  GNU/Linux

  Abridged hardware list from  sudo lshw
   
  description: Portable Computer
  product: Latitude D630
  vendor: Dell Inc.
  width: 32 bits
  capabilities: smbios-2.4 dmi-2.4
  configuration: boot=normal chassis=portable 
uuid=44454C4C-6E00-1039-8032-B2C04F376831
*-core
 description: Motherboard
 vendor: Dell Inc.
 physical id: 0
 serial: .2n927h1.  .
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A12
date: 06/20/2008
size: 64KiB
capacity: 1984KiB
capabilities: isa pci pcmcia pnp upgrade shadowing cdboot 
bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer 
int10video acpi usb agp smartbattery biosbootspecification netboot
   *-cpu
description: CPU
product: Intel(R) Core(TM)2 Duo CPU T7250  @ 2.00GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 6.15.13
serial: -06FD----
slot: Microprocessor
size: 2GHz
capacity: 2001MHz
width: 64 bits
clock: 200MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi 
flexpriority dtherm ida cpufreq
configuration: cores=2 enabledcores=2 id=0 threads=2
  *-cache:0
   description: L1 cache
   physical id: 700
   size: 32KiB
   capacity: 32KiB
   capabilities: internal write-back data
   configuration: level=1
  *-cache:1
   description: L2 cache
   physical id: 701
   size: 2MiB
   capacity: 2MiB
   clock: 66MHz (15.0ns)
   capabilities: pipeline-burst internal varies unified
   configuration: level=2
  *-logicalcpu:0
   description: Logical CPU
   physical id: 0.1
   width: 64 bits
   capabilities: logical
  *-logicalcpu:1
   description: Logical CPU
   physical id: 0.2
   width: 64 bits
   capabilities: logical
   *-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 2GiB
  *-bank:0
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 0
   serial: 07B02E7C
   slot: DIMM_A
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
  *-bank:1
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 1
   serial: E9AE2E7D
   slot: DIMM_B
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
   *-pci
description: Host bridge
product: Mobile PM965/GM965/GL960 Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 0c
width: 32 bits
clock: 33MHz

To manage notifications about this bug go to:

Re: [Desktop-packages] [Bug 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or el

2018-01-09 Thread James Campbell
Right after reporting this and 3 other bugs all at the same time, I
rebooted and it got cought in a loop right before the login and I had to
reinstall.
Thank you for working on these issues, your way ahead of me.
James

On Tue, Jan 9, 2018 at 7:27 AM, Videonauth <1741...@bugs.launchpad.net>
wrote:

> Yes, sadly now the NVidia Driver 384.90 (I still wonder where you get
> the 384.111 on artful) fails still to build even after the released fix.
> But this time with a different message and build log. And without
> showing me an opportunity to report the bug (except using ubuntu-bug
> command which will maybe not fetch all information).
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1742039).
> https://bugs.launchpad.net/bugs/1741914
>
> Title:
>   artful-proposed 4.13.0-24: kernel module failed to build [Cannot
>   generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
>   libelf-dev, libelf-devel or elfutils-libelf-devel]
>
> Status in bbswitch package in Ubuntu:
>   Confirmed
> Status in bcmwl package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in ndiswrapper package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-304 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-340 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-384 package in Ubuntu:
>   Confirmed
> Status in virtualbox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After update to new kernel (4.13.0-24) the system prompted me with
>   this.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 17.10
>   Package: nvidia-384 384.90-0ubuntu3.17.10.2
>   ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
>   Uname: Linux 4.13.0-22-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.7-0ubuntu3.7
>   Architecture: amd64
>   DKMSKernelVersion: 4.13.0-24-generic
>   Date: Mon Jan  8 16:30:09 2018
>   PackageVersion: 384.90-0ubuntu3.17.10.2
>   Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal,
> 3.6.3-0ubuntu2
>   PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal,
> 2.7.14-2ubuntu1
>   RelatedPackageVersions:
>dpkg 1.18.24ubuntu1
>apt  1.5.1
>   SourcePackage: nvidia-graphics-drivers-384
>   Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module
> failed to build
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/
> 1741914/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1741914

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1741925] Re: Unity launcher disappears on mouse-over launcher

2018-01-09 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

not emails but replies/edits to that bug

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741925

Title:
  Unity launcher disappears on mouse-over launcher

Status in mesa package in Ubuntu:
  New

Bug description:
  Move the mouse over the launcher and the EVERYTHING on the desktop
  disappears for a few seconds. Only the wallpaper remains. Failed
  immediately after the latest update (installed by me on 5 Jan 2018)
  and a reboot. Reboot doesn't help.

  Launcher and the other desktop displays return after a 10 to 30 second
  pause. No disk activity is observed during recovery.

  "ClassicMenu Indicator" is installed and it is the only way to start
  an application.

  Executing the bug and then immediately examining all the /var/log logs
  showed no recorded error or incident in any log.

  uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic
  #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686
  GNU/Linux

  Abridged hardware list from  sudo lshw
   
  description: Portable Computer
  product: Latitude D630
  vendor: Dell Inc.
  width: 32 bits
  capabilities: smbios-2.4 dmi-2.4
  configuration: boot=normal chassis=portable 
uuid=44454C4C-6E00-1039-8032-B2C04F376831
*-core
 description: Motherboard
 vendor: Dell Inc.
 physical id: 0
 serial: .2n927h1.  .
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A12
date: 06/20/2008
size: 64KiB
capacity: 1984KiB
capabilities: isa pci pcmcia pnp upgrade shadowing cdboot 
bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer 
int10video acpi usb agp smartbattery biosbootspecification netboot
   *-cpu
description: CPU
product: Intel(R) Core(TM)2 Duo CPU T7250  @ 2.00GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 6.15.13
serial: -06FD----
slot: Microprocessor
size: 2GHz
capacity: 2001MHz
width: 64 bits
clock: 200MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi 
flexpriority dtherm ida cpufreq
configuration: cores=2 enabledcores=2 id=0 threads=2
  *-cache:0
   description: L1 cache
   physical id: 700
   size: 32KiB
   capacity: 32KiB
   capabilities: internal write-back data
   configuration: level=1
  *-cache:1
   description: L2 cache
   physical id: 701
   size: 2MiB
   capacity: 2MiB
   clock: 66MHz (15.0ns)
   capabilities: pipeline-burst internal varies unified
   configuration: level=2
  *-logicalcpu:0
   description: Logical CPU
   physical id: 0.1
   width: 64 bits
   capabilities: logical
  *-logicalcpu:1
   description: Logical CPU
   physical id: 0.2
   width: 64 bits
   capabilities: logical
   *-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 2GiB
  *-bank:0
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 0
   serial: 07B02E7C
   slot: DIMM_A
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
  *-bank:1
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 1
   serial: E9AE2E7D
   slot: DIMM_B
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
   *-pci
description: Host bridge
product: Mobile PM965/GM965/GL960 Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 0c
width: 32 bits
clock: 33MHz

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1742287] Re: gvfsd-mtp crashed with SIGSEGV

2018-01-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1706097, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1742287/+attachment/5033782/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1742287/+attachment/5033784/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1742287/+attachment/5033788/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1742287/+attachment/5033789/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1742287/+attachment/5033790/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742287/+attachment/5033791/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742287/+attachment/5033792/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1742287

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  This message occurred when I connected my smartphone.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.34.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 19:04:54 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2017-11-12 (58 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.21 /org/gtk/gvfs/exec_spaw/4
  SegvAnalysis:
   Segfault happened at: 0x7fd0a85315a9:mov0x18(%rax),%rax
   PC (0x7fd0a85315a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1742287/+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 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

2018-01-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1735798

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

Status in network-manager package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my
  school's VPN, and I am unable to get on mygateway or even the school's
  main website after I disconnect from the VPN or the computer sleeps
  after the VPN has been started. It uses EAP authentication.

  Here is the log after connecting once, turning off, and restarting:
  LOG:
  POST https://vpn.myschool.edu/
  getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
  Failed to open HTTPS connection to vpn.myschool.edu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto static metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735798/+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 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.

2018-01-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: openconnect (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1735798

Title:
  Unable to access any subdomain provided by VPN provider until reboot.

Status in network-manager package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting from VPN, ubuntu is unable to reconnect to the VPN
  and any domain hosted by the server. For reference, this is my
  school's VPN, and I am unable to get on mygateway or even the school's
  main website after I disconnect from the VPN or the computer sleeps
  after the VPN has been started. It uses EAP authentication.

  Here is the log after connecting once, turning off, and restarting:
  LOG:
  POST https://vpn.myschool.edu/
  getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known
  Failed to open HTTPS connection to vpn.myschool.edu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  1 11:39:56 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-02 (364 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0 proto static metric 600
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735798/+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 1742280] [NEW] nvidia-340 340.104-0ubuntu2: nvidia-340 kernel module failed to build

2018-01-09 Thread Peter M Spreemann
Public bug reported:

error occured during normal system update with the standard Software-Update 
Tool. 
Havn't done anything unusual during Update.
Kodi 17.6 was up and waiting to start something in Main-Menue on 3rd virtual 
Desktop during Update.

Going to reboot the system after this Kernel Update and see what
happens.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: nvidia-340 340.104-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
Uname: Linux 4.13.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
DKMSKernelVersion: 4.13.0-24-generic
Date: Tue Jan  9 21:39:15 2018
InstallationDate: Installed on 2015-05-04 (981 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageVersion: 340.104-0ubuntu2
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.104-0ubuntu2: nvidia-340 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful third-party-packages

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1742280

Title:
  nvidia-340 340.104-0ubuntu2: nvidia-340 kernel module failed to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  error occured during normal system update with the standard Software-Update 
Tool. 
  Havn't done anything unusual during Update.
  Kodi 17.6 was up and waiting to start something in Main-Menue on 3rd virtual 
Desktop during Update.

  Going to reboot the system after this Kernel Update and see what
  happens.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-340 340.104-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Tue Jan  9 21:39:15 2018
  InstallationDate: Installed on 2015-05-04 (981 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageVersion: 340.104-0ubuntu2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.104-0ubuntu2: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1742280/+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 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0

2018-01-09 Thread fermulator
since upgrading to Ubuntu 17.04, I'm unable to reproduce the crash any
longer FYI.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1739525

Title:
  gnome-shell segfault at e8 in libgdk-3.so.0

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As requested by vanvugt in #1580605, submitting a crash unique to my
  user.

  This isn't fun, several times per day a crash:
  {{{
  $ dmesg -T | grep seg
  [Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip 
7fd954f6d6a2 sp 7ffe04425eb8 error 4 in 
libgdk-3.so.0.1800.9[7fd954f3+d4000]
  [Thu Nov 9 10:11:16 2017] dota2[22006]: segfault at 0 ip 7fef2866683a sp 
7fff560539a0 error 6 in libtier0.so[7fef2863+8]
  [Thu Nov 9 13:04:18 2017] gnome-shell[1356]: segfault at e8 ip 
7f15ccddd6a2 sp 7fff9ecf47f8 error 4 in 
libgdk-3.so.0.1800.9[7f15ccda+d4000]
  [Thu Nov 9 17:16:45 2017] gnome-shell[14440]: segfault at e8 ip 
7f196afdd6a2 sp 7ffea13b5948 error 4 in 
libgdk-3.so.0.1800.9[7f196afa+d4000]
  [Thu Nov 9 17:16:52 2017] dconf worker[18015]: segfault at 52c ip 
004a133c sp 7f351f7e6170 error 4 in perl[40+1cf000]
  [Thu Nov 9 20:35:24 2017] gnome-shell[32271]: segfault at e8 ip 
7fd6ef0256a2 sp 7ffebb0d3608 error 4 in 
libgdk-3.so.0.1800.9[7fd6eefe8000+d4000]
  [Thu Nov 9 20:42:09 2017] gnome-shell[11070]: segfault at 23 ip 
7fc2bd8687bf sp 7fffcc3bc680 error 4 in 
libgnome-desktop-3.so.12.0.0[7fc2bd848000+39000]
  [Thu Nov 9 23:13:09 2017] gnome-shell[24832]: segfault at 6 ip 
7fb95e624818 sp 7ffc656ced30 error 4 in 
libgio-2.0.so.0.4800.2[7fb95e56+18]
  [Thu Nov 9 23:51:17 2017] gnome-shell[3253]: segfault at e8 ip 
7f2d1f4756a2 sp 7fff455b3128 error 4 in 
libgdk-3.so.0.1800.9[7f2d1f438000+d4000]
  [Fri Nov 10 01:09:27 2017] gnome-shell[31134]: segfault at e8 ip 
7f3b923756a2 sp 7fff91dea558 error 4 in 
libgdk-3.so.0.1800.9[7f3b92338000+d4000]
  [Fri Nov 10 01:12:43 2017] gnome-shell[9188]: segfault at e8 ip 
7f683370d6a2 sp 7ca20198 error 4 in 
libgdk-3.so.0.1800.9[7f68336d+d4000]
  [Fri Nov 10 03:40:54 2017] gnome-shell[25978]: segfault at e8 ip 
7f8af06ed6a2 sp 7ffdf3c5cfc8 error 4 in 
libgdk-3.so.0.1800.9[7f8af06b+d4000]
  [Sat Nov 11 00:49:59 2017] gnome-shell[31566]: segfault at e8 ip 
7ffab7ae56a2 sp 7fff76561338 error 4 in 
libgdk-3.so.0.1800.9[7ffab7aa8000+d4000]
  [Sat Nov 11 20:01:10 2017] gnome-shell[23459]: segfault at e8 ip 
7f6a4c1dd6a2 sp 7ffdfcd62008 error 4 in 
libgdk-3.so.0.1800.9[7f6a4c1a+d4000]
  [Sat Nov 11 21:05:36 2017] gnome-shell[28874]: segfault at e8 ip 
7f48523d56a2 sp 7ffd15fbc738 error 4 in 
libgdk-3.so.0.1800.9[7f4852398000+d4000]
  }}}

  My setup:
   * Dual monitors
   * OFTEN switch between users
  a) using the GDM3 "switch user" GUI
  b) using CTRL+ALT+FXX quick flips
   * Daily I suspend the system and resume (Power Management)

  Versions
  {{{
  $ cat /etc/issue
  Ubuntu 16.04.3 LTS \n \l

  $ uname -a
  Linux  4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  
  $ dpkg --list | grep gnome-shell
  ii  chrome-gnome-shell  
9-0ubuntu1~ubuntu16.04.3 all  GNOME Shell 
extensions integration for web browsers
  ii  gnome-shell 
3.18.5-0ubuntu0.3amd64graphical shell for 
the GNOME desktop
  ii  gnome-shell-common  
3.18.5-0ubuntu0.3all  common files for the 
GNOME graphical shell
  ii  gnome-shell-timer   
0.3.12+20140924-3all  GNOME Shell extension 
providing a countdown timer in the top panel

  $ dpkg --list | grep libgdk
  ii  libgdk-pixbuf2.0-0:amd64
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
  ii  libgdk-pixbuf2.0-0:i386 
2.32.2-1ubuntu1.3i386 GDK Pixbuf library
  ii  libgdk-pixbuf2.0-common 
2.32.2-1ubuntu1.3all  GDK Pixbuf library - 
data files
  ii  libgdk-pixbuf2.0-dev
2.32.2-1ubuntu1.3amd64GDK Pixbuf library 
(development files)
  }}}

  Some random snippet:
  {{{
   Dec 6 21:47:44 fermmy gnome-session[9885]: (gnome-shell:10011): Gtk-CRITICAL 
**: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed
  Dec 6 21:47:44 fermmy kernel: [225347.940591] gnome-shell[10011]: segfault at 
e8 ip 7f6d239876a2 sp 7ffcebaa54b8 error 4 in 

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

2018-01-09 Thread Timo Aaltonen
PPA builders are unfortunately still offline because of SPECTRE :(

One quick workaround for this issue is to downgrade to stock 16.04
xserver and install x-x-v-intel:

sudo apt install --install-recommends xserver-xorg xserver-xorg-video-
all xserver-xorg-input-all xserver-xorg-video-intel

that should do it.. it'll remove a bunch of packages named -hwe-16.04
and replace them with the stock packages.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741588] Re: Categories in Ubuntu Software don't work

2018-01-09 Thread Robert Ancell
Thanks for the clarification!

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1741588

Title:
  Categories in Ubuntu Software don't work

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I'm a developer on the Polarr team for Linux, and users should be able
  to find the Polarr app under the Photography category of the Ubuntu
  Software store.

  I attached a screenshot of the Photography category in the Ubuntu
  16.04 Software store. The other categories are similarly non-
  functional.

  As you can see, there are only ellipses where there should be icons
  and descriptive text for each of the photography applications.
  Clicking on the items doesn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-software 3.20.5-0ubuntu0.16.04.7
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  4 10:41:25 2018
  InstallationDate: Installed on 2017-12-19 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1741588/+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 1726156] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from construct

2018-01-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1726156

Title:
  gnome-shell-portal-helper crashed with SIGABRT in
  g_assertion_message() from g_assertion_message_expr("assertion failed:
  (priv->label_box == NULL)") from construct_label_box()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell-portal-helper crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 17:19:12 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  InstallationDate: Installed on 2017-06-08 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726156/+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 1726156] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from construct

2018-01-09 Thread Apport retracing service
** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1726156

Title:
  gnome-shell-portal-helper crashed with SIGABRT in
  g_assertion_message() from g_assertion_message_expr("assertion failed:
  (priv->label_box == NULL)") from construct_label_box()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell-portal-helper crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 17:19:12 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  InstallationDate: Installed on 2017-06-08 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726156/+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 1742268] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()

2018-01-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1726156 ***
https://bugs.launchpad.net/bugs/1726156

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1726156, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1742268/+attachment/5033674/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1742268/+attachment/5033676/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1742268/+attachment/5033680/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1742268/+attachment/5033681/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1742268/+attachment/5033682/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742268/+attachment/5033683/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742268/+attachment/5033684/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1726156
   gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() from 
g_assertion_message_expr("assertion failed: (priv->label_box == NULL)") from 
construct_label_box()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1742268

Title:
  gnome-shell-portal-helper crashed with SIGABRT in
  g_assertion_message()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  nothing to say, apport triggered this but all is OK.
  Best regards and thanks

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  Uname: Linux 4.15.0-999-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 20:45:36 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'torbrowser.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Screenshot.desktop', 
'gimp.desktop', 'libreoffice-writer.desktop', 'org.gnome.gedit.desktop', 
'google-chrome.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-10-30 (436 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to bionic on 2018-01-08 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742268/+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 1741588] Re: Categories in Ubuntu Software don't work

2018-01-09 Thread dmiller309
Polarr is a Snap, but the bug I intended to report here is that on
16.04, none of the items in the category list display or are clickable.
The screenshot attached to the original bug report illustrates the
problem. I couldn't say for sure whether Polarr is in the list or not
because each of the apps display as a box with an ellipsis inside: no
icon or text. One weird thing I when switching between categories is
that none of the items in the list for each category render or are
clickable, but there are different amounts of items in each category. I
know I had an internet connection because I was on a video call.

During a demo of the new Polarr Snap I was asked whether the Polarr Snap
is in the Software Store and if it showed up under the Graphics
category. I could bring up Polarr by searching for it directly. It was
kind of embarrassing though when none of the categories in the store
worked. We link our existing users to our snapcraft.io/polarr page, but
we're not featured, the categories were broken on 16.04, and we don't
show up under categories on 17.10, so there is currently no way for new
users to find Polarr in the Software Store.

Thanks for your patience, I know that y'all have a lot of work to do
with all the new Snaps coming out. I've seen categories in the Software
Store work before and maybe this is just a temporary regression; I just
wanted to share this in case you weren't aware of the problem.

-- 
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/1741588

Title:
  Categories in Ubuntu Software don't work

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I'm a developer on the Polarr team for Linux, and users should be able
  to find the Polarr app under the Photography category of the Ubuntu
  Software store.

  I attached a screenshot of the Photography category in the Ubuntu
  16.04 Software store. The other categories are similarly non-
  functional.

  As you can see, there are only ellipses where there should be icons
  and descriptive text for each of the photography applications.
  Clicking on the items doesn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-software 3.20.5-0ubuntu0.16.04.7
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  4 10:41:25 2018
  InstallationDate: Installed on 2017-12-19 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1741588/+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 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

2018-01-09 Thread RégisC
Hi Sebastien,

I think https://bugzilla.gnome.org/show_bug.cgi?id=706688 could be used
as the upstream bug.

Regards

** Bug watch added: GNOME Bug Tracker #706688
   https://bugzilla.gnome.org/show_bug.cgi?id=706688

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730458

Title:
  Ubuntu (gnome) freezes temporarily upon login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have noticed that gnome-shell CPU usage shoots up to over 100% for a
  few seconds shortly after logging in, completely freezing the shell
  for a good 10-20s.

  This happens on a migrated Unity 7 > Ubuntu session as well as on a
  completely new Ubuntu session (eg a user just created to test this).

  Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:05:45 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

2018-01-09 Thread Janghou
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

@laurel, to find your version, try in a terminal
 lsb_release -a

If you have further questions for support or how to deal with his matter, 
please read:
https://askubuntu.com/questions/992571/gui-unity-crashing-in-16-04-lts-after-latest-updates-compiz-segfaults

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741447

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 

[Desktop-packages] [Bug 433926] Re: xkbcomp error: Type "ONE_LEVEL" has 1 levels, but has 2 symbols

2018-01-09 Thread Gunnar Hjalmarsson
On 2018-01-09 18:45, H.-Dirk Schmitt wrote:
> Still in xenial
> affected: xkb-data 2.16-1ubuntu1
> 
> │Jan  8 11:49:55 user.warning /usr/lib/gdm3/gdm-x-session[3463 >
> Warning:  Type "ONE_LEVEL" has 1 levels, but  has 2 │

This seems to be an old one. If I understand it correctly, Sergey posted
a suggestion in comment #17, but got no feedback. Can someone who is
affected provide some feedback to that suggestion?

Please note that this is not important enough to update 16.04 or any
other stable release. However, if the change would be committed
upstream, it might make it into Ubuntu 18.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/433926

Title:
  xkbcomp error: Type "ONE_LEVEL" has 1 levels, but  has 2 symbols

Status in xkeyboard-config:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I can confirm that the bug reported upstream is also present in Karmic alpha 
6:
  https://bugs.freedesktop.org/show_bug.cgi?id=21761

  This bug was also reported in gentoo
  http://bugs.gentoo.org/show_bug.cgi?id=269931

  and in debian
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291853

  Apparently a fix was released upstream, it would be nice to have it in
  Karmic as well.

  Many thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/433926/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

2018-01-09 Thread Angel González
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

ppa:paulo-miguel-dias/pkppa works for me too

No more issues

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741447

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1741925] Re: Unity launcher disappears on mouse-over launcher

2018-01-09 Thread Bruce MacAlister
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

Answers:
Do you have an additional monitor connected? NO What is the display resolution 
you use? 12??X800 Do things still crash if you change the resolution to 
something smaller than the native NO

Thank you for your direction. In attempt to narrow the failure down I examined 
the two visible symptoms:
1. Mouse-over the launcher causes the launcher and the task line at the top to 
disappear
2. There appears to be a recovery time of 10 to 30 seconds and then the 
launcher and all reappear
The most likely culprits appear to be:
1. Mouse software; I assume that is part of the Lunux kernel. I was unable to 
find any information on the Ubuntu software stack or architecture so I could 
not identify the process(es) used for the mouse.
To evaluate mouse malfunction I (a) tried both the laptop’s mouse-pad and a USB 
mouse with no difference in behavior and (b) did a mouse-over of some Linux 
apps where the button or widget reacts to a mouse-over; the mouse-over behavior 
worked as expected.
My conclusion is that the mouse and the mouse code is behaving properly.
2. Launcher code; without a software stack the name of the process is 
unknowable. Doing a query in the System Monitor gave a likely 
“api-spi-bus-launcher” (see that attached image, “Launcher properties  
2018-01-09 12-44-12.png”).
An strace on that pid
sudo strace -p 1488 -b execve -o launcher.txt
[sudo] password for bruce: 
yielded
   restart_syscall(<... resuming interrupted poll ...>) = 1
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1
I do not know how to read strace output. The “restart_syscall” line looks 
suspiciously like an error recover execution.
The launcher disappearance behavior is captured in two images, before the 
failure “Launcher failure a 2018-01-09 12-23-23.png” and during recovery 
“Launcher failure b 2018-01-09 12-24-39.png”. They are 
attached.?field.comment=Answers:
Do you have an additional monitor connected? NO What is the display resolution 
you use? 12??X800 Do things still crash if you change the resolution to 
something smaller than the native NO

Thank you for your direction. In attempt to narrow the failure down I examined 
the two visible symptoms:
1. Mouse-over the launcher causes the launcher and the task line at the top to 
disappear
2. There appears to be a recovery time of 10 to 30 seconds and then the 
launcher and all reappear
The most likely culprits appear to be:
1. Mouse software; I assume that is part of the Lunux kernel. I was unable to 
find any information on the Ubuntu software stack or architecture so I could 
not identify the process(es) used for the mouse.
To evaluate mouse malfunction I (a) tried both the laptop’s mouse-pad and a USB 
mouse with no difference in behavior and (b) did a mouse-over of some Linux 
apps where the button or widget reacts to a mouse-over; the mouse-over behavior 
worked as expected.
My conclusion is that the mouse and the mouse code is behaving properly.
2. Launcher code; without a software stack the name of the process is 
unknowable. Doing a query in the System Monitor gave a likely 
“api-spi-bus-launcher” (see that attached image, “Launcher properties  
2018-01-09 12-44-12.png”).
An strace on that pid
sudo strace -p 1488 -b execve -o launcher.txt
[sudo] password for bruce: 
yielded
   restart_syscall(<... resuming interrupted poll ...>) = 1
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, 
revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1
I do not know how to read strace output. The “restart_syscall” line looks 
suspiciously like an error recover execution.
The launcher disappearance behavior is captured in two images, before the 
failure “Launcher failure a 2018-01-09 12-23-23.png” and during recovery 
“Launcher failure b 2018-01-09 12-24-39.png”. They are attached.

** Attachment added: "before launcher failur"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741925/+attachment/5033648/+files/Launcher%20failure%20a%202018-01-09%2012-23-23.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741925

Title:
  Unity launcher disappears on mouse-over launcher

Status in mesa package in Ubuntu:
  New

Bug 

[Desktop-packages] [Bug 1742251] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de

2018-01-09 Thread Henrique Ferreira
Public bug reported:

I tried to install brazillian bank security module, but I can't.
Show error: dconf-waring and dconf-critical

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Jan  9 14:58:23 2018
ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
InstallationDate: Installed on 2018-01-09 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1742251

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: a tentar sobreescrever
  '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras
  instâncias do pacote libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I tried to install brazillian bank security module, but I can't.
  Show error: dconf-waring and dconf-critical

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Jan  9 14:58:23 2018
  ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
  InstallationDate: Installed on 2018-01-09 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1742251/+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 1742243] [NEW] Please merge with Debian unstable 2.2.0-11.1

2018-01-09 Thread Nish Aravamudan
Public bug reported:

TBD

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to openexr in Ubuntu.
https://bugs.launchpad.net/bugs/1742243

Title:
  Please merge with Debian unstable 2.2.0-11.1

Status in openexr package in Ubuntu:
  New

Bug description:
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1742243/+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 433926] Re: xkbcomp error: Type "ONE_LEVEL" has 1 levels, but has 2 symbols

2018-01-09 Thread H.-Dirk Schmitt
Still in xenial
affected: xkb-data 2.16-1ubuntu1 

│Jan  8 11:49:55 user.warning /usr/lib/gdm3/gdm-x-session[3463 >
Warning:  Type "ONE_LEVEL" has 1 levels, but  has 2 │

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/433926

Title:
  xkbcomp error: Type "ONE_LEVEL" has 1 levels, but  has 2 symbols

Status in xkeyboard-config:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  I can confirm that the bug reported upstream is also present in Karmic alpha 
6:
  https://bugs.freedesktop.org/show_bug.cgi?id=21761

  This bug was also reported in gentoo
  http://bugs.gentoo.org/show_bug.cgi?id=269931

  and in debian
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291853

  Apparently a fix was released upstream, it would be nice to have it in
  Karmic as well.

  Many thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/433926/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2018-01-09 Thread Norbert
synaptic confirmed on 18.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2018-01-09 Thread Norbert
Problem with `nemo` "Open as Root" is confirmed on 18.04.

** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage 

[Desktop-packages] [Bug 1693464] Re: Bluetooth Audio broken for Bose SoundLink Mini

2018-01-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1693464

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1693464/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

2018-01-09 Thread laurel
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

I'm a newbie and after updating Ubuntu 16.04 on Jan 5, 2018, I
experienced launcher disappearing when running over with mouse, windows
disappearing and appearing, Dash not working and cannot shutdown.  I get
Internal Error Message: compiz crashed with SIGSERV.  The error report
incorrectly prints that I have amd64 architecture and that I have Ubuntu
16.04.2 LTS Release amd64 (20170215.2) when I have Ubuntu 16.04.3  This
result seems not to have been commented on in the previous bug #1735594.

I'm working on a Toshiba Satellite M645 laptop (2011) with an Intel Core
i5 CPU, 64 bit OS and graphics is Intel Ironlake Mobile.

I'm afraid to try the ppa:paulo-miguel-dias/pkppa suggestion because I
am so new to this.  I installed  August 2017 and had no problems until
Jan 5, 2018 when using the Software Updater.

The good news is: I learned to use terminal commands and can access all
the browsers, word processors, files, etc. that I have on my machine so
I'm not down just inconvenienced. Thanks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741447

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1530323] Re: The input box for editing a Wired connection static IP address doesn't appear correctly

2018-01-09 Thread Qazi Omair Ahmed
Please elaborate your Description. There should be the steps to
reproduce the  bug, expected result, actual result, and the notes.
Please do so, so that the developer team looks to the bug and fixes this
at the earliest.

Thanks,
Qazi Omair Ahmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1530323

Title:
  The input box for editing a Wired connection static IP address doesn't
  appear correctly

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Configuration:
  PC: Dell-Vostro-260s
  OS: UK16.04-1230-Daily-amd64
  APP: network-manager-gnome

  The input box for IP doesn't appear correctly in the edit window of
  Wired connection.

  在有线网络连接编辑页面进行手动配置网络时,IP地址设置栏由于输入框过大,输入过程中无法显示全键入数字,最大化后可正常查看。

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1530323/+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 1429796] Re: Pidgin Crashes when opened from Application Launcher Menu

2018-01-09 Thread Qazi Omair Ahmed
Thanks for the bug! I reported this bug to the Pidgin Upstream Bug
Tracker (https://developer.pidgin.im/ticket/17279#ticket)

** Bug watch added: Pidgin Trac #17279
   http://developer.pidgin.im/ticket/17279

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1429796

Title:
  Pidgin Crashes when opened from Application Launcher Menu

Status in Torchat:
  New
Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE
  ---

  1. Open Pidgin from the Application Launcher Menu.

  EXPECTED RESULT
  

  Pidgin starts without any problems.

  ACTUAL RESULT
  

  Pidgin Crashes.

  NOTES
  --

  Lubuntu 15.04
  Pidgin 2.10.9 (libpurple 2.10.9)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: pidgin 1:2.10.9-0ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Mon Mar  9 12:02:45 2015
  ExecutablePath: /usr/bin/pidgin
  InstallationDate: Installed on 2013-03-16 (723 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcCmdline: pidgin
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to vivid on 2015-02-27 (9 days ago)
  UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video
  ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2013-03-16 (786 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  Package: pidgin 1:2.10.9-0ubuntu8
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Tags:  vivid
  Uname: Linux 3.19.0-16-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/torchat/+bug/1429796/+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 1429796] Re: Pidgin crash on start

2018-01-09 Thread Qazi Omair Ahmed
** Description changed:

- When i start pigin from menu it crash.
+ STEPS TO REPRODUCE
+ ---
+ 
+ 1. Open Pidgin from the Application Launcher Menu.
+ 
+ EXPECTED RESULT
+ 
+ 
+ Pidgin starts without any problems.
+ 
+ ACTUAL RESULT
+ 
+ 
+ Pidgin Crashes.
+ 
+ NOTES
+ --
  
  Lubuntu 15.04
  Pidgin 2.10.9 (libpurple 2.10.9)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: pidgin 1:2.10.9-0ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Mon Mar  9 12:02:45 2015
  ExecutablePath: /usr/bin/pidgin
  InstallationDate: Installed on 2013-03-16 (723 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcCmdline: pidgin
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to vivid on 2015-02-27 (9 days ago)
  UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video
- --- 
+ ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2013-03-16 (786 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  Package: pidgin 1:2.10.9-0ubuntu8
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Tags:  vivid
  Uname: Linux 3.19.0-16-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video
  _MarkForUpload: True

** Summary changed:

- Pidgin crash on start
+ Pidgin Crashes when opened from Application Launcher Menu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1429796

Title:
  Pidgin Crashes when opened from Application Launcher Menu

Status in Torchat:
  New
Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE
  ---

  1. Open Pidgin from the Application Launcher Menu.

  EXPECTED RESULT
  

  Pidgin starts without any problems.

  ACTUAL RESULT
  

  Pidgin Crashes.

  NOTES
  --

  Lubuntu 15.04
  Pidgin 2.10.9 (libpurple 2.10.9)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: pidgin 1:2.10.9-0ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Mon Mar  9 12:02:45 2015
  ExecutablePath: /usr/bin/pidgin
  InstallationDate: Installed on 2013-03-16 (723 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcCmdline: pidgin
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to vivid on 2015-02-27 (9 days ago)
  UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video
  ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2013-03-16 (786 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  Package: pidgin 1:2.10.9-0ubuntu8
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Tags:  vivid
  Uname: Linux 3.19.0-16-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/torchat/+bug/1429796/+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 1726853] Re: system-config-printer.py crashed with TypeError in get_authentication(): update expected at most 1 arguments, got 2

2018-01-09 Thread Christopher Boehm
Any progress with this? I can't print anything at all.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1726853

Title:
  system-config-printer.py crashed with TypeError in
  get_authentication(): update expected at most 1 arguments, got 2

Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  After changing my NT domain passowrd, got NT_STATUS_ACCESS_DENIED when
  trying to print something to samba printer.

  Rather than prompting for a new password, system-config-printer just
  crash...

  not sure this is really link to my password update as I upgrade my
  system from 17.04 to 17.10 as the same time...

  
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy system-config-printer
  system-config-printer:
Installed: 1.5.9+20170825-0ubuntu1
Candidate: 1.5.9+20170825-0ubuntu1
Version table:
   *** 1.5.9+20170825-0ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://ch.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: system-config-printer 1.5.9+20170825-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Tue Oct 24 14:34:30 2017
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationDate: Installed on 2016-05-03 (539 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterpreterPath: /usr/bin/python3.6
  Lpstat:
   device for DCP9020CDW: 
dnssd://Brother%20DCP-9020CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055c0d34df
   device for FollowMe: smb://print/FOLLOWME_PS
   device for HP-Officejet-4630: socket://192.168.1.116:9100
   device for HP_Officejet_4630_series_AD35AD: 
dnssd://HP%20Officejet%204630%20series%20%5BAD35AD%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d0bf9cad35ad
   device for KyoceraMda: socket://192.168.1.112:9100
  MachineType: LENOVO 20FAS11D00
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DCP9020CDW.ppd', 
'/etc/cups/ppd/HP_Officejet_4630_series_AD35AD.ppd', 
'/etc/cups/ppd/HP-Officejet-4630.ppd', '/etc/cups/ppd/KyoceraMda.ppd', 
'/etc/cups/ppd/FollowMe.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DCP9020CDW.ppd: Permission denied
   grep: /etc/cups/ppd/HP_Officejet_4630_series_AD35AD.ppd: Permission denied
   grep: /etc/cups/ppd/HP-Officejet-4630.ppd: Permission denied
   grep: /etc/cups/ppd/KyoceraMda.ppd: Permission denied
   grep: /etc/cups/ppd/FollowMe.ppd: Permission denied
  ProcCmdline: /usr/bin/python3 
/usr/share/system-config-printer/system-config-printer.py
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency 
root=UUID=5cbe7176-d524-4b66-8e26-e53e6f331691 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: system-config-printer
  Title: system-config-printer.py crashed with TypeError in 
get_authentication(): update expected at most 1 arguments, got 2
  UpgradeStatus: Upgraded to artful on 2017-10-21 (2 days ago)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev postgres sambashare 
sudo vboxusers
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET37W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS11D00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET37W(1.05):bd01/15/2016:svnLENOVO:pn20FAS11D00:pvrThinkPadT460s:rvnLENOVO:rn20FAS11D00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS11D00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1726853/+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 1741768] Re: U2F FIDO authentication doesn't work

2018-01-09 Thread Antoine Pitrou
Hi jc-moz,

I initially thought so, but switched AppArmor to complain mode (rather
than enforce) and got the same results (also the Mozilla-built Chromium
works fine).  Current AppArmor status:

$ sudo apparmor_status
[...]
17 processes have profiles defined.
9 processes are in enforce mode.
   /sbin/dhclient (2869) 
   /usr/sbin/cups-browsed (7130) 
   /usr/sbin/cupsd (7125) 
   /usr/sbin/dnsmasq (3073) 
   /usr/sbin/dnsmasq (3074) 
   /usr/sbin/dnsmasq (3089) 
   /usr/sbin/dnsmasq (3393) 
   /usr/sbin/libvirtd (2495) 
   /usr/sbin/ntpd (4833) 
8 processes are in complain mode.
   /usr/lib/firefox/firefox{,*[^s][^h]} (7492) 
   /usr/lib/firefox/firefox{,*[^s][^h]} (7544) 
   /usr/lib/firefox/firefox{,*[^s][^h]} (7702) 
   /usr/lib/firefox/firefox{,*[^s][^h]} (19925) 
   /usr/lib/firefox/firefox{,*[^s][^h]} (19963) 
   /usr/sbin/avahi-daemon (2145) 
   /usr/sbin/avahi-daemon (2199) 
   /usr/sbin/nmbd (3616) 


There may be something else than AppArmor going on, but I don't know what.  Do 
you have any idea?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1741768

Title:
  U2F FIDO authentication doesn't work

Status in firefox package in Ubuntu:
  New

Bug description:
  I have a Yubico U2F security key.  If I download the upstream Firefox
  binary for 57.0.4 and go to https://demo.yubico.com/u2f?tab=register,
  the test page works fine: I can register with a username/password, my
  key starts blinking and I can touch it to validate.

  If I go to the same page using the official Ubuntu package of Firefox,
  the U2F device is not recognized and the page displays the following
  error:

  """
  Registration failed!

  Make sure you have a U2F device connected, and try again.

   Traceback (most recent call last):
File "/root/python-u2flib-server-demo/examples/yubiauth_server.py", line 
161, in __call__
  raise Exception("FIDO Client error: %s" % error)
  Exception: FIDO Client error: 1 (OTHER ERROR)
  """

  Note that in both cases, I did enable the required options in
  "about:config" (as outlined in e.g. https://www.yubico.com/2017/11
  /how-to-navigate-fido-u2f-in-firefox-quantum/).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 57.0.4+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antoine3844 F pulseaudio
   /dev/snd/controlC1:  antoine3844 F pulseaudio
  BuildID: 20180104112904
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sun Jan  7 17:32:38 2018
  DefaultProfileIncompatibleExtensions: Default - 
{972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePrefErrors: 'utf-8' codec can't decode byte 0xe9 in position 
2410: invalid continuation byte
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-12 (1730 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409)
  MostRecentCrashID: bp-eb109c63-e3b5-4c21-a920-d262b2150407
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4PrefSources: prefs.js
  Profile4Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=57.0.4/20180104112904 (In use)
   Profile1 - LastVersion=57.0.4/20180104112904
   Profile2 - LastVersion=57.0.4/20180104112904
   Profile3 - LastVersion=57.0.3/20171227151400 (Out of date)
   Profile4 - LastVersion=57.0.4/20180104112904 (In 

[Desktop-packages] [Bug 1741768] Re: U2F FIDO authentication doesn't work

2018-01-09 Thread J.C. Jones
Hi, I'm one of the Firefox developers working on our FIDO U2F device
support.

Since this works with the Mozilla-built Firefox but not the Canonical
one, I think it's an AppArmor (or similar) setting prohibiting firefox
from reaching libudev or the udev device paths on disk.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1741768

Title:
  U2F FIDO authentication doesn't work

Status in firefox package in Ubuntu:
  New

Bug description:
  I have a Yubico U2F security key.  If I download the upstream Firefox
  binary for 57.0.4 and go to https://demo.yubico.com/u2f?tab=register,
  the test page works fine: I can register with a username/password, my
  key starts blinking and I can touch it to validate.

  If I go to the same page using the official Ubuntu package of Firefox,
  the U2F device is not recognized and the page displays the following
  error:

  """
  Registration failed!

  Make sure you have a U2F device connected, and try again.

   Traceback (most recent call last):
File "/root/python-u2flib-server-demo/examples/yubiauth_server.py", line 
161, in __call__
  raise Exception("FIDO Client error: %s" % error)
  Exception: FIDO Client error: 1 (OTHER ERROR)
  """

  Note that in both cases, I did enable the required options in
  "about:config" (as outlined in e.g. https://www.yubico.com/2017/11
  /how-to-navigate-fido-u2f-in-firefox-quantum/).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 57.0.4+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antoine3844 F pulseaudio
   /dev/snd/controlC1:  antoine3844 F pulseaudio
  BuildID: 20180104112904
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sun Jan  7 17:32:38 2018
  DefaultProfileIncompatibleExtensions: Default - 
{972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePrefErrors: 'utf-8' codec can't decode byte 0xe9 in position 
2410: invalid continuation byte
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-12 (1730 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409)
  MostRecentCrashID: bp-eb109c63-e3b5-4c21-a920-d262b2150407
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4PrefSources: prefs.js
  Profile4Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=57.0.4/20180104112904 (In use)
   Profile1 - LastVersion=57.0.4/20180104112904
   Profile2 - LastVersion=57.0.4/20180104112904
   Profile3 - LastVersion=57.0.3/20171227151400 (Out of date)
   Profile4 - LastVersion=57.0.4/20180104112904 (In use)
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to xenial on 2015-07-27 (894 days ago)
  dmi.bios.date: 06/22/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Desktop-packages] [Bug 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfuti

2018-01-09 Thread Videonauth
Here a link to the new regression. not sure if this belongs here or not
so i submitted it singlestanding:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-384/+bug/1742160

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1741914

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

2018-01-09 Thread Timo Aaltonen
** Summary changed:

- [regression] compiz crashes when hovering over sidebar
+ [regression] compiz crashes after Mesa upgrade

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfuti

2018-01-09 Thread Videonauth
Yes, sadly now the NVidia Driver 384.90 (I still wonder where you get
the 384.111 on artful) fails still to build even after the released fix.
But this time with a different message and build log. And without
showing me an opportunity to report the bug (except using ubuntu-bug
command which will maybe not fetch all information).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1741914

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1735594] Re: [regression] compiz crashes when hovering over sidebar

2018-01-09 Thread Timo Aaltonen
** Description changed:

- When I use the Unity session I automatically get logged out under these
- conditions:
+ [Impact]
+ When I use the Unity session I automatically get logged out under these 
conditions:
  
  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.
  
  running dmesg after this unwanted logout happens I get following
  information:
  
  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]
  
- The info about my installed compiz:
+ This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
+ - gen4 / gen5 Intel
+ - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)
  
- compiz:
-   Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1
-   Candidat:   1:0.9.13.1+17.10.20170901-0ubuntu1
-   Taula de versió:
-  *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
- 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
- 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages
- 100 /var/lib/dpkg/status
+ [Test case]
+ Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.
+ 
+ [Regression potential]
+ The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).
+ 
+ Best to test on a wide array of Intel HW:
+ gen4 (965GM/GM45/G45)
+ gen5 (Ironlake)
+ gen6 (Sandy Bridge)
+ gen7 (Bay Trail, Ivy Bridge, Haswell)
+ gen8 (Braswell, Broadwell)
+ gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594

Title:
  [regression] compiz crashes when hovering over sidebar

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1742156] [NEW] network-manager wired DHCP mode doesn't work on Ubuntu 18.04

2018-01-09 Thread Cui Wei
Public bug reported:

In virtualbox with NAT configured (10.0.2.2 as defaul DHCP IP), network-
manager on ubuntu 18.04 cannot find any wired interface and also cannot
connect to network via DHCP.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager (not installed)
ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
Uname: Linux 4.14.0-15-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Jan  9 21:44:54 2018
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1742156

Title:
  network-manager wired DHCP mode doesn't work on Ubuntu 18.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  In virtualbox with NAT configured (10.0.2.2 as defaul DHCP IP),
  network-manager on ubuntu 18.04 cannot find any wired interface and
  also cannot connect to network via DHCP.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager (not installed)
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jan  9 21:44:54 2018
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1742156/+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 1735594] Re: [regression] compiz crashes when hovering over sidebar

2018-01-09 Thread Timo Aaltonen
** Summary changed:

- ubuntu automatically logs out when hovering sidebar
+ [regression] compiz crashes when hovering over sidebar

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594

Title:
  [regression] compiz crashes when hovering over sidebar

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  When I use the Unity session I automatically get logged out under
  these conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  The info about my installed compiz:

  compiz:
    Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1
    Candidat:   1:0.9.13.1+17.10.20170901-0ubuntu1
    Taula de versió:
   *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

2018-01-09 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

** This bug has been marked a duplicate of bug 1735594
   ubuntu automatically logs out when hovering sidebar

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741447

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1739762] Re: Search list starts from beginning after going back to it

2018-01-09 Thread Bug Watch Updater
** Changed in: gnome-software
   Status: Unknown => Confirmed

** Changed in: gnome-software
   Importance: Unknown => Medium

-- 
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/1739762

Title:
  Search list starts from beginning after going back to it

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  New

Bug description:
  When I go back to the search results, the list starts from the
  beginning instead of the entry where I was.

  Steps:
  1. Search for anything
  2. A list of results appears
  3. Scroll down to an app and choose it
  4. Go back to the search list
  5. The list starts from the beginning

  Going back should get me to where I was, not to the beginning of the
  list.

  This is a regression from 3.20.5-0ubuntu0.16.04.7 in Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-software 3.26.1-0ubuntu2.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 13:45:10 2017
  InstallationDate: Installed on 2017-10-02 (80 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1739762/+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 1741925] Re: Unity launcher disappears on mouse-over launcher

2018-01-09 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

I was able to reproduce after all, marking as a dupe

** This bug has been marked a duplicate of bug 1735594
   ubuntu automatically logs out when hovering sidebar

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741925

Title:
  Unity launcher disappears on mouse-over launcher

Status in mesa package in Ubuntu:
  New

Bug description:
  Move the mouse over the launcher and the EVERYTHING on the desktop
  disappears for a few seconds. Only the wallpaper remains. Failed
  immediately after the latest update (installed by me on 5 Jan 2018)
  and a reboot. Reboot doesn't help.

  Launcher and the other desktop displays return after a 10 to 30 second
  pause. No disk activity is observed during recovery.

  "ClassicMenu Indicator" is installed and it is the only way to start
  an application.

  Executing the bug and then immediately examining all the /var/log logs
  showed no recorded error or incident in any log.

  uname -a = Linux bruce-Latitude-D630 4.10.0-42-generic
  #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686
  GNU/Linux

  Abridged hardware list from  sudo lshw
   
  description: Portable Computer
  product: Latitude D630
  vendor: Dell Inc.
  width: 32 bits
  capabilities: smbios-2.4 dmi-2.4
  configuration: boot=normal chassis=portable 
uuid=44454C4C-6E00-1039-8032-B2C04F376831
*-core
 description: Motherboard
 vendor: Dell Inc.
 physical id: 0
 serial: .2n927h1.  .
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A12
date: 06/20/2008
size: 64KiB
capacity: 1984KiB
capabilities: isa pci pcmcia pnp upgrade shadowing cdboot 
bootselect int13floppy720 int5printscreen int9keyboard int14serial int17printer 
int10video acpi usb agp smartbattery biosbootspecification netboot
   *-cpu
description: CPU
product: Intel(R) Core(TM)2 Duo CPU T7250  @ 2.00GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 6.15.13
serial: -06FD----
slot: Microprocessor
size: 2GHz
capacity: 2001MHz
width: 64 bits
clock: 200MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi 
flexpriority dtherm ida cpufreq
configuration: cores=2 enabledcores=2 id=0 threads=2
  *-cache:0
   description: L1 cache
   physical id: 700
   size: 32KiB
   capacity: 32KiB
   capabilities: internal write-back data
   configuration: level=1
  *-cache:1
   description: L2 cache
   physical id: 701
   size: 2MiB
   capacity: 2MiB
   clock: 66MHz (15.0ns)
   capabilities: pipeline-burst internal varies unified
   configuration: level=2
  *-logicalcpu:0
   description: Logical CPU
   physical id: 0.1
   width: 64 bits
   capabilities: logical
  *-logicalcpu:1
   description: Logical CPU
   physical id: 0.2
   width: 64 bits
   capabilities: logical
   *-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 2GiB
  *-bank:0
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 0
   serial: 07B02E7C
   slot: DIMM_A
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
  *-bank:1
   description: DIMM DDR Synchronous 667 MHz (1.5 ns)
   product: V916765G24QCFW-F5
   vendor: ProMOS/Mosel Vitelic
   physical id: 1
   serial: E9AE2E7D
   slot: DIMM_B
   size: 1GiB
   width: 64 bits
   clock: 667MHz (1.5ns)
   *-pci
description: Host bridge
product: Mobile PM965/GM965/GL960 Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@:00:00.0
version: 0c
width: 32 bits
clock: 33MHz

To manage notifications about 

[Desktop-packages] [Bug 1741874] Re: if I move the arrow to the Unity, all the unity disappear , only the background still appear , and all the action freezed

2018-01-09 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594

no need, marking as a duplicate

** This bug has been marked a duplicate of bug 1735594
   ubuntu automatically logs out when hovering sidebar

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741874

Title:
  if I move the arrow to the Unity, all the unity disappear ,only the
  background still appear ,and all the action freezed

Status in mesa package in Ubuntu:
  New

Bug description:
  My OS is Ubuntu 16.04 lts,and I upgrader last week (2018/01/07),and
  whe I restart my computer,if I move the mouse arrow to the lift Unity
  ,the OS will freeze,all the icon disappear,it keeps for one minutes,if
  the arrow touch the Unity again ,as the same issue would happen ,so I
  cant touch the Unity, now I use the cairo-dock and terminal to control
  my Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Jan  8 18:16:32 2018
  InstallationDate: Installed on 2017-09-19 (110 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741874/+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 1739762] Re: Search list starts from beginning after going back to it

2018-01-09 Thread Amr Ibrahim
** Bug watch added: GNOME Bug Tracker #792367
   https://bugzilla.gnome.org/show_bug.cgi?id=792367

** Also affects: gnome-software via
   https://bugzilla.gnome.org/show_bug.cgi?id=792367
   Importance: Unknown
   Status: Unknown

-- 
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/1739762

Title:
  Search list starts from beginning after going back to it

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  New

Bug description:
  When I go back to the search results, the list starts from the
  beginning instead of the entry where I was.

  Steps:
  1. Search for anything
  2. A list of results appears
  3. Scroll down to an app and choose it
  4. Go back to the search list
  5. The list starts from the beginning

  Going back should get me to where I was, not to the beginning of the
  list.

  This is a regression from 3.20.5-0ubuntu0.16.04.7 in Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-software 3.26.1-0ubuntu2.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 22 13:45:10 2017
  InstallationDate: Installed on 2017-10-02 (80 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1739762/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

2018-01-09 Thread Timo Aaltonen
This patch broke the DRI driver on older gen4/4.5/5 Intel HW, see bugs
1735594 and 1741447

I've backported five commits from upstream to fix this properly, at
least this backport doesn't crash on my HW anymore.

** Changed in: mesa (Ubuntu Xenial)
   Status: Fix Released => Triaged

** Changed in: mesa (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1727401

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  Triaged
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1735594] Re: ubuntu automatically logs out when hovering sidebar

2018-01-09 Thread Timo Aaltonen
The culprit is a patch added for bug 1727401, it needs to be replaced
with a larger set of backports from 17.3...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594

Title:
  ubuntu automatically logs out when hovering sidebar

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  When I use the Unity session I automatically get logged out under
  these conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  The info about my installed compiz:

  compiz:
    Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1
    Candidat:   1:0.9.13.1+17.10.20170901-0ubuntu1
    Taula de versió:
   *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1742152] [NEW] package libnm-gtk-common 1.2.6-0ubuntu0.16.04.4 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarl

2018-01-09 Thread Daniele Milana
Public bug reported:

nothing to describe. the system give me an alert about something went
wrong ...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libnm-gtk-common 1.2.6-0ubuntu0.16.04.4
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Mon Jan  8 06:31:23 2018
Dependencies:
 
ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-12-10 (29 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
IpRoute:
 default via 192.168.0.1 dev wlo1  proto static  metric 600 
 169.254.0.0/16 dev wlo1  scope link  metric 1000 
 192.168.0.0/24 dev wlo1  proto kernel  scope link  src 192.168.0.3  metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: network-manager-applet
Title: package libnm-gtk-common 1.2.6-0ubuntu0.16.04.4 failed to 
install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
NETGEAR 876f7075-99e7-46e2-8c09-6d425bea906e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1742152

Title:
  package libnm-gtk-common 1.2.6-0ubuntu0.16.04.4 failed to
  install/upgrade: il pacchetto si trova in uno stato di inconsistenza
  critico: è consigliato  installarlo nuovamente prima di tentare la
  configurazione.

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  nothing to describe. the system give me an alert about something went
  wrong ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnm-gtk-common 1.2.6-0ubuntu0.16.04.4
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Jan  8 06:31:23 2018
  Dependencies:
   
  ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-10 (29 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.0.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   192.168.0.0/24 dev wlo1  proto kernel  scope link  src 192.168.0.3  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: network-manager-applet
  Title: package libnm-gtk-common 1.2.6-0ubuntu0.16.04.4 failed to 
install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
NETGEAR 876f7075-99e7-46e2-8c09-6d425bea906e  

[Desktop-packages] [Bug 1742144] Re: Only noise on Buildin Audio headphone output

2018-01-09 Thread yoann
** Description changed:

  For a few weeks, as soon as I plug headphone or sound system to the Jack
- input, I just got lots of noise.
+ output, I just got lots of noise.
  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  root@kveikur:/var/log# uname -a
  Linux kveikur 4.14.12-041412-generic #201801051649 SMP Fri Jan 5 16:50:54 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  
  $ apt-cache policy alsa-utils
  alsa-utils:
-   Installed: 1.1.0-0ubuntu5
-   Candidate: 1.1.0-0ubuntu5
-   Version table:
-  *** 1.1.0-0ubuntu5 500
- 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.1.0-0ubuntu5
+   Candidate: 1.1.0-0ubuntu5
+   Version table:
+  *** 1.1.0-0ubuntu5 500
+ 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  $ apt-cache policy alsa-base
  alsa-base:
-   Installed: 1.0.25+dfsg-0ubuntu5
-   Candidate: 1.0.25+dfsg-0ubuntu5
-   Version table:
-  *** 1.0.25+dfsg-0ubuntu5 500
- 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 500 http://ch.archive.ubuntu.com/ubuntu xenial/main i386 Packages
- 100 /var/lib/dpkg/status
- 
+   Installed: 1.0.25+dfsg-0ubuntu5
+   Candidate: 1.0.25+dfsg-0ubuntu5
+   Version table:
+  *** 1.0.25+dfsg-0ubuntu5 500
+ 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 500 http://ch.archive.ubuntu.com/ubuntu xenial/main i386 Packages
+ 100 /var/lib/dpkg/status
  
  Here the information I have in syslog :
  
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
376480 bytes (2134 ms).
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: snd_pcm_dump():
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Its setup is:
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   stream   : CAPTURE
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   format   : S16_LE
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   subformat: STD
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   channels : 2
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   rate : 44100
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   msbits   : 16
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   buffer_size  : 16384
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_size  : 8192
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_time  : 185759
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_step  : 1
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   avail_min: 8192
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_event : 0
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   start_threshold  : -1
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   silence_threshold: 0
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   silence_size : 0
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   appl_ptr : 1113200
  Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   hw_ptr   : 1207320
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  

[Desktop-packages] [Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

2018-01-09 Thread Alexey Balmashnov
@Daniel

The above commands do bring me to a web-page, but there are no uploaded
relevant error reports, although I see them in /var/crash

** Attachment added: "/var/crash screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+attachment/5033441/+files/20180108_ls_var_crash.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1741886

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Upon physical disconnect/connect of a monitor (connected via HDMI)
  shell crashes with signal 11.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1

  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.

  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+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 1742144] [NEW] Only noise on Buildin Audio headphone output

2018-01-09 Thread yoann
Public bug reported:

For a few weeks, as soon as I plug headphone or sound system to the Jack
input, I just got lots of noise.

$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04
root@kveikur:/var/log# uname -a
Linux kveikur 4.14.12-041412-generic #201801051649 SMP Fri Jan 5 16:50:54 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy alsa-utils
alsa-utils:
  Installed: 1.1.0-0ubuntu5
  Candidate: 1.1.0-0ubuntu5
  Version table:
 *** 1.1.0-0ubuntu5 500
500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy alsa-base
alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu5
  Candidate: 1.0.25+dfsg-0ubuntu5
  Version table:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://ch.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status


Here the information I have in syslog :

Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
376480 bytes (2134 ms).
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: snd_pcm_dump():
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c: Its setup is:
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   stream   : CAPTURE
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   format   : S16_LE
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   subformat: STD
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   channels : 2
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   rate : 44100
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   msbits   : 16
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   buffer_size  : 16384
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_size  : 8192
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_time  : 185759
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_step  : 1
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   avail_min: 8192
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   period_event : 0
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   start_threshold  : -1
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   silence_threshold: 0
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   silence_size : 0
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   boundary : 4611686018427387904
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   appl_ptr : 1113200
Jan  9 14:01:38 kveikur pulseaudio[7801]: [alsa-source-ALC3266 Analog] 
alsa-util.c:   hw_ptr   : 1207320

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.14.12-041412-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  yoann  7801 F pulseaudio
 /dev/snd/controlC1:  yoann  7801 F pulseaudio
Date: Tue Jan  9 14:02:51 2018
InstallationDate: Installed on 2015-11-30 (770 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to 

Re: [Desktop-packages] [Bug 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or el

2018-01-09 Thread Jacques Koch
Thanks will definitely go and take a look. Only been on Linux about a month
or so and really loving it  ,but still finding my feet

On 9 Jan 2018 12:50, "Daniel van Vugt" 
wrote:

> It looks like this bug is now fixed as of 1 hour ago, in linux
> 4.13.0-25.29. You had to be unlucky to have an artful system on proposed
> do an update during the previous day and get the faulty package linux
> 4.13.0-24. That one doesn't exist any more so this bug should quieten
> down now.
>
> See bug 1741955 for updates.
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Fix Committed
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1742014).
> https://bugs.launchpad.net/bugs/1741914
>
> Title:
>   artful-proposed 4.13.0-24: kernel module failed to build [Cannot
>   generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
>   libelf-dev, libelf-devel or elfutils-libelf-devel]
>
> Status in bbswitch package in Ubuntu:
>   Confirmed
> Status in bcmwl package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in ndiswrapper package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-304 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-340 package in Ubuntu:
>   Confirmed
> Status in nvidia-graphics-drivers-384 package in Ubuntu:
>   Confirmed
> Status in virtualbox package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After update to new kernel (4.13.0-24) the system prompted me with
>   this.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 17.10
>   Package: nvidia-384 384.90-0ubuntu3.17.10.2
>   ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
>   Uname: Linux 4.13.0-22-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.7-0ubuntu3.7
>   Architecture: amd64
>   DKMSKernelVersion: 4.13.0-24-generic
>   Date: Mon Jan  8 16:30:09 2018
>   PackageVersion: 384.90-0ubuntu3.17.10.2
>   Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal,
> 3.6.3-0ubuntu2
>   PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal,
> 2.7.14-2ubuntu1
>   RelatedPackageVersions:
>dpkg 1.18.24ubuntu1
>apt  1.5.1
>   SourcePackage: nvidia-graphics-drivers-384
>   Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module
> failed to build
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/
> 1741914/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1741914

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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


  1   2   >