[Desktop-packages] [Bug 1764944] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

*** This bug is a duplicate of bug 1679903 ***
https://bugs.launchpad.net/bugs/1679903

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 #1679903, 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/1764944/+attachment/5120474/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1764944

Title:
  gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-keyring 3.28.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 18 07:31:49 2018
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  InstallationDate: Installed on 2018-04-07 (10 days ago)
  InstallationMedia:
   
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  Signal: 6
  SourcePackage: gnome-keyring
  StacktraceTop:
   g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-keyring-daemon 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-keyring/+bug/1764944/+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 1764725] Re: Je n'ai plus de son sous ubuntu

[thiltges]

Quand j'ouvre la boite des parametres "son" je vois qu'il n'y a rien 
dans le pavé "jouer le son à travers de :" donc il ne connait pas le 
pilote de ma carte Realtek

Bonne journée

René


Le 17/04/2018 à 14:34, dino99 a écrit :
> Voir thes parametres de son dans le tableau de bord (icone coin droit)
> et vérifier que le curseur n'est pas sur 0 (muet) et/ou faire les tests
> de sortie son (via les icones)
>
> https://help.ubuntu.com/community/Sound
>
> https://wiki.ubuntu.com/Sound
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>
> ** Package changed: xorg (Ubuntu) => pulseaudio (Ubuntu)
>

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

Title:
  Je n'ai plus de son sous ubuntu

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  j'ai du son sous windows mais pas sous ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Apr 17 14:03:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV635 [Radeon HD 3650/3750/4570/4580] 
[1002:9598] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RV635 [Radeon HD 3650/3750/4570/4580] 
[1043:9010]
  InstallationDate: Installed on 2018-02-20 (55 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: HP-Pavilion FZ061AA-ABF a6575.fr
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=95cef207-c8c3-49b6-9776-6f663aa4997a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.11
  dmi.board.name: Boston
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.11:bd07/15/2008:svnHP-Pavilion:pnFZ061AA-ABFa6575.fr:pvr:rvnMSI:rnBoston:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: FZ061AA-ABF a6575.fr
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 17 12:05:55 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1764725/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]

[Daniel van Vugt]

^^^
I feel conflicted about letting gnome-shell just exit. It will result in some 
people logging bug reports that we can't diagnose, but those will be orders of 
magnitude fewer than what we see now.

So short term for 18.04, it's a good idea. Slightly beyond that, it's
going to keep hurting us if nobody fixes Xwayland.

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

Title:
  gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
  _XEventsQueued() from XPending() from gdk_check_xpending()
  ["Connection to xwayland lost"]

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gdm3 source package in Artful:
  Confirmed
Status in gnome-shell source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed

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

  ---

  Occurred during start-up, before I did anything special...

  1 Ubuntu Wily Werewolf (development branch) 15.10
  2 3.16.3-1ubuntu6
  3&4 not applicable

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gnome-shell 3.16.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 12 19:22:07 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-10-08 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/libmutter.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1571195] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2

[Jarno Suni]

I think these are duplicates of each other despite the different 
libjpeg-turbo-progs version:
Bug #1550124

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-
  progs 1.3.0-0ubuntu2

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  apt-cache policy libjpeg-progs
  libjpeg-progs:
Installed: 8c-2ubuntu8
Candidate: 1:9b-1
Version table:
   1:9b-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   *** 8c-2ubuntu8 100
  100 /var/lib/dpkg/status

  
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 16 15:36:52 2016
  ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2014-10-21 (542 days ago)
  InstallationMedia:
   
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2
  UpgradeStatus: Upgraded to xenial on 2016-04-16 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1571195/+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 1528195] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no pacote libjpeg-turbo-prog

[Jarno Suni]

*** This bug is a duplicate of bug 1571195 ***
https://bugs.launchpad.net/bugs/1571195

** This bug is no longer a duplicate of bug 1527455
   package libjpeg-progs (not installed) failed to install/upgrade: försöker 
skriva över "/usr/share/man/man1/djpeg.1.gz" som också finns i paketet 
libjpeg-turbo-progs 1.3.0-0ubuntu2
** This bug has been marked a duplicate of bug 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar
  sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no
  pacote libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  Não sei...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  Date: Mon Dec 21 09:57:10 2015
  ErrorMessage: a tentar sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que 
também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2015-10-30 (51 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.1.5
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar 
sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no pacote 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1528195/+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 1516242] Re: dpkg: error al procesar el archivo /var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack): intentando sobreescribir `/usr/share/man/man1/djpeg

[Jarno Suni]

*** This bug is a duplicate of bug 1571195 ***
https://bugs.launchpad.net/bugs/1571195

** This bug has been marked a duplicate of bug 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  dpkg: error al procesar el archivo /var/cache/apt/archives/libjpeg-
  progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):  intentando sobreescribir
  `/usr/share/man/man1/djpeg.1.gz', que está también en el paquete
  libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  the mfollowing line appears when trying to upgrade

  
  dpkg: error al procesar el archivo 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):
   intentando sobreescribir `/usr/share/man/man1/djpeg.1.gz', que está también 
en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.2.0-19.23-lowlatency 4.2.6
  Uname: Linux 4.2.0-19-lowlatency x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 14 14:25:34 2015
  InstallationDate: Installed on 2012-02-27 (1355 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: libjpeg8-empty
  UpgradeStatus: Upgraded to xenial on 2015-11-08 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1516242/+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 1576937] Re: trying to overwrite '/usr/bin/rdjpgcom'

[Jarno Suni]

*** This bug is a duplicate of bug 1571195 ***
https://bugs.launchpad.net/bugs/1571195

** This bug has been marked a duplicate of bug 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  trying to overwrite '/usr/bin/rdjpgcom'

Status in libjpeg-turbo package in Ubuntu:
  New
Status in libjpeg9 package in Ubuntu:
  New

Bug description:
  Seen while upgrading from trusty to xenial:

  Unpacking libjpeg-progs (1:9b-1) over (8c-2ubuntu8) ...
  dpkg: error processing archive 
/mnt/ubuntu/pool/universe/libj/libjpeg9/libjpeg-progs_9b-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/rdjpgcom', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  Errors were encountered while processing:
   /mnt/ubuntu/pool/universe/libj/libjpeg9/libjpeg-progs_9b-1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-turbo-progs 1.3.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 30 00:43:24 2016
  InstallationDate: Installed on 2012-10-18 (1290 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: libjpeg-turbo
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (0 days ago)

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

[Apport retracing service]

*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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 #1748450, 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/1764934/+attachment/5120438/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  No idea why it happened, bug reported appeared from nowhere saying
  this error happened. I think it happened just when I opened IntelliJ
  IDEA Ultimate, but not sure if it's related.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Apr 18 05:49:25 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.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: No upgrade log present (probably fresh install)
  UserGroups:

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

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  black terminal

Status in xorg package in Ubuntu:
  Expired

Bug description:
  my terminal becoms black all

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  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: Thu Jun 29 12:32:32 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fdd0]
  InstallationDate: Installed on 2016-10-16 (255 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: TOSHIBA Satellite L740
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5c492036-60d3-4079-8608-60181e27aac2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.50:bd04/12/2012:svnTOSHIBA:pnSatelliteL740:pvrPSK6XL-00C002:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L740
  dmi.product.version: PSK6XL-00C002
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jun 29 11:43:33 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 760 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1701161/+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 1702140] Re: freeze system again adn again

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  freeze system again adn again

Status in xorg package in Ubuntu:
  Expired

Bug description:
  every three and four hours system will be freeze. i need help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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
  Date: Mon Jul  3 22:48:38 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-83-generic, x86_64: installed
   nvidia-340, 340.102, 4.4.0-83-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
  InstallationDate: Installed on 2017-06-30 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation VPCEH25EN
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=53b92317-9503-44fe-bd39-9bbb573646ad ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH25EN:pvrC105Z9ZK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEH25EN
  dmi.product.version: C105Z9ZK
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81+git20170630.3095cc8e-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
17.1.4~git20170629+17.1.03a0fdbd-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
17.1.4~git20170629+17.1.03a0fdbd-0ubuntu0ricotz~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git20170208.1351e48e-0ubuntu0ricotz2~xenial
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170208.e4fe79cf-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20170208.1516d35b-0ubuntu0ricotz~xenial
  xserver.bootTime: Mon Jul  3 22:23:30 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702140/+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 1702347] Re: Graphical glitches in screen by default on 17.10 & 18.04

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Graphical glitches in screen by default on 17.10 & 18.04

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10 development branch

  updated and dist-upgraded on 4 july 2017

  Im having weird glitches in screen when scrolling or switching windows
  by default

  Graphics:  Card: NVIDIA C77 [GeForce 9100M G]
 Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: 
modesetting,fbdev,vesa)
 Resolution: 1440x900@60.00hz
 GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2

  installing nvidia-340 resulted in a black screen after login, so i had to 
purge nvidia* to get
  back to desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jul  4 20:59:21 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d]
  InstallationDate: Installed on 2017-06-13 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612)
  MachineType: Acer, inc. Aspire 7530
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3342
  dmi.board.name: EI Capitan
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 7530
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.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: Tue Jul  4 20:45:53 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   event6  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu2
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702347/+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 1749907] Re: unable to update firefox and google chrome

[Launchpad Bug Tracker]

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  unable to update firefox and google chrome

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Firefox can't be updated automatically

  sp@sp-Compaq-610:~$ sudo add-apt-repository ppa:ubuntu-mozilla-daily/ppa
   daily (or even multiple builds per day) for various mozilla projects and 
branches.

  For questions and bugs with software in this archive, please contact  or visit #ubuntu-mozillateam on freenode.
   More info: https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/ppa
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmpyppt_4e0/secring.gpg' created
  gpg: keyring `/tmp/tmpyppt_4e0/pubring.gpg' created
  gpg: requesting key 247510BE from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmpyppt_4e0/trustdb.gpg: trustdb created
  gpg: key 247510BE: public key "Launchpad PPA for Ubuntu Mozilla Daily Build 
Team" imported
  gpg: no ultimately trusted keys found
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  sp@sp-Compaq-610:~$ sudo apt-get update
  Ign http://dl.google.com stable InRelease
  Hit http://archive.canonical.com wily InRelease   
 
  Hit http://ppa.launchpad.net wily InRelease   
 
  Hit http://dl.google.com stable Release.gpg   
 
  Ign http://in.archive.ubuntu.com wily InRelease   
 
  Hit http://security.ubuntu.com xenial-security InRelease  
 
  Hit http://dl.google.com stable Release   
 
  Hit https://cli-assets.heroku.com ./ InRelease
 
  Hit http://ppa.launchpad.net wily InRelease   
 
  Ign http://in.archive.ubuntu.com wily-updates InRelease   
 
  Ign http://security.ubuntu.com wily-security InRelease
 
  Get:1 https://cli-assets.heroku.com ./ Packages [820 B]   
 
  Get:2 https://cli-assets.heroku.com ./ Translation-en_IN [364 B]  
 
  Get:3 https://cli-assets.heroku.com ./ Translation-en [361 B] 
 
  Get:4 http://dl.google.com stable/main amd64 Packages [1,392 B]   
 
  Get:5 https://cli-assets.heroku.com ./ Translation-en_IN [364 B]  
 
  Get:6 https://cli-assets.heroku.com ./ Translation-en [361 B] 
 
  Ign http://in.archive.ubuntu.com wily-proposed InRelease  
 
  Get:7 http://ppa.launchpad.net wily InRelease [20.9 kB]   
 
  Get:8 https://cli-assets.heroku.com ./ Translation-en_IN [364 B]  
 
  Get:9 https://cli-assets.heroku.com ./ Translation-en [361 B] 
 
  Hit http://archive.canonical.com wily/partner Sources 
 
  Get:10 https://cli-assets.heroku.com ./ Translation-en_IN [364 B] 
 
  Get:11 https://cli-assets.heroku.com ./ Translation-en [361 B]
 
  Ign http://in.archive.ubuntu.com wily-backports InRelease 
 
  Get:12 https://cli-assets.heroku.com ./ Translation-en_IN [364 B] 
 
  Ign https://cli-assets.heroku.com ./ Translation-en_IN
 
  Hit http://archive.canonical.com wily/partner amd64 Packages  
 
  Get:13 https://cli-assets.heroku.com ./ Translation-en [361 B]
 
  Ign https://cli-assets.heroku.com ./ Translation-en   
 
  Ign http://in.archive.ubuntu.com wily Release.gpg 
 
  Hit http://ppa.launchpad.net wily InRelease   
 
  Hit http://archive.canonical.com wily/partner i386 Packages   
 
  Hit http://archive.canonical.com wily/partner Translation-en  
 
  Ign http://in.archive.ubuntu.com wily-updates Release.gpg 
 
  Ign http://security.ubuntu.com wily-security Release.gpg  
 
  Hit http://ppa.launchpad.net wily InRelease   
 
  Ign http://in.archive.ubuntu.com wily-proposed Release.gpg
 
  Hit http://security.ubuntu.com xenial-security/main amd64 Packages
 
  Ign http://in.archive.ubuntu.com wily-backports Release.gpg   
 
  Hit http://security.ubuntu.com xenial-security/main i386 Packages 
 
  Ign http://in.archive.ubuntu.com wily Release 
 
  Hit http://security.ubuntu.com xenial-security/main Translation-en
 
  Ign http://in.archive.ubuntu.com wily-updates Release 
 
  Ign 

[Desktop-packages] [Bug 1748098] Re: simple-scan crashes when running simple-scan from the command line when simple-scan is already running

[Launchpad Bug Tracker]

[Expired for simple-scan (Ubuntu) because there has been no activity for
60 days.]

** Changed in: simple-scan (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  simple-scan crashes when running simple-scan from the command line
  when simple-scan is already running

Status in simple-scan package in Ubuntu:
  Expired

Bug description:
  To reproduce open simple-scan then open a terminal and execute simple-
  scan.

  simple-scan:
Installed: 3.26.3-0ubuntu1
Candidate: 3.26.3-0ubuntu1
Version table:
   *** 3.26.3-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
   
  I expected the original simple-scan to stay open when I ran simple-scan from 
the terminal with it already open. Instead simple-scan crashed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: simple-scan 3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Wed Feb  7 21:39:18 2018
  InstallationDate: Installed on 2017-06-20 (232 days ago)
  InstallationMedia: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 
(20170619)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=a021c81d-9a0a-44ab-9906-39b529de57c5 ro quiet splash vt.handoff=1
  SimpleScanLog: [+0.00s] DEBUG: simple-scan.vala:637: Starting Simple Scan 
3.26.3, PID=27746
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to bionic on 2018-02-02 (6 days ago)
  dmi.bios.date: 08/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3627
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnQuanta:rn3627:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1748098/+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 1550124] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1

[Jarno Suni]

Why would you want to install both libjpeg-progs and libjpeg-turbo-progs? 
"apt-cache depends libjpeg-progs" tells they conflict and replace each other.

I noticed similar issue after upgrading from Trusty to Xenial. Both packages 
were installed. I resolved that by purging libjpeg-progs. I did not want to 
purge libjpeg-turbo-progs, because jhead depends on it and I wanted to keep it. 
I had no problem by purging libjpeg-progs by apt, but some have had and here is 
related post:
https://askubuntu.com/q/766929/21005

BTW what is libjpeg8-empty? 
$ apt-cache policy libjpeg8-empty 
N: Unable to locate package libjpeg8-empty

I see similar bugs
Bug #1576010
Bug #1559754 
Bug #1576937
Bug #1571195
Bug #1527455
Bug #1516242


** Tags added: package-conflict

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-
  progs 1.4.2-0ubuntu1

Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  update failed with this.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Feb 22 20:02:43 2016
  ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in 
package libjpeg-turbo-progs 1.4.2-0ubuntu1
  InstallationDate: Installed on 2012-09-23 (1251 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.4.2-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1550124/+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 1733772] Re: thunderbird ambiance

[Rudolf Tucek]

*** This bug is a duplicate of bug 1710059 ***
https://bugs.launchpad.net/bugs/1710059

** This bug has been marked a duplicate of bug 1710059
   Theming issue when searching in Thunderbird

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

Title:
  thunderbird ambiance

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  In Thunderbird (ubuntu artful 17.10) the search dialog gives results with 
black/grey background and blue font. This difficult to read.
  When i changed the theme to Gnome Vanilla, the problem disappears. So i'm not 
sure if i should report the bug to ambiance theme or to thunderbird

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: thunderbird 1:52.4.0+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brce   1773 F pulseaudio
   /dev/snd/controlC0:  brce   1773 F pulseaudio
  BuildID: 20171005162202
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 22 06:34:35 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-10-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.0.111 dev ens4 proto static metric 100 
   169.254.0.0/16 dev ens4 scope link metric 1000 
   192.168.0.0/16 dev ens4 proto kernel scope link src 192.168.66.3 metric 100
  IwConfig:
   ens4  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Prefs:
   extensions.lastAppVersion: "52.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   network.predictor.cleaned-up: true (prefs.js)
   places.database.lastMaintenance: 1510754123 (prefs.js)
   places.history.expiration.transient_current_max_pages: 122334 (prefs.js)
  Profiles: Profile0 (Default) - LastVersion=52.4.0/20171005162202
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z10PE-D8 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd11/04/2015:svnASUSTeKCOMPUTERINC.:pnZ10PE-D8WS:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ10PE-D8WS:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: Z10PE-D8 WS
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1733772/+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 1710059] Re: Theming issue when searching in Thunderbird

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Theming issue when searching in Thunderbird

Status in ubuntu-mate:
  Invalid
Status in thunderbird package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  Invalid

Bug description:
  Affecting the dropdown list of the search input field in the top right
  of Thunderbird.

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1710059/+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 1764924] [NEW] Intel HD Graphics 630 can not use three displays but HD 530 can

[Qianqian Fang]

Public bug reported:

My Ubuntu (14.04 LTS) desktop used to have an Intel 6700K CPU and I have
been using the built in HD Graphics 530 GPU to drive 3 external displays
- via DP, HDMI and DVI on the motherboard (AsRock Extreme4).

at some point, I upgraded the CPU to an Intel 7700K, and I realized that
the computer can not output to 3 displays anymore.

using xrandr -q, I can only see two connections - HDMI and DP, but the
DVI output is not listed, nor can be activated.

Based on this intel's page, HD630 GPU is supposed to support 3 outputs,

https://www.intel.com/content/www/us/en/support/articles/25672
/graphics-drivers.html

I am wondering if this is a known issue, or if there is a version of the
xorg intel driver that support 3 outputs for HD 630?

my intel driver is provided by xserver-xorg-video-intel-lts-xenial
version 2:2.99.917+git20160325-1ubuntu1~trusty1

thanks, let me know if there is a workaround.

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Intel HD Graphics 630 can not use three displays but HD 530 can

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  My Ubuntu (14.04 LTS) desktop used to have an Intel 6700K CPU and I
  have been using the built in HD Graphics 530 GPU to drive 3 external
  displays - via DP, HDMI and DVI on the motherboard (AsRock Extreme4).

  at some point, I upgraded the CPU to an Intel 7700K, and I realized
  that the computer can not output to 3 displays anymore.

  using xrandr -q, I can only see two connections - HDMI and DP, but the
  DVI output is not listed, nor can be activated.

  Based on this intel's page, HD630 GPU is supposed to support 3
  outputs,

  https://www.intel.com/content/www/us/en/support/articles/25672
  /graphics-drivers.html

  I am wondering if this is a known issue, or if there is a version of
  the xorg intel driver that support 3 outputs for HD 630?

  my intel driver is provided by xserver-xorg-video-intel-lts-xenial
  version 2:2.99.917+git20160325-1ubuntu1~trusty1

  thanks, let me know if there is a workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1764924/+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 1764877] Re: glamorgl Xv causes xvimagesink failure

[Bug Watch Updater]

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

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

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

Title:
  glamorgl Xv causes xvimagesink failure

Status in GStreamer:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu 16.04 with xorg-server-hwe-16.04-1.19.5, xvimagesink fails
  for certain sizes of image. Originally seen when receiving a meeting
  screen share in Pidgin, reproducible as follows:

  $ gst-launch-1.0 -v videotestsrc  ! video/x-raw,width=905,height=720 !
  xvimagesink

  The problem is actually in glamor_xv.c, fixed by the following upstream patch:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=12a6b189fb17894d2c3851b70a396bbf41f444c6

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1764877/+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 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]

[Daniel van Vugt]

It looks like upstream has a "fix" coming:

https://gitlab.gnome.org/GNOME/mutter/commit/2d80fd02e76bbe17dc52072299dda92ab88c99c0

Although that will just stop the crash reports from occurring and not
fix the root cause. That may be all we need for now...

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

Title:
  gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
  _XEventsQueued() from XPending() from gdk_check_xpending()
  ["Connection to xwayland lost"]

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gdm3 source package in Artful:
  Confirmed
Status in gnome-shell source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed

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

  ---

  Occurred during start-up, before I did anything special...

  1 Ubuntu Wily Werewolf (development branch) 15.10
  2 3.16.3-1ubuntu6
  3&4 not applicable

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gnome-shell 3.16.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 12 19:22:07 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-10-08 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/libmutter.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1505409/+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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from

[Daniel van Vugt]

*** This is a duplicate of bug 1505409, but is being kept separate so as
to automatically collect duplicate reports since the stack trace
signature has changed recently. Any resolution and discussion should
occur in bug 1505409. ***

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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 2018-02-08 (0 days ago)
  UserGroups:

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

[Laur]

*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** Information type changed from Public to Public Security

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

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:
  error < broken count 0

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Feb 28 08:27:12 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-OyTCUS/100-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 2017-10-19 (136 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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: Upgraded to artful on 2018-02-28 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1753205/+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 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files '/lib/udev/hwdb.d/20-sane.hwdb'

[Laur]

** Information type changed from Public to Public Security

** Information type changed from Public Security to Private Security

** Information type changed from Private Security to Public Security

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages
  with differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  
  From #3 comment below, to get a workaround, try:

  sudo apt-get -o Dpkg::Options::="--force-overwrite" install
  --reinstall libsane1:i386 (or your real package name)

  ***
  Has been fixed with:

  sane-backends (1.0.27-1~experimental3ubuntu2) bionic; urgency=medium

* debian/rules: Drop timestamps from conflicting multiarch:same files
  hwdb.d/20-sane.hwdb and rules.d/60-libsane1.rules (closes: #880391)

   -- Adam Conrad  Sat, 03 Feb 2018 14:26:39 -0700
  ***

  apport error this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_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 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 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: Upgraded to artful on 2017-10-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1725928/+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 1763417] Re: thin red lines around "Format" button in gnome-disks

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1763417/+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 1763417] Re: thin red lines around "Format" button in gnome-disks

[Daniel van Vugt]

I'm seeing the same bug with red headerbar buttons in other apps. I
think colorhug-client was where I saw it last.

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1763417/+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 1763417] Re: thin red lines around "Format" button in gnome-disks

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1763417/+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 1763417] Re: thin red lines around "Format" button in gnome-disks

[Daniel van Vugt]

** No longer affects: gnome-disk-utility (Ubuntu)

** Summary changed:

- thin red lines around "Format" button in gnome-disks
+ Thin red lines around red headerbar buttons

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1763417/+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 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent

[Daniel van Vugt]

** Also affects: gdm via
   https://bugzilla.gnome.org/show_bug.cgi?id=794734
   Importance: Unknown
   Status: Unknown

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

Title:
  Blocked at gdm login screen on 18.04 if user password has a circumflex
  accent

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I have a bug since the recent updates on Ubuntu 18.04 (post 10th
  March): when the user password contains a circumflex accent, like "û",
  access is denied even if password entered is correct and I stay
  blocked in a loop at gdm login screen - error message (translated from
  French): "Sorry, it doesn't work, please try again".

  Even after modifying it on recovery mode with passwd without û, it
  stays blocked. Only way to solve it is to reinstall.

  Graphic card: [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
  Kernel driver in use: radeon
  Kernel modules: radeon, amdgpu

  Steps to reproduce :

  I did a fresh and new install with 18.04 daily iso from 21st March,
  formatting / and /home with following user password:

  Ubuntu42

  At startup, I could log successfully both on Xorg and Wayland sessions. Then 
I modified and tested those passwords, with all of them I could again boot and 
connect, on Xorg and Wayland:
  ArchLinux43
  LinuxMint@28
  KDENeon=51
  Fedora_1984

  But the last one made me blocked at the gdm login screen:

  Debianû74

  Here unable to modify it on recovery session, error message in French:
  "erreur de manipulation du jeton d'authentification".

  Also unable to launch terminal: CTRl Alt F1 refreshes the screen, but
  F2, F3... F12 freezes it! I only can update in chroot with lie USB.

  I had to again format and reinstall, with a password without any
  circumflex accent.

  
  How and when I discovered it :

  On 10th March, I ran since many weeks the alpha version of Ubuntu
  18.04, with a password having a "û" inside, which had always worked
  fine. I did an update, cumulating the last 3 weeks before.

  On next startup, when I typed my password, both on Xorg and Wayland
  sessions, no error message but no desktop, nothing appeared but a few
  seconds later I was back on login screen.

  I could well log in on terminal (Ctrl Alt F2) or chroot with a live
  USB, and do the last updates in the next days, but nothing changed.

  On console, if I ran "startx" I got the message "timeout in locking
  authority file" and "fatal server error: cannot open log file
  ./local/share/xorg/Xorg.0.log

  Both / and /home were not full - more than 60% space available,
  verified with df -Th ; echo ; df -Ti

  I tried to reinstall Ubuntu with daily live of 15th March, formatting
  / but not /home as it was protected by ecryptfs and I didn't save some
  files, using same user name and password, still blocked.

  So I copied the /home and .Private folders to another disk to try
  later recover them, reinstall again, formatting both / and /home,
  always with my usual password having a "û" (I verified French
  language, keyboard with French activated, upper case, symbols... OK).

  This time, again both for Xorg or Wayland sessions, at gdm login I did
  not success to connect, I got an error message "Désolé ça n'a pas
  fonctionné, veuillez réessayer",

  I tried to modify the password in recovery mode, with no special
  characters nor accents, but still blocked at gdm. And no terminal
  available with Ctrl Alt F2...

  On 23rd March, I re-reinstalled all Ubuntu, formatting / and /home,
  this time with daily iso from 21st March, but with a modification: to
  avoid any misconfiguration with languages on live USB, I chose a very
  easy password, only with normal letters and numbers.

  On startup, yes, finally I could log at gdm on default Xorg session
  and enter desktop !

  I went to my user configuration, changed to put my usual password
  (with an "û"), and bam, back to the future, still blocked at gdm
  screen on restart, either on Xorg or Wayland, Ctr Alt F2 not working.

  It made me understand that the bug came from a special character in my
  password, then I tried the different ones explained on top of this
  report to discover it was "û".

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1758563/+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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

[Gunnar Hjalmarsson]

Did some testing on bionic.

It appears to me as if the feature is designed solely for Wayland. Yes,
on Wayland with GTK_IM_MODULE unset it seems to work without issues. On
Wayland with GTK_IM_MODULE=ibus I can reproduce the issues as described
above.

On Xorg the feature works very poorly irrespective of the value of
GTK_IM_MODULE. Basically you can only type the characters you see on the
first instance of the screen keyboard (which depends on the effective
XKB layout). Capitalized letters get typed as small letters, and most
extended characters don't result in anything or some wrong character.

Considering that Xorg will be default in 18.04, would it be worth the
regression risk to stop im-config from setting GTK_IM_MODULE this late
in the cycle in order to fix the feature on Wayland?

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

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

  Test Case
  -
  1. Open the Settings app. Click Universal Access.
  2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal 
Access Menu" to make turning the Screen Keyboard on and off easier.)
  3. Open Text Editor
  4. Click the u button on the Screen Keyboard
  5. Long-press the u button on the Screen Keyboard for a few seconds. On the 
popup, click the ü character.

  What Happens
  
  In Step 4, u is entered in the Text Editor document.

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+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 1764877] Re: glamorgl Xv causes xvimagesink failure

[Daniel van Vugt]

** Changed in: xorg-server (Ubuntu)
   Status: New => Triaged

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => Medium

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

** Also affects: gstreamer via
   https://bugzilla.gnome.org/show_bug.cgi?id=795235
   Importance: Unknown
   Status: Unknown

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

Title:
  glamorgl Xv causes xvimagesink failure

Status in GStreamer:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu 16.04 with xorg-server-hwe-16.04-1.19.5, xvimagesink fails
  for certain sizes of image. Originally seen when receiving a meeting
  screen share in Pidgin, reproducible as follows:

  $ gst-launch-1.0 -v videotestsrc  ! video/x-raw,width=905,height=720 !
  xvimagesink

  The problem is actually in glamor_xv.c, fixed by the following upstream patch:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=12a6b189fb17894d2c3851b70a396bbf41f444c6

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1764877/+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 1764880] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertiva “hash_table->live_e

[Daniel van Vugt]

*** This bug is a duplicate of bug 1763878 ***
https://bugs.launchpad.net/bugs/1763878

** This bug is no longer a duplicate of private bug 1764763
** This bug has been marked a duplicate of bug 1763878
   [regression] Many programs crashing at exit with assert failure: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed. Called from 
cairo_debug_reset_static_data()

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Assertiva “hash_table->live_entries == 0” falhou.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I don't know what's happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertiva 
“hash_table->live_entries == 0” falhou.
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 18:27:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['openweather-extens...@jenslody.de', 'caffe...@patapon.info', 
'sound-output-device-choo...@kgshank.net', 'mediapla...@patapon.info', 
'netsp...@hedayaty.gmail.com', 'amdtool...@zerosubnet.com']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: gnome-shell-extension-prefs freon@Veske
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7fa28c086202 , assertion=assertion@entry=0x7fa29543ed05 
"hash_table->live_entries == 0", file=file@entry=0x7fa29543ece8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7fa29543ee90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7fa29543ed05 "hash_table->live_entries == 
0", file=0x7fa29543ece8 "../../../../src/cairo-hash.c", line=217, 
function=0x7fa29543ee90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertiva “hash_table->live_entries == 0” falhou.
  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/1764880/+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 1019047] Re: Wacom settings icon is present even though no Wacom tablet is attached

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Confirmed => Expired

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

Title:
  Wacom settings icon is present even though no Wacom tablet is attached

Status in gnome-control-center:
  Expired
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  In a world where there are very few people actually own and use a
  Wacom graphics tablet compared to the greater computer using
  demographic, does it really make sense to have an icon for its
  settings in the control panel on every computer even when a Wacom
  tablet is not attached? If so, why not have an icon for USB humping
  dogs? Lots of people use those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1019047/+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 1764896] [NEW] System will not display using displayport from AMD GPU

[terry b]

Public bug reported:

There are 2 monitors connected to 1 GPU. The monitor connected via a
digital connection always comes up correctly. The monitor connected via
DISPLAYPORT does not come up, even though the machine is booting
correctly.

It's almost like the DP path isn't recognized by xorg.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 17 18:02:09 2018
DistUpgraded: 2018-03-30 21:12:37,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 
470/480/570/580] [1462:3417]
InstallationDate: Installed on 2017-03-11 (402 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=UUID=68755ecb-0ee0-46a1-8a3e-c027d0cbac65 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-03-31 (17 days ago)
dmi.bios.date: 12/13/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.20
dmi.board.name: Z170M Pro4S
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.20:bd12/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170MPro4S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

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

Title:
  System will not display using displayport from AMD GPU

Status in xorg package in Ubuntu:
  New

Bug description:
  There are 2 monitors connected to 1 GPU. The monitor connected via a
  digital connection always comes up correctly. The monitor connected
  via DISPLAYPORT does not come up, even though the machine is booting
  correctly.

  It's almost like the DP path isn't recognized by xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 17 18:02:09 2018
  DistUpgraded: 2018-03-30 21:12:37,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 
470/480/570/580] [1462:3417]
  InstallationDate: Installed on 2017-03-11 (402 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=UUID=68755ecb-0ee0-46a1-8a3e-c027d0cbac65 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  

[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for GTX 960M

[Giraffe]

Using a Quadro M2000M on 18.04 with nvidia-prime same problem here...

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

Title:
  Black-screen on boot with nvidia 390 for GTX 960M

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1764005/+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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

[Gunnar Hjalmarsson]

After having read one of Carlos' comments in the upstream issue, I
switched to a German XKB layout and was then able to type ü via the
screen keyboard.

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

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

  Test Case
  -
  1. Open the Settings app. Click Universal Access.
  2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal 
Access Menu" to make turning the Screen Keyboard on and off easier.)
  3. Open Text Editor
  4. Click the u button on the Screen Keyboard
  5. Long-press the u button on the Screen Keyboard for a few seconds. On the 
popup, click the ü character.

  What Happens
  
  In Step 4, u is entered in the Text Editor document.

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+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 1764877] Re: glamorgl Xv causes xvimagesink failure

[dwmw2]

** Description changed:

- On Ubuntu 16.04 with xserver-xorg-1:7.7+13ubuntu3, xvimagesink fails for
+ On Ubuntu 16.04 with xorg-server-hwe-16.04-1.19.5, xvimagesink fails for
  certain sizes of image. Originally seen when receiving a meeting screen
  share in Pidgin, reproducible as follows:
  
  $ gst-launch-1.0 -v videotestsrc  ! video/x-raw,width=905,height=720 !
  xvimagesink
  
  The problem is actually in glamor_xv.c, fixed by the following upstream patch:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=12a6b189fb17894d2c3851b70a396bbf41f444c6

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

Title:
  glamorgl Xv causes xvimagesink failure

Status in xorg-server package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04 with xorg-server-hwe-16.04-1.19.5, xvimagesink fails
  for certain sizes of image. Originally seen when receiving a meeting
  screen share in Pidgin, reproducible as follows:

  $ gst-launch-1.0 -v videotestsrc  ! video/x-raw,width=905,height=720 !
  xvimagesink

  The problem is actually in glamor_xv.c, fixed by the following upstream patch:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=12a6b189fb17894d2c3851b70a396bbf41f444c6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1764877/+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 1764880] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertiva “hash_table->live_e

[Apport retracing service]

*** This bug is a duplicate of bug 1764763 ***
https://bugs.launchpad.net/bugs/1764763

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 #1764763, 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/1764880/+attachment/5120149/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Assertiva “hash_table->live_entries == 0” falhou.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I don't know what's happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertiva 
“hash_table->live_entries == 0” falhou.
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 18:27:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['openweather-extens...@jenslody.de', 'caffe...@patapon.info', 
'sound-output-device-choo...@kgshank.net', 'mediapla...@patapon.info', 
'netsp...@hedayaty.gmail.com', 'amdtool...@zerosubnet.com']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: gnome-shell-extension-prefs freon@Veske
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7fa28c086202 , assertion=assertion@entry=0x7fa29543ed05 
"hash_table->live_entries == 0", file=file@entry=0x7fa29543ece8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7fa29543ee90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7fa29543ed05 "hash_table->live_entries == 
0", file=0x7fa29543ece8 "../../../../src/cairo-hash.c", line=217, 
function=0x7fa29543ee90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertiva “hash_table->live_entries == 0” falhou.
  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/1764880/+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 1655555] Re: Chromium aborts on SIGBUS every minute with vm.overcommit_memory=2

[Brian]

We see a lot of SIGBUS crashes with Chrome on Linux 4.4.0.*

Does the problem go away with a more recent release?

-- Brian

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

Title:
  Chromium aborts on SIGBUS every minute with vm.overcommit_memory=2

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The Linux kernel has a knob, vm.overcommit_memory, which switches how
  memory allocation requests are handled. What I'm reporting is that
  Chromium is basically unusable with a non-standard setting of that
  knob (which makes sense as a better default to me on my system).

  So, steps to reproduce:

  1) install chromium-browser
  2) sysctl vm.overcommit_memory=2
  3) run chromium-browser

  Expected behavior: works normally.

  Actual behavior: crashes every minute or two. Console output:

  [1]7449 bus error (core dumped)  chromium-browser

  I believe this is either a misconfigured build, or an upstream bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-LVDS-1:
   edid-base64: 
AP///wAw5IIDAAAWAQOAHxF4CrqFo1hUoScMUFQBAQEBAQEBAQEBAQEBAQEBMCpARGGEJDAwIDUANa4QAAAZ/gBMRyBEaXNwbGF5CiAg/gBMUDE0MFdEMi1UTEUyAFI=
   dpms: On
   modes: 1600x900
   enabled: enabled
   status: connected
  DRM.card0-VGA-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  Date: Wed Jan 11 09:30:28 2017
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2013-07-12 (1278 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Load-Avg-1min: 10.00
  Load-Processes-Running-Percent:   0.5%
  MachineType: LENOVO 3444FHG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=0c3285b7-5de5-405d-8524-8396272551d7 ro quiet splash 
iwlwifi.power_save=1 iwlwifi.led_mode=1 i915.i915_enable_rc6=7 
i915.i915_enable_fbc=1 i915.lvds_downclock=1 drm.vblankoffdelay=1 quiet splash 
vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (200 days ago)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3444FHG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET93WW(2.53):bd02/04/2013:svnLENOVO:pn3444FHG:pvrThinkPadX1Carbon:rvnLENOVO:rn3444FHG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3444FHG
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/165/+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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

[Gunnar Hjalmarsson]

Hmm.. I now see that the issue is present in 17.10 too, so it's probably
due to something else but the latest IBus changes which affected
Ctrl+Shift+U.

I also see that some extended characters work. For instance, the letters
å, ä and ö, which are in the Swedish alphabet, work for me. Weird.

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

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

  Test Case
  -
  1. Open the Settings app. Click Universal Access.
  2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal 
Access Menu" to make turning the Screen Keyboard on and off easier.)
  3. Open Text Editor
  4. Click the u button on the Screen Keyboard
  5. Long-press the u button on the Screen Keyboard for a few seconds. On the 
popup, click the ü character.

  What Happens
  
  In Step 4, u is entered in the Text Editor document.

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+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 1764877] Re: glamorgl Xv causes xvimagesink failure

[dwmw2]

** Description changed:

- On Ubuntu 16.04 with xserver-xorg-2:1.17.2-2, xvimagesink fails for
+ On Ubuntu 16.04 with xserver-xorg-1:7.7+13ubuntu3, xvimagesink fails for
  certain sizes of image. Originally seen when receiving a meeting screen
  share in Pidgin, reproducible as follows:
  
  $ gst-launch-1.0 -v videotestsrc  ! video/x-raw,width=905,height=720 !
  xvimagesink
  
  The problem is actually in glamor_xv.c, fixed by the following upstream patch:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=12a6b189fb17894d2c3851b70a396bbf41f444c6

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

Title:
  glamorgl Xv causes xvimagesink failure

Status in xorg-server package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04 with xserver-xorg-1:7.7+13ubuntu3, xvimagesink fails
  for certain sizes of image. Originally seen when receiving a meeting
  screen share in Pidgin, reproducible as follows:

  $ gst-launch-1.0 -v videotestsrc  ! video/x-raw,width=905,height=720 !
  xvimagesink

  The problem is actually in glamor_xv.c, fixed by the following upstream patch:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=12a6b189fb17894d2c3851b70a396bbf41f444c6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1764877/+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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

[Gunnar Hjalmarsson]

@Jeremy: Your workaround with not setting GTK_IM_MODULE makes me think
of bug #1760308, where that would have been an alternative solution (see
comment #6). Now Sebastien fixed it in IBus instead.

To stop setting GTK_IM_MODULE would be an easy thing in im-config, of
course. I'm hesitating since we have set that variable to ibus for many
cycles, and we are very late in the cycle. I don't understand the
significance of setting it, and I think it would be desirable to at
least consult with one or two IM users before making that change.

Or maybe Sebastien, who is already familiar with the IBus changes which
screwed up things wrt Ctrl+Shift+U, can give us a hint offhand on what
could be done on the IBus side.

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

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

  Test Case
  -
  1. Open the Settings app. Click Universal Access.
  2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal 
Access Menu" to make turning the Screen Keyboard on and off easier.)
  3. Open Text Editor
  4. Click the u button on the Screen Keyboard
  5. Long-press the u button on the Screen Keyboard for a few seconds. On the 
popup, click the ü character.

  What Happens
  
  In Step 4, u is entered in the Text Editor document.

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+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 1764877] [NEW] glamorgl Xv causes xvimagesink failure

[dwmw2]

Public bug reported:

On Ubuntu 16.04 with xserver-xorg-2:1.17.2-2, xvimagesink fails for
certain sizes of image. Originally seen when receiving a meeting screen
share in Pidgin, reproducible as follows:

$ gst-launch-1.0 -v videotestsrc  ! video/x-raw,width=905,height=720 !
xvimagesink

The problem is actually in glamor_xv.c, fixed by the following upstream patch:
https://cgit.freedesktop.org/xorg/xserver/commit/?id=12a6b189fb17894d2c3851b70a396bbf41f444c6

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


** Tags: patch xenial

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

Title:
  glamorgl Xv causes xvimagesink failure

Status in xorg-server package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04 with xserver-xorg-2:1.17.2-2, xvimagesink fails for
  certain sizes of image. Originally seen when receiving a meeting
  screen share in Pidgin, reproducible as follows:

  $ gst-launch-1.0 -v videotestsrc  ! video/x-raw,width=905,height=720 !
  xvimagesink

  The problem is actually in glamor_xv.c, fixed by the following upstream patch:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=12a6b189fb17894d2c3851b70a396bbf41f444c6

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

[Apport retracing service]

*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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 #1748450, 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/1764871/+attachment/5120091/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  gnome-shell:
Installed: 3.28.0-0ubuntu5
Candidate: 3.28.0-0ubuntu5
Version table:
   *** 3.28.0-0ubuntu5 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Apr 17 22:10:55 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-26 (173 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () 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 2018-04-01 (16 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764871/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Pioterus]

Commenting out dnsmasq stopped working. What I have done recently:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
so my kernel is 4.13 and to my big surprise after connecting with OpenVPN I can 
resolve host names of my remote site (using host myhost.remote.domain.name), 
but I cannot ping to them (or krdc to them etc) host unknown and thats it. What 
is going on?

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1764872] [NEW] When in fullscreen, the buttons to minimize and close don't appear when hovering the mouse

[Leonardo Müller]

Public bug reported:

When in fullscreen, the buttons that should appear when hovering the
mouse cursor centered on the top of the display don't appear. They still
have the function but, as it's impossible to see them, it's not possible
to see if the button will close or minimize the session.

I'm using vinagre with the VNC protocol to see and use my desktop, which
is in the local network.

I had this bug with virt-manager in Artful. It's curious to see it back,
but now in vinagre.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vinagre 3.22.0-5
Uname: Linux 4.16.2-041602-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Apr 17 18:18:17 2018
InstallationDate: Installed on 2017-06-13 (307 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: vinagre
UpgradeStatus: Upgraded to bionic on 2017-10-20 (179 days ago)

** Affects: vinagre (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 vinagre in Ubuntu.
https://bugs.launchpad.net/bugs/1764872

Title:
  When in fullscreen, the buttons to minimize and close don't appear
  when hovering the mouse

Status in vinagre package in Ubuntu:
  New

Bug description:
  When in fullscreen, the buttons that should appear when hovering the
  mouse cursor centered on the top of the display don't appear. They
  still have the function but, as it's impossible to see them, it's not
  possible to see if the button will close or minimize the session.

  I'm using vinagre with the VNC protocol to see and use my desktop,
  which is in the local network.

  I had this bug with virt-manager in Artful. It's curious to see it
  back, but now in vinagre.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vinagre 3.22.0-5
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Apr 17 18:18:17 2018
  InstallationDate: Installed on 2017-06-13 (307 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: vinagre
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (179 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/1764872/+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 1364292] Re: 8086:2a42 [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset

[Andrew Drummond]

I had this problem on a Toshiba Tecra A10-104 using Linux mint 17.3 XFCE (based 
on U14.04) with Intel GM45 onboard graphics.
Updating from a 3.x kernel to the latest 4.4 one fixed the problem for me, with 
no regressions found so far. :)

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

Title:
  8086:2a42 [Toshiba Portégé R600-10Q] VGA output doesn't work with
  Intel GM45 chipset

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I have just installed Ubuntu 14.04 64-bit on my Toshiba Portege
  R600-10Q laptop (a model from 2009). I am now trying to display the
  desktop on a BenQ Senseye3 22" monitor, via the vga output, but it's
  not working - the monitor says "No Signal Detected!".

  What I've done:
  I have gone into "Screen Display", where I can see the monitor is detected by 
the laptop.
  The monitor has a 1920 x 1080 native resolution, which I have tried to use, 
but I have also set it to lower resolutions, e.g. 1024 x 576.
  I have tried to use the monitor in dual screen, mirrored and single screen 
mode - none work.
  I have tried pressing Fn + F5 to get single screen output - the laptop screen 
goes blank, but still no output on the monitor.
  I have tried several monitors (of the same type, and also of a different 
make), so I don't think it's that.

  If I plug the vga cable in after boot up, then the monitor receives no
  signal.

  WORKAROUND: If, and only if, the monitor was plugged in to the PC's
  VGA output during boot up, then the display outputs to the monitor
  correctly.

  The laptop has the Intel® GS45 Express chipset for graphics acceleration. I 
installed mesa-utils and ran glxinfo in a terminal. Amongst the output was:
  OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset

  Also, in the "About This Computer" window I see:
  Graphics: Mobile Intel® GM45 Express Chipset

  I wonder if the problem is that my chipset is GS45 not GM45.

  The output of "sudo lshw -C video" is:
  *-display:0
  description: VGA compatible controller
  product: Mobile 4 Series Chipset Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2
  bus info: pci@:00:02.0
  version: 07
  width: 64 bits
  clock: 33MHz
  capabilities: msi pm vga_controller bus_master cap_list rom
  configuration: driver=i915 latency=0
  resources: irq:44 memory:ff40-ff7f memory:e000-efff 
ioport:cff8(size=8)
  *-display:1 UNCLAIMED
  description: Display controller
  product: Mobile 4 Series Chipset Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2.1
  bus info: pci@:00:02.1
  version: 07
  width: 64 bits
  clock: 33MHz
  capabilities: pm bus_master cap_list
  configuration: latency=0
  resources: memory:ffc0-ffcf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.3
  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: Tue Sep  2 10:00:57 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:000c]
     Subsystem: Toshiba America Info Systems Device [1179:000c]
  InstallationDate: Installed on 2014-08-28 (4 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: TOSHIBA PORTEGE R600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=fe977943-4013-472e-b627-f7184c9e190f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.60
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.60:bd11/27/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE R600
  dmi.product.version: PPR61E-00Q00CEN
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  

[Desktop-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

** Changed in: ibus (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+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 1764855] Re: gnome-language-selector assert failure: python3: ../../src/xcb_io.c:259: poll_for_event: Проверочное утверждение «!xcb_xlib_threads_sequence_lost» не выполнено.

[Gunnar Hjalmarsson]

** Information type changed from Private to Public

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

Title:
  gnome-language-selector assert failure: python3:
  ../../src/xcb_io.c:259: poll_for_event: Проверочное утверждение
  «!xcb_xlib_threads_sequence_lost» не выполнено.

Status in language-selector package in Ubuntu:
  New

Bug description:
  11

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: language-selector-gnome 0.188
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AssertionMessage: python3: ../../src/xcb_io.c:259: poll_for_event: 
Проверочное утверждение «!xcb_xlib_threads_sequence_lost» не выполнено.
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 22:59:59 2018
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2018-04-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  Signal: 6
  SourcePackage: language-selector
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff4bb8cb622 , assertion=assertion@entry=0x7ff4bfdf9660 
"!xcb_xlib_threads_sequence_lost", file=file@entry=0x7ff4bfdf94cb 
"../../src/xcb_io.c", line=line@entry=259, 
function=function@entry=0x7ff4bfdf9908 "poll_for_event") at assert.c:92
   __GI___assert_fail (assertion=0x7ff4bfdf9660 
"!xcb_xlib_threads_sequence_lost", file=0x7ff4bfdf94cb "../../src/xcb_io.c", 
line=259, function=0x7ff4bfdf9908 "poll_for_event") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  Title: gnome-language-selector assert failure: python3: 
../../src/xcb_io.c:259: poll_for_event: Проверочное утверждение 
«!xcb_xlib_threads_sequence_lost» не выполнено.
  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/language-selector/+bug/1764855/+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 1764860] Re: dbus crashed with SIGABRT in _dbus_abort()

[Till Kamppeter]

** Information type changed from Private to Public

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

Title:
  dbus crashed with SIGABRT in _dbus_abort()

Status in cups package in Ubuntu:
  New

Bug description:
  bionic beaver @ dell xps12

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 20:42:40 2018
  ExecutablePath: /usr/lib/cups/notifier/dbus
  InstallationDate: Installed on 2018-03-11 (37 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lpstat:
   device for HP_LaserJet_500_color_M551_2F183C_: 
ipp://BKPRT777.local:631/ipp/print
   device for HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: 
ipps://BKPRT777.local:443/ipp/print
   device for Lexmark-W820-Bravo: socket://10.42.9.152:9100
  MachineType: Dell Inc. XPS 12 9Q23
  Papersize: letter
  PpdFiles:
   Lexmark-W820-Bravo: Lexmark W820 PS
   HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: HP LaserJet 500 color 
M551, driverless, cups-filters 1.20.2
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct 
i8042.dumbkbd vt.handoff=1
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct 
i8042.dumbkbd vt.handoff=1
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
   __libc_start_main (main=0x55f0c84c81b0, argc=3, argv=0x7ffcaf592438, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcaf592428) at ../csu/libc-start.c:310
  Title: dbus crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (37 days ago)
  UserGroups:
   
  dmi.bios.date: 12/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.asset.tag: 0004061282
  dmi.board.name: 0520M8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 0004061282
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/07/2012:svnDellInc.:pnXPS129Q23:pvrA05:rvnDellInc.:rn0520M8:rvrA00:cvnDellInc.:ct8:cvrA05:
  dmi.product.family: 103C_5335KV
  dmi.product.name: XPS 12 9Q23
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1764860/+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 1763829] Re: [snap] chromium won't start after logging in to google account

[Olivier Tilloy]

The fix is in the candidate channel for all supported architectures now.
I'll leave it there for a couple of days to give people an opportunity to test 
and report, after which I will promote to the stable channel in no issue is 
raised.

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

Title:
  [snap] chromium won't start after logging in to google account

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (issue initially reported on the forum: https://forum.snapcraft.io/t
  /call-for-testing-chromium-65-0-3325-146/4390/20)

  $ snap info core chromium | egrep "name|installed"
  name:  core
  installed:   16-2.32.3(4407) 90MB core
  name:  chromium
  installed:   65.0.3325.181 (274)  144MB -

  Steps to reproduce:
  1) Install the chromium snap: snap install chromium
  2) Launch it: /snap/bin/chromium
  3) Click the account button on the right side of the tabs bar, and log into a 
google account
  4) Close the browser window
  5) Launch chromium again

  Expected result: chromium launches, a window is shown and the user is
  logged into their google account

  Current result: the executable seemingly hangs, no window is shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1763829/+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 1764161] Re: Translation template for ibus is missing some strings

[Sebastien Bacher]

The use of dh-translations was removed without explanation in that upload
http://launchpadlibrarian.net/227995812/ibus_1.5.10-1ubuntu1_1.5.11-1ubuntu1.diff.gz

I just did an upload adding the build-depends and rules translations use

** Changed in: ibus (Ubuntu)
   Importance: Medium => High

** Changed in: ibus (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+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 1764865] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2()

[Apport retracing service]

*** This bug is a duplicate of bug 1755017 ***
https://bugs.launchpad.net/bugs/1755017

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 #1755017, 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/1764865/+attachment/5120062/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1764865

Title:
  usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2()

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  don't know how to reproduce it, just crash arrived at startup

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: usb-modeswitch 2.5.2+repack0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 22:59:46 2018
  ExecutablePath: /usr/sbin/usb_modeswitch_dispatcher
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: /usr/sbin/usb_modeswitch_dispatcher --switch-mode 1-9
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7fb7c8dfb3d7 <__strrchr_avx2+23>:vmovdqu 
(%rdi),%ymm1
   PC (0x7fb7c8dfb3d7) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: usb-modeswitch
  StacktraceTop:
   __strrchr_avx2 () at ../sysdeps/x86_64/multiarch/strrchr-avx2.S:54
   ?? ()
   __libc_start_main (main=0x55cc8caf0b70, argc=3, argv=0x7fff7edcf798, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff7edcf788) at ../csu/libc-start.c:310
   ?? ()
  Title: usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1764865/+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 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

Or, even better, a real upload which fixes the issue also going forward.
:) Sebastien let me know on IRC what's needed, so I wrote a patch.

** Patch added: "ibus_lp1764161.debdiff"
   
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+attachment/5120061/+files/ibus_lp1764161.debdiff

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ibus (Ubuntu)
   Status: New => In Progress

** Changed in: ibus (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: patch

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+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 1764862] Re: unity-settings-daemon crashed with signal 5

[Apport retracing service]

*** This bug is a duplicate of bug 1727648 ***
https://bugs.launchpad.net/bugs/1727648

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 #1727648, 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/1764862/+attachment/5120029/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1764862

Title:
  unity-settings-daemon crashed with signal 5

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: unity-settings-daemon 15.04.1+18.04.20180216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Apr 17 23:18:48 2018
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2018-03-11 (37 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   () at /usr/lib/unity-settings-daemon-1.0/libxrandr.so
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: unity-settings-daemon crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (37 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1764862/+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 1764078] Re: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  in 16.04 i shifted meenubuttons to the right

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: gnome-menus 3.13.3-6ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sun Apr 15 09:31:35 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  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: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to artful on 2018-04-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1764078/+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 1763662] Re: H264 missing from WebRTC (regression)

[Olivier Tilloy]

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  H264 missing from WebRTC (regression)

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  H264 is missing from WebRTC in Chromium 65.0.3325.181.
  This is a regression. It worked in Chromium 64.0.3282.167.
  According to the webrtc team it might be because of a missing flag [1].

  Steps to reproduce:
  1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser 
chromium-codecs-ffmpeg-extra
  2. open a tab with chrome://webrtc-internals
  3. Create a room in https://appr.tc and join the room.
  3. Check the SDP offer in webrtc-internals. Select the 
https://appr.tc/r/ tab and click on the createOfferOnSuccess event.

  We should have H264 in the SDP offer but it's missing:
  a=rtpmap:100 H264/9

  [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1763662/+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 1764648] Re: Read pixels broken in Chrome/Chromium on 18.04 using the NVIDIA driver

[Olivier Tilloy]

According to the upstream bug report this is fixed in chromium 66, which
is currently in beta and will be released to the stable channel this
week.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Read pixels broken in Chrome/Chromium on 18.04 using the NVIDIA driver

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  2 ways to reproduce:
  1) Go to 
https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html 
and run the all/conformance/reading tests.
  2) Go to photoeditor.polarr.co. Select the Pro workspace. Skip the tutorial. 
Press F to open the filters panel (or click the 3 circle icon on the left). All 
of the filter previews will be garbled or black for any image that you edit.

  I've tried this on 2 computers, one with a 980, and one with a 1070.
  They both fail on Ubuntu 18.04 but work correctly on 16.04 and 17.10.
  Firefox works correctly. I attempted to use the Noveau driver, but I
  got a max resolution of 640p and WebGL didn't work at all so far as I
  could tell.

  I've tried running my Polarr photo editor (an Electron app) on 18.04,
  and it also doesn't work correctly any more.

  This is what I get in the terminal for chromium-browser when I run the WebGL 
conformance tests for reading pixels:
  amiller@amiller-All-Series:~$ chromium-browser 
  [4775:4775:0417/30.985800:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.986559:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.987074:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.987630:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Tue Apr 17 00:06:03 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2018-04-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Sat Apr  7 06:58:00 2018)
  Load-Avg-1min: 0.29
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=a9752952-f843-46f2-9206-e16c858d6d33 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-17 (0 days ago)
  dmi.bios.date: 12/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1203
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1203:bd12/10/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1764648/+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 1759540] Re: [MIR] ubuntu-report: send telemetry data to ubuntu server

[Sebastien Bacher]

The issue got discussed on IRC, as written in the description the upstream 
projects include a vendors/ subdir with those components, we didn't use that 
because we though using the distribution versions was the preferred way. We are 
going to switch back to use the vendors/ copies instead (which e.g snapd is 
doing), could someone from the MIR team review the source again with that in 
mind and confirm it's ok?
The upstream source including the vendors bundle can be found on 
https://github.com/ubuntu/ubuntu-report

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

Title:
  [MIR] ubuntu-report: send telemetry data to ubuntu server

Status in ubuntu-report package in Ubuntu:
  Incomplete

Bug description:
  Note that only the C library ("libsysmetrics1") and the command line
  ("ubuntu-report") packages are needed in main (we should also promote
  "libsysmetrics-dev" package, even if not necessary). We don't need the
  Go API "golang-github-ubuntu-ubuntu-report-dev" which has many go
  package dependencies in universe.

  [Availability]
  Available and built on all archs.

  [Rationale]
  We want to provide telemetry upload features, collected by ubiquity, 
do-release-upgrader and that package in ubnutu 18.04. see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755456 for more 
rationales and details.

  [Security]
  No security issue reported, as brand new package.
  The package do a POST message over https to an ubuntu server, data being sent 
are really limited to garantee anynomous informations.
  See example of what is sent on https://github.com/ubuntu/ubuntu-report README.

  [Quality assurance]
  The canonical desktop team is the upstream maintainer and will continue 
maintening it.
  Upstream has CI built-in on every commit + coverage report. The package build 
and runs (currently) 243 tests from unit to integration tests. Autopkgtests 
ensuring that building works and tests still pass is also provided.

  In addition the documentation and C API are continously strongly
  tested (with examples extracted from the documentation, built, linked
  against a on-demand generated C library, and tests ran against it).

  [Dependencies]
  Upstream is using a vendor/ directory, but the ubuntu package remove it on 
build and use the distribution packaged build-deps equivalent.
  No runtime dep in the 3 packages that needs to be promoted.

  [Standards compliance]
  Package follow latest debian packaging standard compliant. No lintian 
override files, and binaries/packages follows Debian standard FHS. Note that 
there is no .symbols file as the generated C API export internal symbols 
(starting with _) which names contains a hash dependant of the source file, and 
per arch specific. The exported symbols from the public API have a stable name 
though: https://godoc.org/github.com/ubuntu/ubuntu-report/pkg/sysmetrics/C

  [Maintenance]
  Canonical desktop team being the usptream and downstream maintainer, strongly 
backed by tests, will follow bugs and maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1759540/+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 1759590] Re: Chromium-Browser Won't Sustain My Profile

[Lonnie Lee Best]

I just reinstalled the latest build of Ubuntu 18.04. I still have the
same problem with Chromium.

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

Title:
  Chromium-Browser Won't Sustain My Profile

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Each time I launch chromium-browser it forgets all previous sessions;
  it doesn't remember any saved passwords, history, bookmarks, or form
  data.

  It seem like it is creating a brand new profile each launch.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 09:21:18 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-02-09 (47 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Load-Avg-1min: 1.37
  Load-Processes-Running-Percent:   0.1%
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=41d735c2-7b0b-4553-8de3-78761dcbc4f5 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-03-28 (0 days ago)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.chromium-browser.customizations.00-example: [deleted]
  modified.conffile..etc.chromium-browser.default: [deleted]
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1759590/+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 1761995] Re: Error Formatting luks device

[dino99]

udisks2 2.7.6-2ubuntu6 "suggests" libblockdev-crypto2;

that needs to be set to "recommends" at least.

** Changed in: udisks
   Status: New => Confirmed

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

Title:
  Error Formatting luks device

Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in meta-gnome3 package in Ubuntu:
  Confirmed

Bug description:
  Application Gnome Disks

  When trying to format an encrypted drive I get this error:

  Error formatting volume

  Error creating the luks device:The function
  'bd_crypto_luks_format_blob' called, but not implemented! (udisks-
  error-quark,0)

  1. Description:   Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. GNOME Disks 3.28.0-1ubuntu1

  3. LUKS formatting disk should work

  4. error message when opting for password protect volume (LUKS)
  utilizing format volume

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 09:46:19 2018
  InstallationDate: Installed on 2018-03-12 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/1761995/+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 1364173] Re: Xsession sourced scripts shouldn't be run using user's default shell

[Bug Watch Updater]

** Changed in: kdebase-workspace
   Status: New => Unknown

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

Title:
  Xsession sourced scripts shouldn't be run using user's default shell

Status in KDE Base Workspace:
  Unknown
Status in kde-workspace package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Recently I encountered a problem that my input method malfunctions
  because the environmental variables are wrongly set(which is, fully
  configured using im-config), after hours of debugging I found that
  it's Z-shell(my current default shell)'s bug that prematurely quits
  before the Xsession.d im-config input method configure script
  completes.

  The problem is, /etc/X11/Xsession (and all the Xsession.d scripts it sourced) 
**shouldn't** be run in Z-shell.  Patching /etc/kde4/kdm/Xsession # invoke 
global X session script. code from
  . /etc/X11/Xsession
  to
  /etc/X11/Xsession

  workarounded the issue (however I have no idea why).  Switching to
  other display managers instead of KDM worked also)

  Reproducible: Always

  Steps to Reproduce:
  Currently there's no simple reproduce method as another software(zsh)'s bug 
involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1364173/+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 1761995] Re: Error Formatting luks device

[N1ck 7h0m4d4k15]

I can confirm what Sebastien proposed. Installing libblockdev-crypto2 and 
restarting the udisks2.service did the trick. 
Also it maybe worth mention that in my case the installation of Ubuntu 
18.04(beta2) performed with the new "minimal installation" option.

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

Title:
  Error Formatting luks device

Status in udisks:
  New
Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in meta-gnome3 package in Ubuntu:
  Confirmed

Bug description:
  Application Gnome Disks

  When trying to format an encrypted drive I get this error:

  Error formatting volume

  Error creating the luks device:The function
  'bd_crypto_luks_format_blob' called, but not implemented! (udisks-
  error-quark,0)

  1. Description:   Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. GNOME Disks 3.28.0-1ubuntu1

  3. LUKS formatting disk should work

  4. error message when opting for password protect volume (LUKS)
  utilizing format volume

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 09:46:19 2018
  InstallationDate: Installed on 2018-03-12 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/1761995/+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 1764648] Re: Read pixels broken in Chrome/Chromium on 18.04 using the NVIDIA driver

[dmiller309]

I filed an upstream bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=833984

I saw the issue a couple weeks ago but waited to report it because
Ubuntu 18.04 is still in beta. 18.04 is scheduled for release next week
though, so it would be ideal if the issue was resolved before then.

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

Title:
  Read pixels broken in Chrome/Chromium on 18.04 using the NVIDIA driver

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  2 ways to reproduce:
  1) Go to 
https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html 
and run the all/conformance/reading tests.
  2) Go to photoeditor.polarr.co. Select the Pro workspace. Skip the tutorial. 
Press F to open the filters panel (or click the 3 circle icon on the left). All 
of the filter previews will be garbled or black for any image that you edit.

  I've tried this on 2 computers, one with a 980, and one with a 1070.
  They both fail on Ubuntu 18.04 but work correctly on 16.04 and 17.10.
  Firefox works correctly. I attempted to use the Noveau driver, but I
  got a max resolution of 640p and WebGL didn't work at all so far as I
  could tell.

  I've tried running my Polarr photo editor (an Electron app) on 18.04,
  and it also doesn't work correctly any more.

  This is what I get in the terminal for chromium-browser when I run the WebGL 
conformance tests for reading pixels:
  amiller@amiller-All-Series:~$ chromium-browser 
  [4775:4775:0417/30.985800:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.986559:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.987074:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer
  [4775:4775:0417/30.987630:ERROR:gles2_cmd_decoder.cc(12024)] 
[.Offscreen-For-WebGL-0x55577c136f80]GL ERROR :GL_INVALID_OPERATION : 
glReadPixels: format and type incompatible with the current read framebuffer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Tue Apr 17 00:06:03 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2018-04-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Sat Apr  7 06:58:00 2018)
  Load-Avg-1min: 0.29
  Load-Processes-Running-Percent:   0.1%
  MachineType: ASUS All Series
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=a9752952-f843-46f2-9206-e16c858d6d33 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-17 (0 days ago)
  dmi.bios.date: 12/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1203
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1203:bd12/10/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1764648/+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 905022] Re: No sounds from headphones on ThinkPad T420

[Chris Kirby]

Wow, this is a blast from the past. That bug was probably one or two
machines ago and I no longer have the hardware to test / reproduce it.
This can be closed.

> On Apr 17, 2018, at 10:37, Rolf Leggewie <905...@bugs.launchpad.net> wrote:
> 
> Sorry for the long delay.  Is this something that still affects Xenial
> or later?
> 
> ** Changed in: alsa-driver (Ubuntu)
>   Status: Confirmed => Incomplete
> 
> ** Changed in: alsa-driver (Ubuntu)
> Assignee: (unassigned) => Rolf Leggewie (r0lf)
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/905022
> 
> Title:
>  No sounds from headphones on ThinkPad T420
> 
> Status in alsa-driver package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Long time reader, first time poster :-)
> 
>  I cannot get sound from the analog headphone/microphone port on my
>  Lenovo ThinkPad T420. Based on Google searches I have fiddled with the
>  snd-hda-intel options in /etc/modprobe.d/alsa-base.conf as follows:
> 
>  - Set model=thinkpad resulting in no sound through the headphone jack
>  and the loss of the headphone playback connector in alsamixer.
>  Unsurprisingly this results in no option to set or configure the
>  analog headphone connector in the sound settings applet and/or
>  pavucontrol.
> 
>  - Set model=generic with the same results as above.
> 
>  - Set model=auto which resulted in the appearance of the headphone
>  connector (progress!) but I still get no sound from the headphones
>  when I select the connector and/or mute the speakers through
>  alsamixer.
> 
>  I also tried re-configuring the alsa-driver package to include verbose
>  debugging support but ran into a whole lot of hassles (some of the
>  source references smp_lock.h which is no more in kernel 3+, macro
>  conflicts with system includes, etc.) when I tried to build it with
>  module-assistant. I also tried to build it from the latest tarball
>  from the alsa project with mixed results and ultimately no joy.
> 
>  Most problems of this kind I've seen tend to fall into 3 categories:
>  (i) fixed by changing snd-hda-intel options, (ii) fixed through some
>  sequence of random updates, (iii) sitting in silence. I'm hoping to be
>  a bit more proactive.
> 
>  The output of alsa-info.sh is attached.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/905022/+subscriptions

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

Title:
  No sounds from headphones on ThinkPad T420

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Long time reader, first time poster :-)

  I cannot get sound from the analog headphone/microphone port on my
  Lenovo ThinkPad T420. Based on Google searches I have fiddled with the
  snd-hda-intel options in /etc/modprobe.d/alsa-base.conf as follows:

  - Set model=thinkpad resulting in no sound through the headphone jack
  and the loss of the headphone playback connector in alsamixer.
  Unsurprisingly this results in no option to set or configure the
  analog headphone connector in the sound settings applet and/or
  pavucontrol.

  - Set model=generic with the same results as above.

  - Set model=auto which resulted in the appearance of the headphone
  connector (progress!) but I still get no sound from the headphones
  when I select the connector and/or mute the speakers through
  alsamixer.

  I also tried re-configuring the alsa-driver package to include verbose
  debugging support but ran into a whole lot of hassles (some of the
  source references smp_lock.h which is no more in kernel 3+, macro
  conflicts with system includes, etc.) when I tried to build it with
  module-assistant. I also tried to build it from the latest tarball
  from the alsa project with mixed results and ultimately no joy.

  Most problems of this kind I've seen tend to fall into 3 categories:
  (i) fixed by changing snd-hda-intel options, (ii) fixed through some
  sequence of random updates, (iii) sitting in silence. I'm hoping to be
  a bit more proactive.

  The output of alsa-info.sh is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/905022/+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 1764829] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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 #1748450, 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/1764829/+attachment/5119832/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  nothing seemed to happened but a system crash popup window appeared
  but it still functioned and sent me here to report it.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Apr 17 13:35:35 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-15 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2018-04-17 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764829/+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 1758459] Re: Getting 2.93 in Bionic

[Bug Watch Updater]

** Changed in: transmission (Debian)
   Status: New => Confirmed

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

Title:
  Getting 2.93 in Bionic

Status in transmission package in Ubuntu:
  Confirmed
Status in transmission package in Debian:
  Confirmed

Bug description:
  As referenced on #1752940 some trackers have started blacklisting
  Transmission versions below 2.93 on the basis that they have no way of
  telling if an older version has been patched for CVE-2018-5702 or not.

  Can we try to get 2.93 in Bionic before the final freeze, especially
  since this is an LTS and 2.92 is starting to get old (Apr 9, 2016).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1758459/+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 1761995] Re: Error Formatting luks device

[Jesse]

Hi Sebastien, yeah actually I did it right after reporting this bug.
Installing libblockdev-crypto2 and restarting udisks2 service made it
work!

Do you think we should categorize this under udisks2?

** Also affects: udisks
   Importance: Undecided
   Status: New

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

Title:
  Error Formatting luks device

Status in udisks:
  New
Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in meta-gnome3 package in Ubuntu:
  Confirmed

Bug description:
  Application Gnome Disks

  When trying to format an encrypted drive I get this error:

  Error formatting volume

  Error creating the luks device:The function
  'bd_crypto_luks_format_blob' called, but not implemented! (udisks-
  error-quark,0)

  1. Description:   Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. GNOME Disks 3.28.0-1ubuntu1

  3. LUKS formatting disk should work

  4. error message when opting for password protect volume (LUKS)
  utilizing format volume

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 09:46:19 2018
  InstallationDate: Installed on 2018-03-12 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Apport retracing service]

*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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 #1748450, 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/1764828/+attachment/5119822/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When start.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Apr 17 13:27:20 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-15 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.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: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764828/+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 1764827] [NEW] sometimes, maybe after pluging in headphones, there is no sound. Sound goes thrue , , dummy output''

[Lukas Birstonas]

Public bug reported:

No sound. Sound goes to dummy output

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lukasbirstonas   1259 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 21:25:57 2018
InstallationDate: Installed on 2017-12-02 (136 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Front
Title: [20CD0034UK, Conexant CX20751/2, Green Headphone Out, Front] Pulseaudio 
fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GQET35WW (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CD0034UK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50518 Std
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGQET35WW(1.15):bd04/21/2014:svnLENOVO:pn20CD0034UK:pvrThinkPadS1Yoga:rvnLENOVO:rn20CD0034UK:rvrSDK0E50518Std:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad S1 Yoga
dmi.product.name: 20CD0034UK
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  sometimes, maybe after pluging in headphones, there is no sound. Sound
  goes thrue ,,dummy output''

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound. Sound goes to dummy output

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lukasbirstonas   1259 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 21:25:57 2018
  InstallationDate: Installed on 2017-12-02 (136 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Title: [20CD0034UK, Conexant CX20751/2, Green Headphone Out, Front] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET35WW (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CD0034UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50518 Std
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET35WW(1.15):bd04/21/2014:svnLENOVO:pn20CD0034UK:pvrThinkPadS1Yoga:rvnLENOVO:rn20CD0034UK:rvrSDK0E50518Std:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad S1 Yoga
  dmi.product.name: 20CD0034UK
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1764827/+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 1764042] Re: wifi crashes in ubuntu 16.04 lts xenial

[israel oluwole]

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/network-manager/+question/668023

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Good day,
  I am a new ubuntu user and I've been finding a solution everywhere to this 
issue:
  I run ubuntu (studio) 16.04 lts, code name: xenial dual booted with windows 8 
on Hp notebook 15. When I first installed ubuntu, hotspot from my BlackBerry 
q10 connects fine but suddenly it stopped and every time i connect it pops up 
the dialog box: wifi authentication required by wifi network and expects me to 
retype a password that is already correct!
  I have tried reinstalling network manager, adding [device] wifi-rand*... to 
network*.conf and so on and rebooted over and again. Nothing has changed yet. 
The same applies to my bluetooth too (it was okay suddenly it changed)

  I need help quick, I need my pc for an imminent exam. Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1764042/+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 1764819] [NEW] CredSSP v6 on Bionic not supported freerdp2

[Michael LoBianco]

Public bug reported:

On 18.04 Bionic Beaver, version 2.0.0-rc2 of freerdp2 is needed in order
to support CredSSP v6. After the release of KB4088776, I'm unable to
remote into certain Windows machines.

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

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

Title:
  CredSSP v6 on Bionic not supported freerdp2

Status in freerdp2 package in Ubuntu:
  New

Bug description:
  On 18.04 Bionic Beaver, version 2.0.0-rc2 of freerdp2 is needed in
  order to support CredSSP v6. After the release of KB4088776, I'm
  unable to remote into certain Windows machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1764819/+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 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

Not sure. Possibly a no-change rebuild would make a difference now when
an up-to-date template is in. But for that we need a developer who has
time to do it by tomorrow. You may want to wait another day before doing
it manually.

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+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 1759540] Re: [MIR] ubuntu-report: send telemetry data to ubuntu server

[Steve Langasek]

>  We don't need the Go API "golang-github-ubuntu-ubuntu-report-dev"
> which has many go package dependencies in universe.

Unfortunately, listing golang-github-ubuntu-ubuntu-report-dev is not
sufficient to keep the go tree out of main.  ubuntu-report is itself
implemented in go, which means it statically links all the various go
libraries that it uses.  The closure of main traverses Depends,
Recommends, and also Built-Using - specifically to ensure that
statically-linked code included in a binary in main doesn't go unnoticed
and missed wrt security support.

So there is in fact a tremendous dependency tree that you would need to
MIR in order to ship ubuntu-report in main, as shown at
.
I don't think it's realistic to have these dependencies addressed in
time for release, and would recommend withdrawing this MIR for 18.04
(and unseeding the package).

** Changed in: ubuntu-report (Ubuntu)
   Status: Fix Released => Incomplete

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

Title:
  [MIR] ubuntu-report: send telemetry data to ubuntu server

Status in ubuntu-report package in Ubuntu:
  Incomplete

Bug description:
  Note that only the C library ("libsysmetrics1") and the command line
  ("ubuntu-report") packages are needed in main (we should also promote
  "libsysmetrics-dev" package, even if not necessary). We don't need the
  Go API "golang-github-ubuntu-ubuntu-report-dev" which has many go
  package dependencies in universe.

  [Availability]
  Available and built on all archs.

  [Rationale]
  We want to provide telemetry upload features, collected by ubiquity, 
do-release-upgrader and that package in ubnutu 18.04. see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755456 for more 
rationales and details.

  [Security]
  No security issue reported, as brand new package.
  The package do a POST message over https to an ubuntu server, data being sent 
are really limited to garantee anynomous informations.
  See example of what is sent on https://github.com/ubuntu/ubuntu-report README.

  [Quality assurance]
  The canonical desktop team is the upstream maintainer and will continue 
maintening it.
  Upstream has CI built-in on every commit + coverage report. The package build 
and runs (currently) 243 tests from unit to integration tests. Autopkgtests 
ensuring that building works and tests still pass is also provided.

  In addition the documentation and C API are continously strongly
  tested (with examples extracted from the documentation, built, linked
  against a on-demand generated C library, and tests ran against it).

  [Dependencies]
  Upstream is using a vendor/ directory, but the ubuntu package remove it on 
build and use the distribution packaged build-deps equivalent.
  No runtime dep in the 3 packages that needs to be promoted.

  [Standards compliance]
  Package follow latest debian packaging standard compliant. No lintian 
override files, and binaries/packages follows Debian standard FHS. Note that 
there is no .symbols file as the generated C API export internal symbols 
(starting with _) which names contains a hash dependant of the source file, and 
per arch specific. The exported symbols from the public API have a stable name 
though: https://godoc.org/github.com/ubuntu/ubuntu-report/pkg/sysmetrics/C

  [Maintenance]
  Canonical desktop team being the usptream and downstream maintainer, strongly 
backed by tests, will follow bugs and maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1759540/+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 1764805] Re: gvfsd-smb-browse crashed with SIGSEGV in tevent_common_schedule_immediate()

[Apport retracing service]

*** This bug is a duplicate of bug 1760620 ***
https://bugs.launchpad.net/bugs/1760620

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 #1760620, 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/1764805/+attachment/5119750/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  gvfsd-smb-browse crashed with SIGSEGV in
  tevent_common_schedule_immediate()

Status in gvfs package in Ubuntu:
  New

Bug description:
  opened Gnome Tweaks tool, clicked on Extensions, noticed "Activities
  configurator" extension had an "Update" button next to it. Clicked it.
  Accepted prompt to update the extension. 20 seconds later crash
  occurred.

  Also lost side bar menu.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Apr 17 18:06:46 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2018-01-28 (78 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.15 
/org/gtk/gvfs/exec_spaw/13
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f0ff5546e94:mov0x10(%rdi),%rdi
   PC (0x7f0ff5546e94) ok
   source "0x10(%rdi)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
   tevent_common_schedule_immediate () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
   tevent_req_post () from /usr/lib/x86_64-linux-gnu/libtevent.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/samba/libsamba-sockets.so.0
   tdgram_sendto_send () from 
/usr/lib/x86_64-linux-gnu/samba/libsamba-sockets.so.0
  Title: gvfsd-smb-browse crashed with SIGSEGV in 
tevent_common_schedule_immediate()
  UpgradeStatus: Upgraded to bionic on 2018-03-14 (33 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1764805/+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 1764005] Re: Black-screen on boot with nvidia 390 for GTX 960M

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-prime (Ubuntu)
   Status: New => Confirmed

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

Title:
  Black-screen on boot with nvidia 390 for GTX 960M

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1764005/+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 1764005] Re: Black-screen on boot with nvidia 390 for GTX 960M

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Black-screen on boot with nvidia 390 for GTX 960M

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1764005/+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 1764005] Re: Black-screen on boot with nvidia 390 for GTX 960M

[Martin Wimpress]

** Also affects: nvidia-prime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Black-screen on boot with nvidia 390 for GTX 960M

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1764005/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Pioterus]

This bug forced me to search for ubuntu alternatives. I'm looking
currently at Manjaro.

About commenting out dns=dnsmasq.
Doing so on laptop (LAN and wifi connections active) has this drawback:
ping my_comp_name
.unresloved name
adding my_comp_name to /etc/hosts  makes the ping my_comp_name  working again, 
but 
unplagging RJ45, system changes automatically to wifi connetcion (other IP) and 
ping my_comp_name again is not working. With dnsmasq enabled the system nicely 
deals with name resolution so there are no such issues. What happens when the 
host name resolution is not working ok? System behaves oddly (it delays some 
operations in many situations).

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1764803] [NEW] failed install of nvidia-drivers-390

[Dean ford]

Public bug reported:

insulation method using ubuntu-driver, blacklisting nouveau.
also tried with the ppa added and driver from nvidia.com. All failed which 
hasnt happed before when installing (K)ubuntu 

Black screen after reboot
GPU running hot
Kubuntu 18.04 final beta

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks
Date: Tue Apr 17 17:30:25 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0504]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 620M/630M/635M/640M 
LE] [1025:0505]
InstallationDate: Installed on 2018-04-12 (4 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: Acer Aspire 5755G
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=7ce01f2b-9fff-47af-a177-4bb10ec8e87f ro acpi_osi=Linux 
acpi_backlight=vendor quiet nomodset splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JV51_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.15
dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5755G:pvrV1.15:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15:
dmi.product.name: Aspire 5755G
dmi.product.version: V1.15
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  failed install of nvidia-drivers-390

Status in xorg package in Ubuntu:
  New

Bug description:
  insulation method using ubuntu-driver, blacklisting nouveau.
  also tried with the ppa added and driver from nvidia.com. All failed which 
hasnt happed before when installing (K)ubuntu 

  Black screen after reboot
  GPU running hot
  Kubuntu 18.04 final beta

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks
  Date: Tue Apr 17 17:30:25 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 

[Desktop-packages] [Bug 1764427] Re: USB/HDMI monitor config for multiple frequencies aren't supported

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-report - 1.0.8

---
ubuntu-report (1.0.8) bionic; urgency=medium

  * Handle complex screen config with multiple frequencies (LP: #1764427)
  * Configure timeout to client for https POST request (LP: #1764655)
  * List architecture as part of POST data (LP: #1764673)
  * All 3 items above are covered by new tests

 -- Didier Roche   Tue, 17 Apr 2018 10:31:49 +0200

** Changed in: ubuntu-report (Ubuntu)
   Status: New => Fix Released

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

Title:
   USB/HDMI monitor config for multiple frequencies aren't supported

Status in ubuntu-report package in Ubuntu:
  Fix Released

Bug description:
  Here is an example: http://paste.ubuntu.com/p/8rv7jg7HZv/

  Note the xrandr lines are generally:
  1920x1080 59.93*+

  But some other form (multiple frequencies with some hardware) are possible:
  3840x2160 30.00*+ 25.00 24.00 23.98

  And also:
  1920x1080 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98.

  We should support those (the regexp is restrictive in that form).
  Will add a test with the above example xrandr.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1764427/+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 1764655] Re: Configure timeout to client for https POST request

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-report - 1.0.8

---
ubuntu-report (1.0.8) bionic; urgency=medium

  * Handle complex screen config with multiple frequencies (LP: #1764427)
  * Configure timeout to client for https POST request (LP: #1764655)
  * List architecture as part of POST data (LP: #1764673)
  * All 3 items above are covered by new tests

 -- Didier Roche   Tue, 17 Apr 2018 10:31:49 +0200

** Changed in: ubuntu-report (Ubuntu)
   Status: New => Fix Released

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

Title:
  Configure timeout to client for https POST request

Status in ubuntu-report package in Ubuntu:
  Fix Released

Bug description:
  In case the server hangs, ensure we have a reasonable client connexion
  timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1764655/+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 1764673] Re: List architecture as part of POST data

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-report - 1.0.8

---
ubuntu-report (1.0.8) bionic; urgency=medium

  * Handle complex screen config with multiple frequencies (LP: #1764427)
  * Configure timeout to client for https POST request (LP: #1764655)
  * List architecture as part of POST data (LP: #1764673)
  * All 3 items above are covered by new tests

 -- Didier Roche   Tue, 17 Apr 2018 10:31:49 +0200

** Changed in: ubuntu-report (Ubuntu)
   Status: New => Fix Released

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

Title:
  List architecture as part of POST data

Status in ubuntu-report package in Ubuntu:
  Fix Released

Bug description:
  The installation media (32 or 64 bits) is reflected in the install
  stenza (doesn't work for upgrade though). We initially thought that we
  would derivate the architecture from CPU information.

  However, arm* doesn't report any information enabling us getting the
  system architecture. Ensure we report it thus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1764673/+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 905022] Re: No sounds from headphones on ThinkPad T420

[Rolf Leggewie]

Sorry for the long delay.  Is this something that still affects Xenial
or later?

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => Rolf Leggewie (r0lf)

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

Title:
  No sounds from headphones on ThinkPad T420

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Long time reader, first time poster :-)

  I cannot get sound from the analog headphone/microphone port on my
  Lenovo ThinkPad T420. Based on Google searches I have fiddled with the
  snd-hda-intel options in /etc/modprobe.d/alsa-base.conf as follows:

  - Set model=thinkpad resulting in no sound through the headphone jack
  and the loss of the headphone playback connector in alsamixer.
  Unsurprisingly this results in no option to set or configure the
  analog headphone connector in the sound settings applet and/or
  pavucontrol.

  - Set model=generic with the same results as above.

  - Set model=auto which resulted in the appearance of the headphone
  connector (progress!) but I still get no sound from the headphones
  when I select the connector and/or mute the speakers through
  alsamixer.

  I also tried re-configuring the alsa-driver package to include verbose
  debugging support but ran into a whole lot of hassles (some of the
  source references smp_lock.h which is no more in kernel 3+, macro
  conflicts with system includes, etc.) when I tried to build it with
  module-assistant. I also tried to build it from the latest tarball
  from the alsa project with mixed results and ultimately no joy.

  Most problems of this kind I've seen tend to fall into 3 categories:
  (i) fixed by changing snd-hda-intel options, (ii) fixed through some
  sequence of random updates, (iii) sitting in silence. I'm hoping to be
  a bit more proactive.

  The output of alsa-info.sh is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/905022/+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 1764161] Re: Translation template for ibus is missing some strings

[AsciiWolf]

Should I add the missing Czech translated strings manually?

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+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 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

I noticed that dh-translations is not in Build-Depends, so I added cdbs
to Build-Depends to pull it and uploaded to PPA, but the dh_translations
program was still not run according to the build log.

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+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 1762235] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy()

[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/1762235

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from
  nm_ip_address_dup() from g_boxed_copy()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Apr  8 20:57:53 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-18 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8db9b994f4 :mov
0x44(%rsi),%eax
   PC (0x7f8db9b994f4) ok
   source "0x44(%rsi)" (0x3838342032313176) not located in a known VMA region 
(needed readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_hash_table_iter_init () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   g_boxed_copy () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gjs_boxed_from_c_struct () at /usr/lib/libgjs.so.0
   gjs_value_from_g_argument () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init()
  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/1762235/+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 1759540] Re: [MIR] ubuntu-report: send telemetry data to ubuntu server

[Steve Langasek]

Override component to main
ubuntu-report 1.0.7 in bionic: universe/utils -> main
1 publication overridden.
Override component to main
ubuntu-report 1.0.7 in bionic amd64: universe/utils/optional/100% -> main
ubuntu-report 1.0.7 in bionic arm64: universe/utils/optional/100% -> main
ubuntu-report 1.0.7 in bionic armhf: universe/utils/optional/100% -> main
ubuntu-report 1.0.7 in bionic i386: universe/utils/optional/100% -> main
ubuntu-report 1.0.7 in bionic ppc64el: universe/utils/optional/100% -> main
ubuntu-report 1.0.7 in bionic s390x: universe/utils/optional/100% -> main
libsysmetrics1 1.0.7 in bionic amd64: universe/libs/optional/100% -> main
libsysmetrics1 1.0.7 in bionic arm64: universe/libs/optional/100% -> main
libsysmetrics1 1.0.7 in bionic armhf: universe/libs/optional/100% -> main
libsysmetrics1 1.0.7 in bionic i386: universe/libs/optional/100% -> main
libsysmetrics1 1.0.7 in bionic ppc64el: universe/libs/optional/100% -> main
libsysmetrics1 1.0.7 in bionic s390x: universe/libs/optional/100% -> main
libsysmetrics-dev 1.0.7 in bionic amd64: universe/devel/optional/100% -> main
libsysmetrics-dev 1.0.7 in bionic arm64: universe/devel/optional/100% -> main
libsysmetrics-dev 1.0.7 in bionic armhf: universe/devel/optional/100% -> main
libsysmetrics-dev 1.0.7 in bionic i386: universe/devel/optional/100% -> main
libsysmetrics-dev 1.0.7 in bionic ppc64el: universe/devel/optional/100% -> main
libsysmetrics-dev 1.0.7 in bionic s390x: universe/devel/optional/100% -> main
18 publications overridden.


** Changed in: ubuntu-report (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] ubuntu-report: send telemetry data to ubuntu server

Status in ubuntu-report package in Ubuntu:
  Fix Released

Bug description:
  Note that only the C library ("libsysmetrics1") and the command line
  ("ubuntu-report") packages are needed in main (we should also promote
  "libsysmetrics-dev" package, even if not necessary). We don't need the
  Go API "golang-github-ubuntu-ubuntu-report-dev" which has many go
  package dependencies in universe.

  [Availability]
  Available and built on all archs.

  [Rationale]
  We want to provide telemetry upload features, collected by ubiquity, 
do-release-upgrader and that package in ubnutu 18.04. see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755456 for more 
rationales and details.

  [Security]
  No security issue reported, as brand new package.
  The package do a POST message over https to an ubuntu server, data being sent 
are really limited to garantee anynomous informations.
  See example of what is sent on https://github.com/ubuntu/ubuntu-report README.

  [Quality assurance]
  The canonical desktop team is the upstream maintainer and will continue 
maintening it.
  Upstream has CI built-in on every commit + coverage report. The package build 
and runs (currently) 243 tests from unit to integration tests. Autopkgtests 
ensuring that building works and tests still pass is also provided.

  In addition the documentation and C API are continously strongly
  tested (with examples extracted from the documentation, built, linked
  against a on-demand generated C library, and tests ran against it).

  [Dependencies]
  Upstream is using a vendor/ directory, but the ubuntu package remove it on 
build and use the distribution packaged build-deps equivalent.
  No runtime dep in the 3 packages that needs to be promoted.

  [Standards compliance]
  Package follow latest debian packaging standard compliant. No lintian 
override files, and binaries/packages follows Debian standard FHS. Note that 
there is no .symbols file as the generated C API export internal symbols 
(starting with _) which names contains a hash dependant of the source file, and 
per arch specific. The exported symbols from the public API have a stable name 
though: https://godoc.org/github.com/ubuntu/ubuntu-report/pkg/sysmetrics/C

  [Maintenance]
  Canonical desktop team being the usptream and downstream maintainer, strongly 
backed by tests, will follow bugs and maintenance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1759540/+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 1764730] Re: package hunspell-hr 1:6.0.3-2 failed to install/upgrade: trying to overwrite '/usr/share/hunspell/hr_HR.aff', which is also in package myspell-hr 20060617-2.4ubunt

[Mattia Rizzolo]

Fix uploaded to Debian, will in sync in ubuntu later on once launchpad
notices the upload.

** Changed in: libreoffice-dictionaries (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: libreoffice-dictionaries (Ubuntu)
   Importance: Medium => Low

** Changed in: libreoffice-dictionaries (Ubuntu)
   Importance: Low => High

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

Title:
  package hunspell-hr 1:6.0.3-2 failed to install/upgrade: trying to
  overwrite '/usr/share/hunspell/hr_HR.aff', which is also in package
  myspell-hr 20060617-2.4ubuntu1

Status in libreoffice-dictionaries package in Ubuntu:
  Fix Committed

Bug description:
  Got this during a dist-upgrade this morning. An "apt install -f"
  resolved it.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hunspell-hr 1:6.0.3-2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Tue Apr 17 08:26:59 2018
  DuplicateSignature:
   package:hunspell-hr:1:6.0.3-2
   Unpacking hunspell-hr (1:6.0.3-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-GbRAvN/15-hunspell-hr_1%3a6.0.3-2_all.deb (--unpack):
trying to overwrite '/usr/share/hunspell/hr_HR.aff', which is also in 
package myspell-hr 20060617-2.4ubuntu1
  ErrorMessage: trying to overwrite '/usr/share/hunspell/hr_HR.aff', which is 
also in package myspell-hr 20060617-2.4ubuntu1
  InstallationDate: Installed on 2017-10-08 (190 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~rc1
  SourcePackage: libreoffice-dictionaries
  Title: package hunspell-hr 1:6.0.3-2 failed to install/upgrade: trying to 
overwrite '/usr/share/hunspell/hr_HR.aff', which is also in package myspell-hr 
20060617-2.4ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1764730/+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 1758070] Re: Switching users takes excessive time

[John Rose]

It's been almost a month since I posted this bug. It would be nice if
someone looked at it.

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

Title:
  Switching users takes excessive time

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  I'm not sure if this is the correct package on which to report this
  problem. Everything fine (took a few seconds) on switching users until
  a couple of days ago. Now it takes approx 30 econds to do so with lots
  of flashing on screen. Also, when user goes away from PC for a while
  and Ubuntu suspends, it displays login screen with Password box
  replaced by "Switch to Greeter". Thus, no obvious way to enter
  password. Clicking on "Switch to Greeter" gives (after a delay) login
  screen with password box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-greeter 16.04.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 22 13:58:18 2018
  InstallationDate: Installed on 2016-12-08 (469 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: unity-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1758070/+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 1597322] Re: necessary sk1libs isn't packaged

[Mattia Rizzolo]

I'm clearly failing to find interest in doing it, mostly because I don't
want to be stuck in maintaining such software I have no interest to (and
uploading and forgetting is something I hate…)

If anybody is actually interested in packaging sk1libs, I'd be happy to
review/sponsor, etc etc.

** Changed in: python-uniconvertor (Ubuntu)
 Assignee: Mattia Rizzolo (mapreri) => (unassigned)

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

Title:
  necessary sk1libs isn't packaged

Status in One Hundred Papercuts:
  Triaged
Status in inkscape package in Ubuntu:
  Invalid
Status in python-uniconvertor package in Ubuntu:
  Triaged
Status in python-uniconvertor package in Debian:
  New

Bug description:
  Hi,

  uniconverter does not work due to missing code:

  % uniconvertor zschloss.eps zschloss.svg
  Traceback (most recent call last):
File "/usr/bin/uniconvertor", line 13, in 
  uniconv_run()
File "/usr/lib/python2.7/dist-packages/uniconvertor/__init__.py", line 83, 
in uniconv_run
  from app.io import load
File "/usr/lib/python2.7/dist-packages/uniconvertor/app/__init__.py", line 
69, in 
  from conf.configurator import Configurator
File 
"/usr/lib/python2.7/dist-packages/uniconvertor/app/conf/configurator.py", line 
11, in 
  from app.events import connector
File "/usr/lib/python2.7/dist-packages/uniconvertor/app/__init__.py", line 
69, in 
  from conf.configurator import Configurator
File 
"/usr/lib/python2.7/dist-packages/uniconvertor/app/conf/configurator.py", line 
13, in 
  from sk1libs.utils.fs import gethome
  ImportError: No module named sk1libs.utils.fs


  See
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820748

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: python-uniconvertor 1.1.5-2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jun 29 14:17:08 2016
  InstallationDate: Installed on 2016-04-22 (67 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  SourcePackage: python-uniconvertor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1597322/+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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

[Jeremy Bicha]

Gunnar, please see my comments at https://gitlab.gnome.org/GNOME/gnome-
shell/issues/109#note_98033

Can we stop setting GTK_IM_MODULE=ibus at least in the GNOME and Ubuntu
sessions?

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

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

  Test Case
  -
  1. Open the Settings app. Click Universal Access.
  2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal 
Access Menu" to make turning the Screen Keyboard on and off easier.)
  3. Open Text Editor
  4. Click the u button on the Screen Keyboard
  5. Long-press the u button on the Screen Keyboard for a few seconds. On the 
popup, click the ü character.

  What Happens
  
  In Step 4, u is entered in the Text Editor document.

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+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 1724188] Re: gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name → get_installed_updates_cb → g_task_return_now → complete_in_idle_cb → g_main_dispatch

[Apport retracing service]

** Tags added: bionic

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

Title:
  gnome-software crashed with SIGSEGV in
  gtk_stack_set_visible_child_name → get_installed_updates_cb →
  g_task_return_now → complete_in_idle_cb → g_main_dispatch

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  crash pop up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.1-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Tue Oct 17 19:53:45 2017
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2017-04-09 (191 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
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7faf066c02c7 :   
mov0x30(%rdi,%rax,1),%edx
   PC (0x7faf066c02c7) ok
   source "0x30(%rdi,%rax,1)" (0xfe80) not located in a known VMA 
region (needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   gtk_stack_set_visible_child_name () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in 
gtk_stack_set_visible_child_name()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1724188/+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 1764515] Re: wifi crashes in ubuntu 16.04 lts xenial

[israel oluwole]

** Description changed:

+ ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. 
+ When I installed ubuntustudio afresh, wifi was alright until recently, 
everyone time I connect to my blackberry mobile hotspot, it pops the dialog 
that "the wifi key is needed for authentication" repeatedly, so it never gets 
connected to the internet through my phone.
+ I have tried reinstalling network manager, restart service through the 
command line , boot and reboot, added [device] wifi.scan.rand line to 
network*.conf.
+ All I mentioned above didnt work
  
- ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When 
I installed afresh, wifi was alright until recently, everyone time I connect, 
it pops the dialog that the wifi key is needed for authentication over and 
again, so it never gets connected to the internet.i have tried reinstalling 
network manager, service restart, boot and reboot, adding [device] 
wifi.scan nothing worked
- What do I need? I barely use windows now 'Cause linux is just dope...‎
+ What do I need do? I barely use windows now 'Cause linux is just
+ dope...‎'

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

Status in linux package in Ubuntu:
  Opinion
Status in network-manager package in Ubuntu:
  New

Bug description:
  ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. 
  When I installed ubuntustudio afresh, wifi was alright until recently, 
everyone time I connect to my blackberry mobile hotspot, it pops the dialog 
that "the wifi key is needed for authentication" repeatedly, so it never gets 
connected to the internet through my phone.
  I have tried reinstalling network manager, restart service through the 
command line , boot and reboot, added [device] wifi.scan.rand line to 
network*.conf.
  All I mentioned above didnt work

  What do I need do? I barely use windows now 'Cause linux is just
  dope...‎'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764515/+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 1764730] Re: package hunspell-hr 1:6.0.3-2 failed to install/upgrade: trying to overwrite '/usr/share/hunspell/hr_HR.aff', which is also in package myspell-hr 20060617-2.4ubunt

[Mattia Rizzolo]

** Changed in: libreoffice-dictionaries (Ubuntu)
 Assignee: (unassigned) => Mattia Rizzolo (mapreri)

** Changed in: libreoffice-dictionaries (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  package hunspell-hr 1:6.0.3-2 failed to install/upgrade: trying to
  overwrite '/usr/share/hunspell/hr_HR.aff', which is also in package
  myspell-hr 20060617-2.4ubuntu1

Status in libreoffice-dictionaries package in Ubuntu:
  Fix Committed

Bug description:
  Got this during a dist-upgrade this morning. An "apt install -f"
  resolved it.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hunspell-hr 1:6.0.3-2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Tue Apr 17 08:26:59 2018
  DuplicateSignature:
   package:hunspell-hr:1:6.0.3-2
   Unpacking hunspell-hr (1:6.0.3-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-GbRAvN/15-hunspell-hr_1%3a6.0.3-2_all.deb (--unpack):
trying to overwrite '/usr/share/hunspell/hr_HR.aff', which is also in 
package myspell-hr 20060617-2.4ubuntu1
  ErrorMessage: trying to overwrite '/usr/share/hunspell/hr_HR.aff', which is 
also in package myspell-hr 20060617-2.4ubuntu1
  InstallationDate: Installed on 2017-10-08 (190 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~rc1
  SourcePackage: libreoffice-dictionaries
  Title: package hunspell-hr 1:6.0.3-2 failed to install/upgrade: trying to 
overwrite '/usr/share/hunspell/hr_HR.aff', which is also in package myspell-hr 
20060617-2.4ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1764730/+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 1764780] Re: gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name()

[Apport retracing service]

*** This bug is a duplicate of bug 1724188 ***
https://bugs.launchpad.net/bugs/1724188

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 #1724188, 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/1764780/+attachment/5119637/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724188
   gnome-software crashed with SIGSEGV in  gtk_stack_set_visible_child_name → 
get_installed_updates_cb → g_task_return_now → complete_in_idle_cb → 
g_main_dispatch

** 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-software in Ubuntu.
https://bugs.launchpad.net/bugs/1764780

Title:
  gnome-software crashed with SIGSEGV in
  gtk_stack_set_visible_child_name()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  na

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 11:09:02 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-04-02 (15 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu3
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fcc86656087 :   
mov0x30(%rdi,%rax,1),%edx
   PC (0x7fcc86656087) ok
   source "0x30(%rdi,%rax,1)" (0xfe80) not located in a known VMA 
region (needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   gtk_stack_set_visible_child_name () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.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
   g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in 
gtk_stack_set_visible_child_name()
  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-software/+bug/1764780/+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 1764515] Re: wifi crashes in ubuntu 16.04 lts xenial

[israel oluwole]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Opinion

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

Status in linux package in Ubuntu:
  Opinion
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When 
I installed afresh, wifi was alright until recently, everyone time I connect, 
it pops the dialog that the wifi key is needed for authentication over and 
again, so it never gets connected to the internet.i have tried reinstalling 
network manager, service restart, boot and reboot, adding [device] 
wifi.scan nothing worked
  What do I need? I barely use windows now 'Cause linux is just dope...‎

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764515/+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 1763829] Re: [snap] chromium won't start after logging in to google account

[Olivier Tilloy]

For reference, the following commits fix the issue:

https://git.launchpad.net/~chromium-team/chromium-browser/+git/snappy-
packaging/commit/?id=5f40c7e269a6990b68669229cf4b7db2c41096bc

https://git.launchpad.net/~chromium-team/chromium-browser/+git/snappy-
packaging/commit/?id=794ef552a18646c2ab03121c695d36ee0791de12

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

Title:
  [snap] chromium won't start after logging in to google account

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (issue initially reported on the forum: https://forum.snapcraft.io/t
  /call-for-testing-chromium-65-0-3325-146/4390/20)

  $ snap info core chromium | egrep "name|installed"
  name:  core
  installed:   16-2.32.3(4407) 90MB core
  name:  chromium
  installed:   65.0.3325.181 (274)  144MB -

  Steps to reproduce:
  1) Install the chromium snap: snap install chromium
  2) Launch it: /snap/bin/chromium
  3) Click the account button on the right side of the tabs bar, and log into a 
google account
  4) Close the browser window
  5) Launch chromium again

  Expected result: chromium launches, a window is shown and the user is
  logged into their google account

  Current result: the executable seemingly hangs, no window is shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1763829/+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 1763829] Re: [snap] chromium won't start after logging in to google account

[Olivier Tilloy]

Thanks for testing!

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [snap] chromium won't start after logging in to google account

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  (issue initially reported on the forum: https://forum.snapcraft.io/t
  /call-for-testing-chromium-65-0-3325-146/4390/20)

  $ snap info core chromium | egrep "name|installed"
  name:  core
  installed:   16-2.32.3(4407) 90MB core
  name:  chromium
  installed:   65.0.3325.181 (274)  144MB -

  Steps to reproduce:
  1) Install the chromium snap: snap install chromium
  2) Launch it: /snap/bin/chromium
  3) Click the account button on the right side of the tabs bar, and log into a 
google account
  4) Close the browser window
  5) Launch chromium again

  Expected result: chromium launches, a window is shown and the user is
  logged into their google account

  Current result: the executable seemingly hangs, no window is shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1763829/+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 1764773] Re: gnome-control-center crashed with SIGSEGV in __GI_____strtoul_l_internal()

[Apport retracing service]

*** This bug is a duplicate of bug 1712961 ***
https://bugs.launchpad.net/bugs/1712961

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 #1712961, 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/1764773/+attachment/5119566/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1764773

Title:
  gnome-control-center crashed with SIGSEGV in
  __GI_strtoul_l_internal()

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
   ¯\_(ツ)_/¯

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Apr 17 11:37:42 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-07-26 (264 days ago)
  InstallationMedia:
   
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7f233eb0bd60 <__GI___strtoul_l+32>:  movsbq 
(%rdi),%rax
   PC (0x7f233eb0bd60) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI_strtoul_l_internal (loc=0x7f233eeb0960 <_nl_C_locobj>, group=0, 
base=10, endptr=0x7ffd0da0f718, nptr=0x0) at ../stdlib/strtol_l.c:292
   __GI___strtoul_l (nptr=0x0, endptr=0x7ffd0da0f718, base=10, 
loc=0x7f233eeb0960 <_nl_C_locobj>) at ../stdlib/strtol_l.c:547
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: gnome-control-center crashed with SIGSEGV in 
__GI_strtoul_l_internal()
  UpgradeStatus: Upgraded to bionic on 2018-04-16 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1764773/+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 1764764] Re: Xorg crashed with SIGSEGV in miPointerSetPosition()

[Apport retracing service]

*** This bug is a duplicate of bug 1681084 ***
https://bugs.launchpad.net/bugs/1681084

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 #1681084, 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/1764764/+attachment/5119484/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1764764

Title:
  Xorg crashed with SIGSEGV in miPointerSetPosition()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg crashed and restarted, closed all windows and go back to login
  screen.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 11:20:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:070a]
 Subsystem: Dell GM108M [GeForce 930M] [1028:070a]
  InstallationDate: Installed on 2018-04-04 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  MachineType: Dell Inc. Inspiron 5457
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f059e730-2a5b-4da6-8a15-87df93d2a749 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x56180497eecc:cmp0x10(%rax),%ecx
   PC (0x56180497eecc) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   miPointerSetPosition ()
   ?? ()
   ?? ()
   GetPointerEvents ()
  Title: Xorg crashed with SIGSEGV in miPointerSetPosition()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.9
  dmi.board.name: 0WT51R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.9:bd04/25/2016:svnDellInc.:pnInspiron5457:pvr:rvnDellInc.:rn0WT51R:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5457
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: 

[Desktop-packages] [Bug 1764767] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

*** This bug is a duplicate of bug 1679903 ***
https://bugs.launchpad.net/bugs/1679903

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 #1679903, 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/1764767/+attachment/5119539/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1764767

Title:
  gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  don t know, happened after restart.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-keyring 3.28.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Apr 17 16:30:36 2018
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  InstallationDate: Installed on 2018-03-05 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-keyring
  StacktraceTop:
   g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-keyring-daemon 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-keyring/+bug/1764767/+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