[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

2018-11-22 Thread Daniel van Vugt
** Tags removed: artful
** Tags added: bionic cosmic disco

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Cosmic:
  Triaged

Bug description:
  Monitor is set to 144hz, but on Wayland it visually fails to go above
  60Hz. I have confirmed the monitor is running at 144Hz during the
  Wayland session, and that is also the setting in the Settings control
  panel.

  Using the additional NVidia drivers installed using the Ubuntu
  software control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1763892/+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 1804465] Re: Nautilus crashed with SIGSEGV in g_type_check_instance_cast when searching on Dingo

2018-11-22 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1804260 ***
https://bugs.launchpad.net/bugs/1804260

Thank you for your bug report, that seems similar to bug #1804260. Btw
it's easier to send the report by clicking on the .crash from nautilus
or using the ubuntu-bug command than doing screenshots of it...

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => High

** This bug has been marked a duplicate of bug 1804260
   
/usr/bin/nautilus:11:g_type_check_instance_is_fundamentally_a:g_object_unref:nautilus_search_engine_finalize:g_object_unref:g_closure_invoke

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

Title:
  Nautilus crashed with SIGSEGV in g_type_check_instance_cast when
  searching on Dingo

Status in nautilus package in Ubuntu:
  New

Bug description:
  Hi, since a few days on Ubuntu 19.04 Dingo development version,
  Nautilus systematically crashes when I'm doing a research by file
  name.

  Error message: Nautilus crashed with SIGSEGV in
  g_type_check_instance_cast (see images joined)

  It happens when I enter a word on the search bar with the keyboard,
  never on first character, nor if I do a copy - paste with Ctrl C /
  Ctrl V ; but if I write the search item, it crashes, Nautilus closes.

  Package : Nautilus 3.26.4-0ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804465/+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 1804437] Re: Saving new password for VPN (IPSec) fails silently

2018-11-22 Thread Sebastien Bacher
Thanks

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

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=797392
   Importance: Unknown
   Status: Unknown

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

Title:
  Saving new password for VPN (IPSec) fails silently

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Ubuntu: 18.04
  Involved packages (non-exhaustive list): network-manager, vpnc

  Steps to reproduce:
  1) Open "Network Connections" dialog
  2) Add a non-existing entry for a working IPSec VPN connection, fill all 
required fields but enter a wrong password
  3) Save the entry
  4) Edit entry again, put in the correct password, make sure to fill all 
required fields
  5) Save the entry
  6) Open Edit view of the entry again to verify that the password has not been 
changed with last save action. 

  Expected behavior:
  Either password should be stored when modified and saved -OR- user should be 
notified that password could not be saved for whatever reason. 

  Work-around:
  Delete whole VPN entry and create a new one with the correct password entered 
from the beginning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1804437/+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 1804506] Re: nautilus-desktop crashed with SIGSEGV in queue_background_change()

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

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

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

Title:
  nautilus-desktop crashed with SIGSEGV in queue_background_change()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Crashes randomly!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 21 17:29:25 2018
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-12-14 (342 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: nautilus-desktop
  SegvAnalysis:
   Segfault happened at: 0x55a3f6053bbd:mov0x48(%rbx),%edi
   PC (0x55a3f6053bbd) ok
   source "0x48(%rbx)" (0x55a3004d) not located in a known VMA region 
(needed readable region)!
   destination "%edi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus-desktop crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (33 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  mtime.conffile..etc.apport.crashdb.conf: 2018-11-21T09:13:30.219492
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804506/+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 1804506] Re: nautilus-desktop crashed with SIGSEGV in queue_background_change()

2018-11-22 Thread Sebastien Bacher
** Information type changed from Private to Public

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

Title:
  nautilus-desktop crashed with SIGSEGV in queue_background_change()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Crashes randomly!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 21 17:29:25 2018
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-12-14 (342 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: nautilus-desktop
  SegvAnalysis:
   Segfault happened at: 0x55a3f6053bbd:mov0x48(%rbx),%edi
   PC (0x55a3f6053bbd) ok
   source "0x48(%rbx)" (0x55a3004d) not located in a known VMA region 
(needed readable region)!
   destination "%edi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus-desktop crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (33 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  mtime.conffile..etc.apport.crashdb.conf: 2018-11-21T09:13:30.219492
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804506/+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 1804765] Re: /usr/bin/nautilus-desktop:11:queue_background_change:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit_by_name

2018-11-22 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1804506 ***
https://bugs.launchpad.net/bugs/1804506

** This bug has been marked a duplicate of bug 1804506
   nautilus-desktop crashed with SIGSEGV in queue_background_change()

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

Title:
  /usr/bin/nautilus-
  
desktop:11:queue_background_change:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit_by_name

Status in nautilus package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804765/+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 1804506] Re: nautilus-desktop crashed with SIGSEGV in queue_background_change()

2018-11-22 Thread Sebastien Bacher
Thank you for your bug report. Do you have any idea what you are doing to 
trigger the issue?
There are a bug on reports on the error tracker about that
https://errors.ubuntu.com/problem/85bc1f0a0712ba9b943f1d4adbf05b41c58872f0

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

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

Title:
  nautilus-desktop crashed with SIGSEGV in queue_background_change()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Crashes randomly!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 21 17:29:25 2018
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-12-14 (342 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: nautilus-desktop
  SegvAnalysis:
   Segfault happened at: 0x55a3f6053bbd:mov0x48(%rbx),%edi
   PC (0x55a3f6053bbd) ok
   source "0x48(%rbx)" (0x55a3004d) not located in a known VMA region 
(needed readable region)!
   destination "%edi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus-desktop crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (33 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  mtime.conffile..etc.apport.crashdb.conf: 2018-11-21T09:13:30.219492
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804506/+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 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

2018-11-22 Thread Daniel van Vugt
Here's the final missing piece:
https://salsa.debian.org/gnome-team/mutter/merge_requests/20

** Changed in: mutter (Ubuntu Cosmic)
   Status: In Progress => Triaged

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Cosmic:
  Triaged

Bug description:
  Monitor is set to 144hz, but on Wayland it visually fails to go above
  60Hz. I have confirmed the monitor is running at 144Hz during the
  Wayland session, and that is also the setting in the Settings control
  panel.

  Using the additional NVidia drivers installed using the Ubuntu
  software control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1763892/+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 1799562] Re: Options in the "Move to" and "copy to" context menu

2018-11-22 Thread Sebastien Bacher
Is your userdir or desktop dir on a special location? There is a similar report 
upstream from non Ubuntu on https://bugzilla.gnome.org/show_bug.cgi?id=770836
Do you have any error in journalctl when you get the issue?

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

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

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

Title:
  Options in the "Move to" and "copy to" context menu

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  New

Bug description:
  When you right-click the folders on the desktop to "copy to" or "move to," 
the following dialog box opens: "Could not open folder contents"
    "The specified location is not supported"

  After, Clicking OK on the message opens everything normally. I searched the 
error but could not get more details.
  Attached image of the error message.

  https://imgur.com/a/hNcgxo1

  Follow Machine Configuration

  https://imgur.com/a/QnUMChT

  I thank you for your help

  
  *

  Opçoes contidas no menu de contexto "Mover para"  e "copiar para "

  Ao clicar com com o botão direito do mouse nas pastas da área de trabalho 
para "copiar para" ou "mover para" , abre a seguinte mensagem de diálogo: "Não 
foi possível abrir o conteúdo da pasta"
   "Não há suporte à localização especificada"

  Após, Clicando em OK na mensagem abre tudo normalmente. Pesquisei sobre o 
erro mas não consegui maiores detalhes. 
  Em anexo imagem da mensagem de erro.

  https://imgur.com/a/hNcgxo1

  Segue especificações da Configuração da Máquina

  https://imgur.com/a/QnUMChT

  Desde já agradeço pela ajuda

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1799562/+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 1804765] [NEW] /usr/bin/nautilus-desktop:11:queue_background_change:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit_by_name

2018-11-22 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1804506 ***
https://bugs.launchpad.net/bugs/1804506

Public bug reported:

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

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


** Tags: artful bionic cosmic kylin-17.10

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

Title:
  /usr/bin/nautilus-
  
desktop:11:queue_background_change:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit_by_name

Status in nautilus package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804765/+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 1561278] Re: internal sound card not detected HP X2

2018-11-22 Thread Sebastien Bacher
@Simon, see comment #34?

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1804710] Re: apport hook depends on Python 2

2018-11-22 Thread Sebastien Bacher
That doesn't have to do with the screenshoter, reassigning

** Package changed: gnome-screenshot (Ubuntu) => gnome-screensaver
(Ubuntu)

** Changed in: gnome-screensaver (Ubuntu)
   Importance: Undecided => Critical

** Changed in: gnome-screensaver (Ubuntu)
   Importance: Critical => Low

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

Title:
  apport hook depends on Python 2

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Even once bug 1804709 is addressed and the hook can run at all, it
  still won't work on default Ubuntu installations (which don't have
  Python 2) because the shebang points at /usr/bin/python.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1804710/+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 1804709] Re: Shipped apport hook contains diff lines

2018-11-22 Thread Sebastien Bacher
Thank you for your bug report, screensaver != screenshot, I'm
reassigning to the right component.

That was reported before and fixed in Debian, it now needs to be merged to 
Ubuntu
https://salsa.debian.org/gnome-team/gnome-screensaver/commit/792b8063

** Package changed: gnome-screenshot (Ubuntu) => gnome-screensaver
(Ubuntu)

** Changed in: gnome-screensaver (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-screensaver (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Shipped apport hook contains diff lines

Status in gnome-screensaver package in Ubuntu:
  Fix Committed

Bug description:
  As you can see here:

  ```
  $ head -n3 /usr/share/apport/package-hooks/source_gnome-screensaver.py

  ubuntu/devel  [ 17:38:44 ]
  +#!/usr/bin/python
  +
  '''Apport package hook for gnome-screensaver
  ```

  This means that I can't report bugs (including this one!) using
  ubuntu-bug, because I get this:

  ```
  ERROR: hook /usr/share/apport/package-hooks/source_gnome-screensaver.py 
crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  exec(compile(fd.read(), hook, 'exec'), symb)
File "/usr/share/apport/package-hooks/source_gnome-screensaver.py", line 1
  +#!/usr/bin/python
   ^
  SyntaxError: invalid syntax
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1804709/+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 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

2018-11-22 Thread Daniel van Vugt
Actually if anyone wants a live 18.04 image with the fix built-in, this
might/should work:

http://cdimages.ubuntu.com/bionic/daily-live/current/bionic-desktop-
amd64.iso

** Tags removed: artful

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Released
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [ Impact ]

  In some early intel GPUs gdm can't start in wayland mode, and so
  gnome-shell

  [ Test case ]

  - Start the pc or logout/end session
  - Try to login with the "Ubuntu on Wayland" session
  - Ubuntu should start

  [ Regression potential ]

  Possible false positive on wayland support check on some cards

  
  ---

  
  https://gitlab.gnome.org/GNOME/mutter/issues/127

  ---

  Wayland sessions (including the login screen itself) don't start up on
  older Intel GPUs.

  ---

  Workaround:

  Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false

  ---

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+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 1803271] Re: [regression] Much higher CPU during some gnome-shell operations

2018-11-22 Thread Daniel van Vugt
** Changed in: gjs (Ubuntu Cosmic)
   Status: New => In Progress

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

** Changed in: gjs (Ubuntu Cosmic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

** Changed in: gjs (Ubuntu Bionic)
   Status: Confirmed => Triaged

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

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

Title:
  [regression] Much higher CPU during some gnome-shell operations

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Bionic:
  Triaged
Status in gjs source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  Since fixing bug 1672297 in release 18.04 we experience much higher
  (almost double) CPU usage during gnome-shell JavaScript operations,
  such as the icon spring animation.

  [Test Case]

  Use 'top' to measure the CPU usage of the gnome-shell process while
  tapping Super+A repeatedly. It should be much lower with the fix than
  without.

  [Regression Potential]

  Low. This particular fix is tiny
  (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been
  released and used in a couple of upstream gjs versions already without
  issue.

  [Other Info]

  The fix is already released to 19.04 as part of gjs version 1.54.2-1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+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 1803271] Re: [regression] Much higher CPU during some gnome-shell operations

2018-11-22 Thread Chris Halse Rogers
** Also affects: gjs (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gjs (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  [regression] Much higher CPU during some gnome-shell operations

Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Bionic:
  Triaged
Status in gjs source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  Since fixing bug 1672297 in release 18.04 we experience much higher
  (almost double) CPU usage during gnome-shell JavaScript operations,
  such as the icon spring animation.

  [Test Case]

  Use 'top' to measure the CPU usage of the gnome-shell process while
  tapping Super+A repeatedly. It should be much lower with the fix than
  without.

  [Regression Potential]

  Low. This particular fix is tiny
  (https://gitlab.gnome.org/GNOME/gjs/merge_requests/236) and has been
  released and used in a couple of upstream gjs versions already without
  issue.

  [Other Info]

  The fix is already released to 19.04 as part of gjs version 1.54.2-1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1803271/+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 367473] Re: Segfault when trying to add a Windows printer via SAMBA

2018-11-22 Thread Launchpad Bug Tracker
[Expired for system-config-printer (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: system-config-printer (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Segfault when trying to add a Windows printer via SAMBA

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

Bug description:
  In Ubuntu 9.04, I'm trying to add a Windows printer via SAMBA. I click
  Browse..., find the domain/workgroup, click the triangle to expand it,
  then I click the triangle beside the Windows PC I want. The entire
  "Printer configuration" and all related windows close completely, and
  dmesg reports

  [44291.812374] ppdev0: registered pardevice
  [44291.860041] ppdev0: unregistered pardevice
  [44293.282644] ppdev0: registered pardevice
  [44293.328523] ppdev0: unregistered pardevice
  [44293.744350] ppdev0: registered pardevice
  [44293.792336] ppdev0: unregistered pardevice
  [44343.815645] python[4]: segfault at b4b24290 ip b4b24290 sp bf86a7c8 
error 4 in lowcase.dat.samba3[b4b34000+2]

  I added a network printer just fine, but adding a Windows printer via
  Samba fails. On other Ubuntu computers, rebooting would let me add the
  Windows printer, but this computer consistently fails.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/yelp
  NonfreeKernelModules: nvidia
  Package: yelp 2.25.1-0ubuntu5
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/367473/+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 283895] Re: system-config-printer needs awareness of ~/.cups/lpoptions (as of 8.04)

2018-11-22 Thread Launchpad Bug Tracker
[Expired for system-config-printer (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: system-config-printer (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  system-config-printer needs awareness of ~/.cups/lpoptions (as of
  8.04)

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

Bug description:
  Binary package hint: system-config-printer

  As of the version shipped with Ubuntu 8.04, system-config-printer
  (System->Administration->Printing) does not check for, and is not
  aware of, "personal" ~/.cups/lpoptions files.  With system-config-
  printer oblivious, the UI does not accurately reflect reality.

  Specifically:  A user may have created a ~/.cups/lpoptions file by
  using lpoptions -d or other mechanisms.  As system-config-printer
  exists today, the personal lpoptions file will silently override any
  settings, such as default printer, made in the system-config-printer
  GUI.

  If ~/.cups/lpoptions exists, looking at both system-config-printer and
  the global CUPS configuration (localhost:631) will show the global
  setting with no hint that the current user has overridden the setting.

  Suggested resolution:  In the short term, add a test for
  ~/.cups/lpoptions, and if it exists show a warning such as "The file
  ~/.cups/lpoptions exists and may override any settings shown or made
  here."  Possibly with "Show contents" and "Remove this file?" options.

  In the long term, there seems to be some demand for both global and
  local options in the GUI per bug 127071.  That would require the GUI
  to be much smarter about local lpoptions, where exactly the settings
  are being stored, and which ones are effective/being shown at a
  particular time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/283895/+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 338291] Re: cannot set lpd printer with system-config-printer

2018-11-22 Thread Launchpad Bug Tracker
[Expired for system-config-printer (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: system-config-printer (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  cannot set lpd printer with system-config-printer

Status in gtk+2.0 package in Ubuntu:
  Incomplete
Status in pygtk package in Ubuntu:
  Incomplete
Status in system-config-printer package in Ubuntu:
  Expired

Bug description:
  Binary package hint: system-config-printer

  Im using Ubuntu Jaunty.

  I have a printer shared with some computers over ethernet using a
  d-link printserver.

  To install it on my computer I run system-config-printer, then new ->
  printer, after this i expand the Network Printer tree and click on
  LPD/LPR Host or printer. In the right side in "host" box i write the
  ip of the printserver (192.168.1.240) and in the other box i write the
  name of the printer I set in the printserver (LASER). Now I should
  click foward button but... i cannot because the Foward button isn't
  enabled! Did I make a mistake? If I have to do in other way in my
  opinion it should be explained better.

  P.S. the version of system-config-printer is
  1.1.3+git20090218-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/338291/+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 368306] Re: Can't configure virtual printer

2018-11-22 Thread Launchpad Bug Tracker
[Expired for system-config-printer (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: system-config-printer (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Can't configure virtual printer

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

Bug description:
  Binary package hint: system-config-printer

  system-config-printer doesn't let you create a virtual printer that isn't 
associated with a particular port.For example, a generic postscript or 
generic pdf printer that always prints to a file (i.e. actually trying to spool 
isn't possible). You can select LPT#1 and create a generic postscript 
printer, but there is no option to disassociate it from the parallel port.
  Under other, you can enter URI file://dev/null but you get CUPS server error 
"client-error-not-possible"

  There is no generic/PDF.

  With the newer gnome apps and firefox, you don't need this (too much)
  as postscript/pdf file printing is built into the print dialog but
  other applications still need it as you used a printer definition to
  select the format to print to file.   Open Office is an example
  (though it does have an export to PDF option that others may lack).

  Once you have created a printer (using LPT#1), you can't delete it:
  CUPS server error: client-error-not-found.   But once you have
  deleted, it doesn't show up to be chosen as a print destination but
  still shows up in printer configuration (until you exit and reload).
  And when you create another similarly named printer, it adds a "2" to
  the end.

  ProblemType: Bug
  Architecture: amd64
  CupsErrorLog: E [27/Apr/2009:18:32:38 -0400] CUPS-Add-Modify-Printer: 
Unauthorized
  DistroRelease: Ubuntu 9.04
  Lpstat: device for ML-1710: usb://Samsung/ML-1710
  MachineType:
   
  NonfreeKernelModules: nvidia
  Package: system-config-printer-gnome 1.1.3+git20090218-0ubuntu19
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: ML-1710: Samsung ML-1710, SpliX V. 2.0.0
  ProcCmdLine: root=UUID=a4fc983e-7fb5-4c68-9b5f-030750075a8b ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
  SourcePackage: system-config-printer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/368306/+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 1754864] Re: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04

2018-11-22 Thread Chris Halse Rogers
Marking as verification-done; the change that regressed has been
reverted, so this bug isn't actually fixed, but it also hasn't
introduced the downgrade problem.

** Tags added: verification-done

** Tags removed: verification-done
** Tags added: verification-done-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/1754864

Title:
  Flatpak related refs are not installed when using GNOME Software on
  Ubuntu 18.04

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Triaged

Bug description:
  When installing a Flatpak application that depends on some runtimes
  and they depend on some additional runtime extensions (related refs)
  using GNOME Software on Ubuntu 18.04, the runtime extensions are not
  installed. They are installed if you run "flatpak update" from
  Terminal after the installation. This issue should be already fixed in
  GNOME Software upstream so I believe that this is a downstream Ubuntu
  issue. Please, fix this.

  Steps to Reproduce:
  1. Use the latest, fully updated Ubuntu 18.04 image.
  2. Install "flatpak" and "gnome-software-plugin-flatpak" packages.
  3. Restart the system.
  4. Download and add the Flathub repo file: 
https://dl.flathub.org/repo/flathub.flatpakrepo
  5. Search and install the "GNOME Web" Flatpak package using GNOME Software.
  6. Run the installed "Web" application.

  Actual results:
  GNOME Web is started with the default (Adwaita) theme (and without the 
correct locale if you use non-English system).

  Expected results:
  GNOME Web is started with the correct (Ubuntu) theme (and with the correct 
locale if you use non-English system).

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

2018-11-22 Thread Beluga
Repro.

Arch Linux 64-bit
Version: 6.3.0.0.alpha0+
Build ID: 750ccfb2a60582a5652c08f3cbb6f11d4c152275
CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3_kde5; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 22 November 2018

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

Title:
  Assigns style to columns it cannot handle in .xlsx files

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1) Open LibreOffice Calc
  2) File > New > Spreadsheet
  3) File > Save As, choose name vanilla.xlsx > Save

  Extract contents of vanilla.xlsx file to some directory. In the 
xl/worksheets/sheet1.xml file in the node worksheet/cols/ you'll find node
  

  LibreOffice Calc can handle only 1024 columns, but style says it apply
  to 1025. If such .xlsx document is processed with PhpOffice and single
  cell value is written,  nodes gets expanded, including for . This column cannot be processed by
  LibreOffice Calc and produces warnings that some information is lost.

  Value should be at most 1024 (or whatever limit is in 6.1).

  File produced on my copy of libreoffice is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 18:08:43 2018
  InstallationDate: Installed on 2018-04-11 (180 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1796698/+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 1796698] Re: Assigns style to columns it cannot handle in .xlsx files

2018-11-22 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: New => Confirmed

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

Title:
  Assigns style to columns it cannot handle in .xlsx files

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1) Open LibreOffice Calc
  2) File > New > Spreadsheet
  3) File > Save As, choose name vanilla.xlsx > Save

  Extract contents of vanilla.xlsx file to some directory. In the 
xl/worksheets/sheet1.xml file in the node worksheet/cols/ you'll find node
  

  LibreOffice Calc can handle only 1024 columns, but style says it apply
  to 1025. If such .xlsx document is processed with PhpOffice and single
  cell value is written,  nodes gets expanded, including for . This column cannot be processed by
  LibreOffice Calc and produces warnings that some information is lost.

  Value should be at most 1024 (or whatever limit is in 6.1).

  File produced on my copy of libreoffice is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 18:08:43 2018
  InstallationDate: Installed on 2018-04-11 (180 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1796698/+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 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/

2018-11-22 Thread Adolfo Jayme
** Changed in: fontconfig (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  fontconfig initialization spends most of its time parsing XML
  configuration files in /etc/fonts/conf.d/

Status in Canonical System Image:
  In Progress
Status in fontconfig package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I 
noticed that a significant amount of time (around 35ms) was spent solely on 
parsing the XML configuration files in /etc/fonts/conf.d/ 
  There seems to be around 40 files on Ubuntu Phone in that directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590804/+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 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-22 Thread Peter Goodall
I've extended my search in journalctl. Hope this helps:

% journalctl -b | grep -E 'spice-vdagent|gnome-session'
Nov 23 13:55:56 [xxx] gnome-session[2237]: gnome-session-binary[2237]: WARNING: 
App 'org.gnome.Shell.desktop' exited with code 1
Nov 23 13:55:56 [xxx] gnome-session-binary[2237]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Nov 23 13:55:56 [xxx] gnome-session-binary[2237]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
Nov 23 13:55:58 [xxx] dbus-daemon[2626]: [session uid=121 pid=2626] Activating 
via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' 
requested by ':1.2' (uid=121 pid=2633 
comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
Nov 23 13:55:58 [xxx] at-spi-bus-launcher[2635]: dbus-daemon[2640]: Activating 
service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=121 pid=2633 
comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
Nov 23 13:56:01 [xxx] spice-vdagent[2794]: Cannot access vdagent virtio channel 
/dev/virtio-ports/com.redhat.spice.0
Nov 23 13:56:02 [xxx] gnome-session[2632]: gnome-session-binary[2632]: WARNING: 
App 'spice-vdagent.desktop' exited with code 1
Nov 23 13:56:02 [xxx] gnome-session-binary[2632]: WARNING: App 
'spice-vdagent.desktop' exited with code 1
Nov 23 13:56:02 [xxx] gnome-session-binary[2632]: Entering running state
Nov 23 13:56:09 [xxx] dbus-daemon[2929]: [session uid=1000 pid=2929] Activating 
via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' 
requested by ':1.6' (uid=1000 pid=3013 
comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
Nov 23 13:56:09 [xxx] at-spi-bus-launcher[3014]: dbus-daemon[3019]: Activating 
service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=3013 
comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
Nov 23 13:56:12 [xxx] spice-vdagent[3193]: Cannot access vdagent virtio channel 
/dev/virtio-ports/com.redhat.spice.0
Nov 23 13:56:13 [xxx] gnome-session[2935]: gnome-session-binary[2935]: WARNING: 
App 'spice-vdagent.desktop' exited with code 1
Nov 23 13:56:13 [xxx] gnome-session-binary[2935]: WARNING: App 
'spice-vdagent.desktop' exited with code 1
Nov 23 13:56:13 [xxx] gnome-session-binary[2935]: Entering running state
Nov 23 13:56:15 [xxx] gnome-session[2935]: gnome-session-binary[2935]: WARNING: 
Application 'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 11
Nov 23 13:56:15 [xxx] gnome-session-binary[2935]: WARNING: Application 
'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 11
Nov 23 14:34:52 [xxx] gnome-session-c[9688]: Theme parsing error: 
gtk.css:9707:17: negative values are not allowed.

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

Title:
  spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

  oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent
  virtio channel /dev/virtio-ports/com.redhat.spice.0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: spice-vdagent 0.17.0-1ubuntu2
  Uname: Linux 4.19.0-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 14:34:00 2018
  InstallationDate: Installed on 2017-10-13 (378 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-22 Thread craig jackson
Hi Pawel,

You may be right, but I think the common thread in all the laptops
exhibiting this problem is the ALC294. Does the power save trick
mentioned in my comment work for you at all?

Cheers,
Craig

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Talib Pierson
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

You instructed me to make any further comments on the other report, but
I think that it is possible that bug 1804718 is not a duplicate because
I cannot open the applications; it only plays the animation. I may be
wrong, but I'll post more screenshots so you can see. It's possible my
memory is a little off, because a lot of other unrelated issues have
occurred so I think the images are most accurate.

** Attachment added: "Screenshot from 2018-11-22 10-40-25.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+attachment/5215497/+files/Screenshot%20from%202018-11-22%2010-40-25.png

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1804742] [NEW] package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned e

2018-11-22 Thread NongGuangXin
Public bug reported:

dpkg: dependency problems prevent configuration of gnome-shell:
 gnome-shell depends on gnome-shell-common (= 3.28.3-0ubuntu0.18.04.3); however:
  Package gnome-shell-common is not configured yet.

dpkg: error processing package gnome-shell (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup 
error from a previous failure.

  Setting up libpython3.6-dev:amd64 (3.6.7-1~18.04) ...
Setting up libsmbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.4) ...
Setting up libisccfg160:amd64 (1:9.11.3+dfsg-1ubuntu1.3) ...
Setting up gir1.2-mutter-2:amd64 (3.28.3-2~ubuntu18.04.2) ...
dpkg: dependency problems prevent configuration of update-manager:
 update-manager depends on policykit-1-gnome | polkit-kde-agent-1 | lxpolkit | 
lxqt-policykit | mate-polkit | polkit-1-auth-agent; however:
  Package policykit-1-gnome is not installed.
  Package polkit-kde-agent-1 is not installed.
  Package lxpolkit is not installed.
  Package lxqt-policykit is not installed.
  Package mate-polkit is not installed.
  Package polkit-1-auth-agent is not installed.
  Package gnome-shell which provides polkit-1-auth-agent is not configured yet.

dpkg: error processing package update-manager (--configure):
 dependency problems - leaving unconfigured
Setting up python3-gdbm:amd64 (3.6.7-1~18.04) ...
No apport report written because the error message indicates its a followup 
error from a previous failure.

  Setting up packagekit-tools (1.1.9-1ubuntu2.18.04.4) 
...

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-shell-common 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Nov 23 10:56:40 2018
DisplayManager: gdm3
ErrorMessage: installed gnome-shell-common package post-installation script 
subprocess returned error exit status 2
GsettingsChanges:
 
InstallationDate: Installed on 2018-08-21 (93 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python3.6, Python 3.6.7, unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: gnome-shell
Title: package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to 
install/upgrade: installed gnome-shell-common package post-installation script 
subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to
  install/upgrade: installed gnome-shell-common package post-
  installation script subprocess returned error exit status 2

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  dpkg: dependency problems prevent configuration of gnome-shell:
   gnome-shell depends on gnome-shell-common (= 3.28.3-0ubuntu0.18.04.3); 
however:
Package gnome-shell-common is not configured yet.

  dpkg: error processing package gnome-shell (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Setting up libpython3.6-dev:amd64 (3.6.7-1~18.04) 
...
  Setting up libsmbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.4) ...
  Setting up libisccfg160:amd64 (1:9.11.3+dfsg-1ubuntu1.3) ...
  Setting up gir1.2-mutter-2:amd64 (3.28.3-2~ubuntu18.04.2) ...
  dpkg: dependency problems prevent configuration of update-manager:
   update-manager depends on policykit-1-gnome | polkit-kde-agent-1 | lxpolkit 
| lxqt-policykit | mate-polkit | polkit-1-auth-agent; however:
Package policykit-1-gnome is not installed.
Package polkit-kde-agent-1 is not installed.
Package lxpolkit is not installed.
Package lxqt-policykit is not installed.
Package mate-polkit is not installed.
Package polkit-1-auth-agent is not installed.
Package gnome-shell which provides polkit-1-auth-agent is not configured 
yet.

  dpkg: error processing package update-manager (--configure):
   dependency problems - leaving unconfigured
  Setting up python3-gdbm:amd64 (3.6.7-1~18.04) ...
  No apport report written because the error 

[Desktop-packages] [Bug 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

It sounds like you might have multiple bugs, but for the moment let's
wait till bug 1769383 is fixed and then retest.

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

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


** This bug has been marked a duplicate of bug 1769383
   Ubuntu dock/launcher is shown on the lock screen

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

2018-11-22 Thread Daniel van Vugt
Please stop running apport now.

Next, please try both Gnome Shell sessions: "Ubuntu" and "Ubuntu on
Wayland".

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

Title:
  HID inputs (mouse buttons and keyboard) stop responding when plug in
  DP monitor

Status in ubuntu-mate:
  New
Status in mate-common package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.

  Device Lenovo T460s. Ubuntu-Mate 18.10.

  Plugging in External monitor using mini-display port causes keyboard
  to be unresponsive. Mouse buttons as well. though can still move mouse
  on screen. Plugging in and out using arndr sometimes resolves this.
  Notwithstanding, no smooth transition to multi-monitor mode.

  
  EDIT: 2018-11-22 // The problems are not observed when using HDMI instead of 
mini display-port. Moreover, if one can regain control of HID devices when mini 
DP plugged in, the resolution of the monitor plugged in is completely wrong. 

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins:
   (gconftool-2:31954): GConf-WARNING **: 21:41:20.841: Client failed to 
connect to the D-BUS daemon:
   Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: 2018-10-17 21:42:48,989 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
  InstallationDate: Installed on 2016-07-23 (848 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmDisplayLog:
   (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
  MachineType: LENOVO 20F9004FUS
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=074ff7b7-c074-4137-8cf7-d46cdd7dd723 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic ubuntu
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (32 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9004FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20F9004FUS:pvrThinkPadT460s:rvnLENOVO:rn20F9004FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20F9004FUS
  dmi.product.sku: LENOVO_MT_20F9_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: 2018-10-17 21:42:48,989 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-10-generic, x86_64: installed
   acpi-call, 1.1.0, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   wireguard, 0.0.20181119, 4.18.0-11-generic, x86_64: installed
  

[Desktop-packages] [Bug 1804008] Re: Gnome Shell extensions crash

2018-11-22 Thread Daniel van Vugt
bananenkasper, please log your own bug so as to not confuse the
debugging process here.

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

Title:
  Gnome Shell extensions crash

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  All my gnome-shell extensions randomly (apparently) crash. This
  behavior began when i upgraded to cosmic.

  Here's a excerpt of my logs:

  Nov 19 12:57:28 falcon gnome-shell[1640]: Object Meta.WindowActor 
(0x55669ffd87a0), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #1   5566ae293bb8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #3   5566ae293b00 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #5   5566ae293a80 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #7   5566ae293a00 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #9   5566ae293978 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7fc9f03c2dc0 @ 82)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #11   5566ae2938e0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7fc9f03cf1f0 @ 116)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #13   5566ae293860 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7fc9f03cf5e0 @ 37)
  Nov 19 12:57:28 falcon org.gnome.Shell.desktop[1640]: #15   5566ae2937e0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7fc9f03c2550 @ 12)
  Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618328'
  Nov 19 12:57:31 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618329'
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #1   5566b0c47bf0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #3   5566b0c47b38 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 
(7fc9f03d7790 @ 172)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #5   5566b0c47ab8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 
(7fc9f03d78b0 @ 17)
  Nov 19 12:57:31 falcon gnome-shell[1640]: Object Meta.WindowActor 
(0x55669ffd87a0), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #7   5566b0c47a38 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 
(7fc9f03d2f70 @ 42)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #9   5566b0c479b0 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 
(7fc9f03c2dc0 @ 82)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #11   5566b0c47918 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 
(7fc9f03cf1f0 @ 116)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #13   5566b0c47898 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 
(7fc9f03cf5e0 @ 37)
  Nov 19 12:57:31 falcon org.gnome.Shell.desktop[1640]: #15   5566b0c47818 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 
(7fc9f03c2550 @ 12)
  Nov 19 13:50:35 falcon dbus-daemon[815]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.16238' (uid=1000 pid=1640 comm="/usr/bin/gnome-shell " label="unconfined")
  Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618328'
  Nov 19 13:50:35 falcon gnome-shell[1640]: ../../../../gobject/gsignal.c:2641: 
instance '0x55669ee22c00' has no handler with id '618329'
  Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #1   5566a7f84270 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 
(7fc9f03d7820 @ 20)
  Nov 19 13:50:35 falcon org.gnome.Shell.desktop[1640]: #3   5566a7f841b8 i   

[Desktop-packages] [Bug 1804713] Re: gnome-shell error when changing wallpaper using gsettings

2018-11-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1787822 ***
https://bugs.launchpad.net/bugs/1787822

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


** This bug has been marked a duplicate of bug 1787822
   gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already 
deallocated - impossible to access to it

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

Title:
  gnome-shell error when changing wallpaper using gsettings

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a script that changes my wallpaper on a regular basis. It sets
  the wallpaper using gsettings. Like this:

  file=/home/lincoln/Pictures/wallpaper/10-2.jpg
  gsettings set org.gnome.desktop.background picture-uri file://$file
  gsettings set org.gnome.desktop.screensaver picture-uri file://$file

  Every time this happens, I get an error in my system log.

  Nov 23 08:50:22 imrlincoln slideshow.desktop[2936]: 
/home/lincoln/Pictures/wallpaper/10-2.jpg
  Nov 23 08:50:23 imrlincoln gnome-shell[2678]: Object Meta.Background 
(0x55ad39916a20), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: == Stack trace 
for context 0x55ad28692320 ==
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #0 
0x55ad28b27a98 i   resource:///org/gnome/shell/ui/background.js:718 
(0x7f5aac60f450 @ 22)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #1 
0x55ad28b27a10 i   resource:///org/gnome/shell/ui/tweener.js:112 
(0x7f5ac01c8e68 @ 37)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #2 
0x7ffe30e1de60 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 
(0x7f5ac01d2b38 @ 54)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #3 
0x7ffe30e1dfb0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 
(0x7f5ac01d2bc0 @ 1626)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #4 
0x7ffe30e1e060 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 
(0x7f5ac01d2c48 @ 100)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #5 
0x7ffe30e1e0f0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 
(0x7f5ac01d2cd0 @ 10)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #6 
0x7ffe30e1e1e0 b   resource:///org/gnome/gjs/modules/signals.js:128 
(0x7f5ac01d2230 @ 386)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #7 
0x7ffe30e1e290 b   resource:///org/gnome/shell/ui/tweener.js:244 
(0x7f5ac01cf808 @ 159)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #8 
0x7ffe30e1e2f0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f5ac01b5de0 @ 71)
  Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #9 
0x7ffe30e1e390 b   resource:///org/gnome/shell/ui/tweener.js:219 
(0x7f5ac01cf780 @ 15)

  This does not seem to cause any actual issues, but since this happens
  every 5 minutes, it does cause my system log to get large.

  I tried to track down the actual code mentioned in the error, but it
  doesn't seem to exist anywhere on the filesystem.

  lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  apt-cache policy gnome-shell

  gnome-shell:
Installed: 3.28.3-0ubuntu0.18.04.3
Candidate: 3.28.3-0ubuntu0.18.04.3
Version table:
   *** 3.28.3-0ubuntu0.18.04.3 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu2 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 23 08:56:52 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-08 (198 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage 

[Desktop-packages] [Bug 1803743] Re: Sometimes the sound disappears

2018-11-22 Thread Daniel van Vugt
If you have crash files then please don't attach them to bugs. Instead
send them by running:

  ubuntu-bug *.crash

However, I suspect RHVoice is not a standard Ubuntu package so we are
unable to handle it here at all.

Next time the problem happens, please run this command immediately after
the sound disappears:

  journalctl -b > justafter.txt

and attach the file 'justafter.txt' here.

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

Title:
  Sometimes the sound disappears

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Здравствуйте!
  С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук.  
Определить по какой причине так и не получилось. Если звук пропадает то 
помогает только перезагрузка. Обращался на форум, но безрезультатно 
https://forum.ubuntu.ru/index.php?topic=278602.0   Пару раз переустанавливал 
Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по 
инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. 
Первых два шага не помогают. Проблема остается и звук появляется только при 
перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю.  В 
третьем шаге предлагается специальный скрипт, который собирает всю необходимую 
информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей 
системе в момент когда звук отсутствует 
http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 
  Помогите, пожалуйста.

  
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  1288 F pulseaudio
   /dev/snd/controlC0:  a  1288 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: H61MLV2
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/02/2012:svnBIOSTARGroup:pnH61MLV2:pvr6.0:rvnBIOSTARGroup:rnH61MLV2:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
  dmi.product.family: None
  dmi.product.name: H61MLV2
  dmi.product.version: 6.0
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803743/+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 1725941] Re: hotCorner modification breaks official apps-menu extension

2018-11-22 Thread Daniel van Vugt
Denis,

Please propose your fix to the developers here:

  https://gitlab.gnome.org/GNOME/gnome-shell-extensions

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

** Changed in: gnome-shell-extensions (Ubuntu)
   Status: New => In Progress

** Changed in: gnome-shell-extensions (Ubuntu)
 Assignee: (unassigned) => Denis Gorodnichev (d-g)

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

Title:
  hotCorner modification breaks official apps-menu extension

Status in GNOME Shell:
  Expired
Status in gnome-shell-extensions package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 17.10 x64
  Activities Overview Hot Corner disabled using Gnome Tweaks

  When hot corners are disabled, the official Gnome Extension "Applications 
Menu"
   (https://extensions.gnome.org/extension/6/applications-menu/) is broken -- 
error shows when attempting to enable extensions and clicking menu does 
nothing. A small fix to the extension was suggested to the developer "Apps-menu 
crashes when there is no hotcorner"
   (https://bugzilla.gnome.org/show_bug.cgi?id=712625) but his response is that 
this problem does not fall in his court, at least while "dconf config option 
for disabling the activities hot corner" 
(https://bugzilla.gnome.org/show_bug.cgi?id=688320) is still open.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1725941/+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 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2018-11-22 Thread Daniel van Vugt
** Tags removed: artful
** Tags added: cosmic

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Unknown
Status in GNOME Shell:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+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 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

2018-11-22 Thread Daniel van Vugt
Yeah this bug started out as just being about Wayland so I don't feel
comfortable making this bug just about the Xorg case now.

There is a solution though. Just add the Wayland fix in:

  https://gitlab.gnome.org/GNOME/mutter/merge_requests/171

It may require some backporting to 3.30 as of recently, but I am happy
to do so.

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Cosmic:
  In Progress

Bug description:
  Monitor is set to 144hz, but on Wayland it visually fails to go above
  60Hz. I have confirmed the monitor is running at 144Hz during the
  Wayland session, and that is also the setting in the Settings control
  panel.

  Using the additional NVidia drivers installed using the Ubuntu
  software control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1763892/+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 1768169] Re: touchscreen doesn't work properly after stylus detection

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

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

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

Title:
  touchscreen doesn't work properly after stylus detection

Status in xinput package in Ubuntu:
  Confirmed

Bug description:
  I have a HP Pavilion x360 convertible 15 br0xx. This laptop has a
  multitouch touchscreen and an active pen/stylus.

  On ubuntu 16.04, the touchscreen used with fingers and the pen/stylus
  work properly. The touchscreen was identified as «ELAN0732:00
  04F3:24B8» as slave pointer and the pen as «ELAN0732:00 04F3:24B8 Pen»
  as slave pointer too.

  But, on ubuntu 18.04 bionic with gnome shell, the pen/stylus is
  identified «ELAN0732:00 04F3:24B8 Pen» as slave keyboard instead as
  slave pointer. Touchscreen work well until pen/stylus is used. At this
  point, a new device «ELAN0732:00 04F3:24B8 Pen Pen (0)» is enabled.
  The touchscreen stops working and the pen/styles works but with some
  issues.

  ~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer 
 (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=15   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN0732:00 04F3:24B8   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN0732:00 04F3:24B8 Pen Pen (0)   id=18   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master 
keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ HP Wide Vision HD Camera: HP Wi id=9[slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=16   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=17   [slave  
keyboard (3)]
  ↳ ELAN0732:00 04F3:24B8 Pen   id=11   [slave  
keyboard (3)]

  After disable devices id=11 and id=18, touchscreen recovers its multitouch 
feature.
  There is no combination enabling/disabling ids 10, 11 and 18, to get 
multitouch and pen working together.

  On Wayland session, I get the same behavior.

  Note: Ubuntu 18.04 LTS clean installation with «minimal install
  option» and no other customization.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1768169/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-22 Thread Pawel
Guys please keep this ticket for Zenbook S UX391UA nad ALC294.
UX533 is different issue. This not make sense. I've got 3 other Asus laptops, 
where sound worked perfectly on Linux.

Rebooting through Windows 10 or setting card in power_save does not work on 
UX391UA.
I bought external usb-c soundcard and now I am using it with headphones.

I think that without support from Realtek (for example Kailang Yang 
 
https://www.systutorials.com/linux-kernels/84502/alsa-hda-realtek-new-codecs-support-for-alc234-alc274-alc294-linux-4-4-12/),
 Kernel Alsa team, Canonical team or Asus there will be no changes.
I've tried to contact all of them but without any results.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Talib Pierson
** Attachment added: "Screenshot from 2018-11-21 14-53-35.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+attachment/5215430/+files/Screenshot%20from%202018-11-21%2014-53-35.png

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Talib Pierson
Oh, and the screen sometimes turns black as the background when I move
my cursor

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1733890] Re: Copy to clipboard not working

2018-11-22 Thread Jeff Martin
+1 to Roland's issue. Screenshot's are not pasting as expected. I had a
clipboard indicator extension for Gnome enabled. Thinking that this
might have some impact I disabled it, yet pasting images from the
clipboard does not work. Going to try and debug this one further.

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

Title:
  Copy to clipboard not working

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Grab the whole screen with delay
  2. Press copy to clipboard
  3. Try pasting into any application like GIMP or Chrome (e.g. Github issue 
thread) using Ctrl + v

  It's not pasting any image because it doesn't seem to be in clipboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 22 16:21:11 2017
  InstallationDate: Installed on 2017-11-12 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (2017)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1733890/+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 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Talib Pierson
** Attachment added: "Screenshot from 2018-11-07 07-23-10.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+attachment/5215427/+files/Screenshot%20from%202018-11-07%2007-23-10.png

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Talib Pierson
** Attachment added: "Screenshot from 2018-11-07 07-23-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+attachment/5215428/+files/Screenshot%20from%202018-11-07%2007-23-11.png

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1804718] [NEW] Lock screen does not appear when screen locks

2018-11-22 Thread Talib Pierson
Public bug reported:

When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
Description:Ubuntu 18.10
Release:18.10
ubuntu-session:
  Installed: 3.30.0-0ubuntu4
  Candidate: 3.30.0-0ubuntu4
  Version table:
 *** 3.30.0-0ubuntu4 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
100 /var/lib/dpkg/status
gnome-screensaver:
  Installed: 3.6.1-8ubuntu3
  Candidate: 3.6.1-8ubuntu3
  Version table:
 *** 3.6.1-8ubuntu3 500
500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
100 /var/lib/dpkg/status
I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
https://bugzilla.redhat.com/show_bug.cgi?id=713640
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-session 3.30.0-0ubuntu4
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 22 10:01:17 2018
InstallationDate: Installed on 2016-08-16 (827 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: gnome-session
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

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


** Tags: amd64 apport-bug cosmic third-party-packages

** Attachment added: "This attachment is my most recent screenshot. There are 
others I would like to send."
   
https://bugs.launchpad.net/bugs/1804718/+attachment/5215422/+files/Screenshot%20from%202018-11-22%2015-25-21.png

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4

[Desktop-packages] [Bug 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Talib Pierson
** Attachment added: "Screenshot from 2018-10-25 17-22-26.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+attachment/5215426/+files/Screenshot%20from%202018-10-25%2017-22-26.png

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1804718] Re: Lock screen does not appear when screen locks

2018-11-22 Thread Talib Pierson
** Attachment added: "Screenshot from 2018-11-21 14-53-35.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+attachment/5215429/+files/Screenshot%20from%202018-11-21%2014-53-35.png

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

Title:
  Lock screen does not appear when screen locks

Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I close the laptop lid, the screen locks, but when I start it up again, 
instead of prompting me to enter my password at the lock screen, I appear to be 
back in, even though I am not. The glitched session seems in between a vanilla 
gnome session and my Ubuntu session. I can try to open applications with the 
Ubuntu dock, but they will not open. The top bar doesn't have a log out or 
settings, more like vanilla gnome in Debian. Sometimes white pixels will appear 
at the top edge of the screen near this area. Sometimes the lock screen will 
appear, but not as usual. The Ubuntu dock appears even though I haven't entered 
my passcode yet. I should send screenshots. I wasn't always able to take 
successful screenshots, but I have some. I don't believe this to be much of a 
security issue, because I don't appear to be able to open any applications, 
although it does show what files I have on my desktop. I am using a system76 
laptop.
  Description:  Ubuntu 18.10
  Release:  18.10
  ubuntu-session:
Installed: 3.30.0-0ubuntu4
Candidate: 3.30.0-0ubuntu4
Version table:
   *** 3.30.0-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status
  gnome-screensaver:
Installed: 3.6.1-8ubuntu3
Candidate: 3.6.1-8ubuntu3
Version table:
   *** 3.6.1-8ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status
  I expected a lock screen to prompt me to enter my password. Instead, it was 
either missing, or it displayed along with the Ubuntu dock, which shouldn't 
display on top of the lock screen. I also appeared to be using a modified gnome 
session, even though ubuntu-session, but not gnome-session, is installed. I've 
reinstalled ubuntu-session and ubuntu-desktop already. I know for sure this is 
within the scope of ubuntu-desktop, because when I installed Kubuntu it stopped 
happening. When I uninstalled kubuntu and reinstalled Ubuntu, it started 
happening again. I've uninstalled some default packages, but noting 
ubuntu-session depends on, so I'm not sure what the problem is. 
gnome-power-manager is not installed, but I don't think it needs to be. It 
reminds me of the issues linked below:
  https://bugzilla.redhat.com/show_bug.cgi?id=713640
  
https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks#GNOME_Power_Manager
  
https://askubuntu.com/questions/453296/privacy-issue-when-waking-up-suspended-machine
  Except logging in does not seem to work properly, and will log me into what 
seems to be a gnome session, with all the application icons changed, and all 
that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-session 3.30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 10:01:17 2018
  InstallationDate: Installed on 2016-08-16 (827 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1804718/+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 1758653] Re: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied

2018-11-22 Thread Maarten Jacobs
Oddly enough, this problem started for me after I mounted a NFS volume
using autofs.

Not quite sure how that relates to samba - but it may mean something.

In response to David Spoelstra's comment. I meant to follow his
direction but accidentally installed samba-common (rather then samba-
common-bin).

Both packages appear to create /var/cache/samba, which resolves the
problem experienced by gvfsd.

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

Title:
  gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission
  denied

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission
  denied

  /var/cache/ has no 'samba' subdir nor file.

  oem@ubuntu:~$ ls -la /var/cache/
  total 80
  drwxr-xr-x 18 root root  4096 Feb 19 18:57 .
  drwxr-xr-x 14 root root  4096 Dec  1 20:15 ..
  drwxr-xr-x  2 root root  4096 Sep 15  2017 apparmor
  drwxr-xr-x  4 root root  4096 Dec  1 20:15 app-info
  drwxr-xr-x  3 root root  4096 Mar 25 14:11 apt
  drwxr-xr-x  3 root root  4096 Feb 19 18:00 apt-xapian-index
  drwxr-xr-x  2 root root  4096 Dec  1 20:15 cracklib
  drwxrwx---  3 root lp4096 Mar 25 07:35 cups
  drwxr-xr-x  2 root root  4096 Mar 23 04:41 debconf
  drwxr-xr-x  2 root root  4096 Dec  1 18:55 dictionaries-common
  drwxr-xr-x  2 root root 12288 Mar 19 04:28 fontconfig
  drwxr-xr-x  2 root root  4096 Oct  9 19:50 gdm
  drwx--  2 root root  4096 Mar 25 14:11 ldconfig
  drwxr-xr-x  2 root root  4096 Dec  1 19:13 localepurge
  drwxr-xr-x 13 man  man   4096 Mar 25 14:11 man
  -rw-r--r--  1 root root 0 Mar 25 08:24 motd-news
  drwxr-xr-x  3 root root  4096 Dec  1 19:57 PackageKit
  drwxr-xr-x  2 root root  4096 Mar 24 14:56 snapd
  drwxr-xr-x  2 root root  4096 Feb 20 04:57 ubuntu-advantage-tools

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 25 14:28:21 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1758653/+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 1804715] Re: package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-11-22 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  New

Bug description:
  Just tried running a simple apt update && upgrade and it failed to
  upgrade properly

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: desktop-file-utils 0.22-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Fri Nov 23 09:58:52 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1804715/+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 1804715] [NEW] package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-11-22 Thread Mihir Mone
Public bug reported:

Just tried running a simple apt update && upgrade and it failed to
upgrade properly

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: desktop-file-utils 0.22-1ubuntu5.1
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Fri Nov 23 09:58:52 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
SourcePackage: desktop-file-utils
Title: package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: desktop-file-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  New

Bug description:
  Just tried running a simple apt update && upgrade and it failed to
  upgrade properly

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: desktop-file-utils 0.22-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Fri Nov 23 09:58:52 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1804715/+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 1804713] [NEW] gnome-shell error when changing wallpaper using gsettings

2018-11-22 Thread a1291762
Public bug reported:

I have a script that changes my wallpaper on a regular basis. It sets
the wallpaper using gsettings. Like this:

file=/home/lincoln/Pictures/wallpaper/10-2.jpg
gsettings set org.gnome.desktop.background picture-uri file://$file
gsettings set org.gnome.desktop.screensaver picture-uri file://$file

Every time this happens, I get an error in my system log.

Nov 23 08:50:22 imrlincoln slideshow.desktop[2936]: 
/home/lincoln/Pictures/wallpaper/10-2.jpg
Nov 23 08:50:23 imrlincoln gnome-shell[2678]: Object Meta.Background 
(0x55ad39916a20), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: == Stack trace 
for context 0x55ad28692320 ==
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #0 0x55ad28b27a98 
i   resource:///org/gnome/shell/ui/background.js:718 (0x7f5aac60f450 @ 22)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #1 0x55ad28b27a10 
i   resource:///org/gnome/shell/ui/tweener.js:112 (0x7f5ac01c8e68 @ 37)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #2 0x7ffe30e1de60 
I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f5ac01d2b38 @ 
54)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #3 0x7ffe30e1dfb0 
b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f5ac01d2bc0 @ 
1626)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #4 0x7ffe30e1e060 
b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f5ac01d2c48 @ 
100)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #5 0x7ffe30e1e0f0 
b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f5ac01d2cd0 @ 
10)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #6 0x7ffe30e1e1e0 
b   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f5ac01d2230 @ 386)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #7 0x7ffe30e1e290 
b   resource:///org/gnome/shell/ui/tweener.js:244 (0x7f5ac01cf808 @ 159)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #8 0x7ffe30e1e2f0 
I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5ac01b5de0 @ 71)
Nov 23 08:50:23 imrlincoln org.gnome.Shell.desktop[2678]: #9 0x7ffe30e1e390 
b   resource:///org/gnome/shell/ui/tweener.js:219 (0x7f5ac01cf780 @ 15)

This does not seem to cause any actual issues, but since this happens
every 5 minutes, it does cause my system log to get large.

I tried to track down the actual code mentioned in the error, but it
doesn't seem to exist anywhere on the filesystem.

lsb_release -rd

Description:Ubuntu 18.04.1 LTS
Release:18.04

apt-cache policy gnome-shell

gnome-shell:
  Installed: 3.28.3-0ubuntu0.18.04.3
  Candidate: 3.28.3-0ubuntu0.18.04.3
  Version table:
 *** 3.28.3-0ubuntu0.18.04.3 500
500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.28.1-0ubuntu2 500
500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 23 08:56:52 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-05-08 (198 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-shell error when changing wallpaper using gsettings

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a script that changes my wallpaper on a regular basis. It sets
  the wallpaper using gsettings. Like this:

  file=/home/lincoln/Pictures/wallpaper/10-2.jpg
  gsettings set org.gnome.desktop.background picture-uri file://$file
  gsettings set org.gnome.desktop.screensaver picture-uri file://$file

  Every time this happens, I get an error in my system log.

  Nov 23 08:50:22 imrlincoln slideshow.desktop[2936]: 
/home/lincoln/Pictures/wallpaper/10-2.jpg
  Nov 23 08:50:23 imrlincoln gnome-shell[2678]: Object Meta.Background 
(0x55ad39916a20), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as 

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-22 Thread craig jackson
Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1742852

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1804710] [NEW] apport hook depends on Python 2

2018-11-22 Thread Dan Watkins
Public bug reported:

Even once bug 1804709 is addressed and the hook can run at all, it still
won't work on default Ubuntu installations (which don't have Python 2)
because the shebang points at /usr/bin/python.

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

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

Title:
  apport hook depends on Python 2

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Even once bug 1804709 is addressed and the hook can run at all, it
  still won't work on default Ubuntu installations (which don't have
  Python 2) because the shebang points at /usr/bin/python.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1804710/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

2018-11-22 Thread craig jackson
Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1784485, as I'm seeing the same symptoms, with the same
temporary improvement enabling the power save as described above.

Asus UX533 Kubuntu 18.10 (4.18.0-11-generic) fresh install (dual boot
with Windows 10).

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1804709] Re: Shipped apport hook contains diff lines

2018-11-22 Thread Adolfo Jayme
** Tags added: packaging

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

Title:
  Shipped apport hook contains diff lines

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  As you can see here:

  ```
  $ head -n3 /usr/share/apport/package-hooks/source_gnome-screensaver.py

  ubuntu/devel  [ 17:38:44 ]
  +#!/usr/bin/python
  +
  '''Apport package hook for gnome-screensaver
  ```

  This means that I can't report bugs (including this one!) using
  ubuntu-bug, because I get this:

  ```
  ERROR: hook /usr/share/apport/package-hooks/source_gnome-screensaver.py 
crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  exec(compile(fd.read(), hook, 'exec'), symb)
File "/usr/share/apport/package-hooks/source_gnome-screensaver.py", line 1
  +#!/usr/bin/python
   ^
  SyntaxError: invalid syntax
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1804709/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place

2018-11-22 Thread Adolfo Jayme
** Also affects: fonts-ubuntu (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream
  Vera Mono: Combining diacritics out of place

Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in fonts-droid package in Ubuntu:
  Won't Fix
Status in fonts-hack package in Ubuntu:
  New
Status in fonts-liberation package in Ubuntu:
  Confirmed
Status in fonts-noto package in Ubuntu:
  New
Status in fonts-tlwg package in Ubuntu:
  New
Status in fonts-ubuntu package in Ubuntu:
  New
Status in msttcorefonts package in Ubuntu:
  Won't Fix
Status in oxygen-fonts package in Ubuntu:
  New
Status in ttf-bitstream-vera package in Ubuntu:
  New

Bug description:
  In the Liberation Mono font, combining diacritical marks are drawn
  over the following character rather than the preceding.

  According to the Unicode standard since at least version 3.0, chapter
  3.6, verse D56, combining characters apply to the preceding base
  character. However, this font renders them on the following base
  character.

  Version info:
  Ubuntu Intrepid
  ttf-liberation 1.04~beta2-2

  To reproduce:
  1. Open gedit.
  2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small 
letter a, Combining acute accent, Latin small letter e).
  3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font.

  Expected:
  * Two grapheme clusters are displayed: Latin small letter a with acute 
accent, Latin small letter e.

  Observed:
  * The grapheme clusters displayed are: Latin small letter a, Latin small 
letter e with acute accent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 1561278] Re: internal sound card not detected HP X2

2018-11-22 Thread Simon Williams
Thanks for the tip, but I use the machine mainly at home and would find
internal speakers much more convenient. On a different thread, there's
talk of downloading UCM files to fix this (specifically UCM-
master/bytcr5645 and chtrt5645), but no details of where from. Perhaps
it's obvious to Ubuntu pros, but not to me. Any idea?

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1740599] Re: Selecting multiple files and dragging them to file manager is broken in a Wayland session

2018-11-22 Thread Ubfan
Ubuntu 18.04 Wayland, Select a desktop file icon and drag it to the
nautilus window.  When the icon touches the window, it jumps back to the
original starting point, the cursor remains a hand, and can no longer
move the icon, which is still highlighted.  No other icon may be
highlighlited, clicking on the backbround does not remove the
highlighting, and the cursor remains a hand over other applications like
firefox (but over nautilus or system things like launcher, screen
title,... it becomes an arrow). This comment box may be selected with
the hand, but the cursor clicks no longer reposition the insertion
point. Logging out fixes the problem. Closing nautilus does not.

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

Title:
  Selecting multiple files and dragging them to file manager is broken
  in a Wayland session

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  This issue is reproducible every time I try.

  - Start with two or more files on the desktop
  - Drag out a selection area around the files to select them
  - Open "Files" file manager
  - Drag and drop them to a folder

  The drag and drop operation fails and the cursor gets stuck as a hand
  icon.  Signing out is the only way I have tried to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-server0 1.14.0-1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 10:15:56 2017
  Dependencies:
   gcc-7-base 7.2.0-8ubuntu3
   libc6 2.26-0ubuntu2
   libffi6 3.2.1-6
   libgcc1 1:7.2.0-8ubuntu3
  DistUpgraded: 2017-11-09 17:38:14,971 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5926] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-10-11 (80 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=4c6cd516-44fe-441d-ad87-7a83e1593848 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: Upgraded to artful on 2017-11-09 (50 days ago)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 0PF86Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1740599/+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 1804709] [NEW] Shipped apport hook contains diff lines

2018-11-22 Thread Dan Watkins
Public bug reported:

As you can see here:

```
$ head -n3 /usr/share/apport/package-hooks/source_gnome-screensaver.py  

ubuntu/devel  [ 17:38:44 ]
+#!/usr/bin/python
+
'''Apport package hook for gnome-screensaver
```

This means that I can't report bugs (including this one!) using ubuntu-
bug, because I get this:

```
ERROR: hook /usr/share/apport/package-hooks/source_gnome-screensaver.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in _run_hook
exec(compile(fd.read(), hook, 'exec'), symb)
  File "/usr/share/apport/package-hooks/source_gnome-screensaver.py", line 1
+#!/usr/bin/python
 ^
SyntaxError: invalid syntax
```

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


** Tags: packaging

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

Title:
  Shipped apport hook contains diff lines

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  As you can see here:

  ```
  $ head -n3 /usr/share/apport/package-hooks/source_gnome-screensaver.py

  ubuntu/devel  [ 17:38:44 ]
  +#!/usr/bin/python
  +
  '''Apport package hook for gnome-screensaver
  ```

  This means that I can't report bugs (including this one!) using
  ubuntu-bug, because I get this:

  ```
  ERROR: hook /usr/share/apport/package-hooks/source_gnome-screensaver.py 
crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  exec(compile(fd.read(), hook, 'exec'), symb)
File "/usr/share/apport/package-hooks/source_gnome-screensaver.py", line 1
  +#!/usr/bin/python
   ^
  SyntaxError: invalid syntax
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1804709/+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 1804431] Re: Georgian Lari (currency) symbol is shown as rectangle

2018-11-22 Thread Adolfo Jayme
** Package changed: unicode (Ubuntu) => fonts-liberation (Ubuntu)

** Summary changed:

- Georgian Lari (currency) symbol is shown as rectangle 
+ No support for Georgian lari currency sign (U+20BE)

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

Title:
  No support for Georgian lari currency sign (U+20BE)

Status in fonts-liberation package in Ubuntu:
  New

Bug description:
  I think title describes it well.
  I have attached screenshot of current state

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1804431/+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 1804431] [NEW] Georgian Lari (currency) symbol is shown as rectangle

2018-11-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I think title describes it well.
I have attached screenshot of current state

** Affects: fonts-liberation (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: font georgian lari unicode
-- 
Georgian Lari (currency) symbol is shown as rectangle 
https://bugs.launchpad.net/bugs/1804431
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to fonts-liberation in Ubuntu.

-- 
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 1561278] Re: internal sound card not detected HP X2

2018-11-22 Thread Michael P
For what it's worth: An easy solution for audio is a bluetooth headset.
Works great under 18.04. I'd also like to get the main speakers working,
but I suspect the passengers next to me on the plane are happier with
the headset-only arrangement.

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1687436] Re: cupsd uses 100% CPU

2018-11-22 Thread Chrescht
For me nothing worked but to disable the cups-browsed service:
sudo systemctl disable cups-browsed

It disables the excessively active service to add any found network
printers(!)

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

Title:
  cupsd uses 100% CPU

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  cupsd constantly uses 100% of CPU (one core) when cups-browsed is
  running too. Network printer queues are autodetected and available.
  Printer listing is usually delayed by approx. 30s.

  lsb_release -rd:
  Description:  Ubuntu 17.04
  Release:  17.04

  apt-cache policy cups
  cups:
Installed: 2.2.2-1ubuntu1
Candidate: 2.2.2-1ubuntu1
Version table:
   *** 2.2.2-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy cups-browsed
  cups-browsed:
Installed: 1.13.4-1ubuntu1
Candidate: 1.13.4-1ubuntu1
Version table:
   *** 1.13.4-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1687436/+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 1804663] Re: audio of web is off

2018-11-22 Thread Sebastien Bacher
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  audio of web is off

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  i don't hear anything from web

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 22 15:11:04 2018
  DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 530] 
[174b:7162]
  InstallationDate: Installed on 2016-08-05 (838 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Packard Bell imedia S3840
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=562bbd01-6a42-4bcd-b109-080f909cc9ae ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-31 (82 days ago)
  dmi.bios.date: 07/08/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: imedia S3840
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr:
  dmi.product.family: Packard Bell Desktop
  dmi.product.name: imedia S3840
  dmi.product.version: P01-B1
  dmi.sys.vendor: Packard Bell
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Aug 31 16:50:45 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 Logitech Wheel Mouse MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1804663/+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 1804685] Re: icon view captions display in the wrong positions

2018-11-22 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

Title:
  icon view captions display in the wrong positions

Status in nautilus package in Ubuntu:
  New

Bug description:
  In the Preferences for Nautilus, under the Views tab, the user has the
  option to select information to appear in the "First", "Second", and
  "Third" position beneath icons.  However, in icon view,  whatever the
  user selects to appear in the "First" position will appear in the
  second location beneath the icon.  Whatever the user selects to appear
  in the "Second" position will appear in the third, or bottom,
  position.  Whatever the user selects to appear in the "Third" position
  will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS 
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804685/+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 1804693] Re: Copy problem with small files from shares mounted with libpam-mount

2018-11-22 Thread Sebastien Bacher
Thank you for your bug report. Could you give some details on how you
configure/use libpam-mount and what sort of mounts you are doing with
it? Can you copy files with cp or gvfs-copy without issue or do they
have the same bug?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

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

Title:
  Copy problem with small files from shares mounted with libpam-mount

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Dear all,

  With a fresh install of ubuntu 18.04.1 and libpam-mount, I encounter
  issue when I copy small text files of few octets from remote share to
  local host with nautilus.

  More exactly, when I paste the file from a mounted remote samba share
  to a local directory, nautilus reports a time of transfer of
  approximatively 596523 hours! The process keep locked and I need to
  killall nautilus to terminate the copy.

  It seems that nautilus is unable to "understand" the end of copy
  because the file is well copied from remote to local directory and is
  usable.

  Can you resolve this issue please ?

  Kind regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 20:01:59 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'235'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x548+992+52'"
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804693/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-22 Thread craig jackson
Interestingly, if I put the sound device into power save mode and wait a
few seconds before playing a sound, I can actually hear it perffectly
clearly, but after repeating the playing of the sound a few times, it
distorts then disappears:

  sudo -i
  echo 10 >/sys/module/snd_hda_intel/parameters/power_save
  sleep 10
  aplay /usr/share/sounds/alsa/Front_Center.wav

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1758994] Re: "There was an error playing video from the webcam"

2018-11-22 Thread Jehandan Jeyaseelan
Hi, I was wondering as to when the fix will be included in Ubuntu
18.04.1 LTS?

The fix has been out since July but users of Ubuntu 18.04 LTS haven't
received the updated packages with the fix yet. It is still 1.14.1 for
gst-plugins-good1.0.

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

Title:
  "There was an error playing video from the webcam"

Status in cheese package in Ubuntu:
  Confirmed
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released

Bug description:
  Chesee version: 3.28
  Ubuntu version: 18.04 (26.03.18 updated)

  when i open cheese, cheese shows "There was an error playing video
  from the webcam"

  Crashlog:
  UNPC:~$ cheese

  (cheese:2): Gtk-WARNING **: 21:07:11.856: Theme parsing error:
  cheese.css:7:35: The style property GtkScrollbar:min-slider-length is
  deprecated and shouldn't be used anymore. It will be removed in a
  future version

  (cheese:2): cheese-WARNING **: 21:07:12.958: Device '/dev/video0' failed 
during initialization: gstv4l2object.c(3695): gst_v4l2_object_set_format_full 
(): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1:
  Call to TRY_FMT failed for YUYV @ 1280x720: Input/output error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1758994/+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 1803849] Re: libgl1-mesa-dri:i386 can not be installed

2018-11-22 Thread Timo Aaltonen
I was able to install 'steam-latest.deb' from Valve on a chroot without
issues, and then ran 'steam' which installed all the i386 bits, again
without any issues.

If you have problems with the upgrade, try asking for help on a forum or
IRC. There's nothing to be fixed in the Ubuntu archive anyway, so
closing again.

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

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

Title:
  libgl1-mesa-dri:i386 can not be installed

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Steam client tries to install a set of i386 libraries. One of them is 
libgl1-mesa-dri:i386.
  But since upgrade to Ubuntu 18.10 this package got broken dependency and thus 
installation fails.

  >The following packages have unmet dependencies:
  > libgl1-mesa-dri:i386 : Depends: libllvm7:i386 (>= 1:7~svn298832-1~) but it 
is not going to be installed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgl1-mesa-dri:i386 (not installed)
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 18 09:54:04 2018
  DistUpgraded: 2018-10-19 13:34:56,068 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   exfat, 1.2.10, 4.18.0-11-generic, x86_64: installed
   exfat, 1.2.10, 4.18.0-12-generic, x86_64: installed
   exfat, 1.2.10, 4.19.1-041901-generic, x86_64: installed
   exfat, 1.2.10, 4.19.2-041902-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0804]
  InstallationDate: Installed on 2018-03-27 (235 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.2-041902-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (29 days ago)
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.product.sku: 0804
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803849/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V

2018-11-22 Thread adin
I have the same issue on Ubuntu 18.04.1 LTS (kernel 4.15.0-38-generic)
connected with DisplayLink (driver 4.4.24).  I'm connecting through
Display port on a Dell Inspiron 15, and a docker D6000.

The flicker occurs only on the laptop's monitor, and the external
monitors seem fine.  No flicker whatsoever.

As similar reports, when the docker is disconnected the flicker stops.

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

Title:
  [Dell XPS 13 9360] Mouse cursor flickers with one external monitor
  connected via HDMI+Wavlink WL-UG39DK1V

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  When I connect my laptop to my DisplayLink based device with USB (Wavlink 
universal USB 3.0 docking station https://www.wavlink.com/en/product/150 
WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the 
mouse icon flickers as per the following video:
  https://launchpadlibrarian.net/346625588/20171121_131417.mp4

  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  I've reported this to DisplayLink via:
  https://displaylink.org/forum/showthread.php?p=84713#post84713

  WORKAROUND: Use GNOME Flashback (Metacity) session.

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  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 Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

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

[Desktop-packages] [Bug 1804693] [NEW] Copy problem with small files from shares mounted with libpam-mount

2018-11-22 Thread Alexandre Neveux
Public bug reported:

Dear all,

With a fresh install of ubuntu 18.04.1 and libpam-mount, I encounter
issue when I copy small text files of few octets from remote share to
local host with nautilus.

More exactly, when I paste the file from a mounted remote samba share
to a local directory, nautilus reports a time of transfer of
approximatively 596523 hours! The process keep locked and I need to
killall nautilus to terminate the copy.

It seems that nautilus is unable to "understand" the end of copy
because the file is well copied from remote to local directory and is
usable.

Can you resolve this issue please ?

Kind regards.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.2
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 22 20:01:59 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'235'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x548+992+52'"
 b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
InstallationDate: Installed on 2018-11-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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

Title:
  Copy problem with small files from shares mounted with libpam-mount

Status in nautilus package in Ubuntu:
  New

Bug description:
  Dear all,

  With a fresh install of ubuntu 18.04.1 and libpam-mount, I encounter
  issue when I copy small text files of few octets from remote share to
  local host with nautilus.

  More exactly, when I paste the file from a mounted remote samba share
  to a local directory, nautilus reports a time of transfer of
  approximatively 596523 hours! The process keep locked and I need to
  killall nautilus to terminate the copy.

  It seems that nautilus is unable to "understand" the end of copy
  because the file is well copied from remote to local directory and is
  usable.

  Can you resolve this issue please ?

  Kind regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 20:01:59 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'235'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x548+992+52'"
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804693/+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 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-22 Thread Luís Louro
Same error on Ubuntu 18.04 4.15.0-39-generic
I can't use virtualization because the system reboots when using it. Also I 
have short time random black screen and random reboots.

final part of dmesg:

[9.163753] e1000e :00:1f.6 eno1: 10/100 speed: disabling TSO
[9.163802] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[   12.577491] PKCS#7 signature not signed with a trusted key
[   12.577523] vboxdrv: loading out-of-tree module taints kernel.
[   12.578400] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
[   12.602825] vboxdrv: Found 6 processor cores
[   12.624573] vboxdrv: TSC mode is Invariant, tentative frequency 3095999268 Hz
[   12.624575] vboxdrv: Successfully loaded version 5.2.10_Ubuntu (interface 
0x00290001)
[   12.637952] PKCS#7 signature not signed with a trusted key
[   12.638961] VBoxNetFlt: Successfully started.
[   12.651862] PKCS#7 signature not signed with a trusted key
[   12.652723] VBoxNetAdp: Successfully started.
[   12.666487] PKCS#7 signature not signed with a trusted key
[   12.667240] VBoxPciLinuxInit
[   12.672532] vboxpci: IOMMU not found (not registered)
[   31.920956] rfkill: input handler disabled

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

Title:
  spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

  oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent
  virtio channel /dev/virtio-ports/com.redhat.spice.0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: spice-vdagent 0.17.0-1ubuntu2
  Uname: Linux 4.19.0-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 14:34:00 2018
  InstallationDate: Installed on 2017-10-13 (378 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+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 1804688] Re: libreoffice always crashes when I do this

2018-11-22 Thread Bjlockie
The .crash

** Attachment added: "_usr_lib_libreoffice_program_soffice.bin.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1804688/+attachment/5215370/+files/_usr_lib_libreoffice_program_soffice.bin.1000.crash

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

Title:
  libreoffice always crashes when I do this

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I reported the crash using ubuntu-bug and I think it uploaded the .crash but 
then did nothing after.
  Maybe it didn't upload.
  I put it here:
  
http://lockie.ca/libreoffice/_usr_lib_libreoffice_program_soffice.bin.1000.crash

  The way to crash it is to open this file:
  http://lockie.ca/libreoffice/convertible_sofas
  1. select the columns E to G
  2. press control-c to copy them
  3. observe the crash

  If you create a new calc document and try to copy 2 empty columns, it
  freezes but doesn't crash.

  Version: 6.1.2.1
  Build ID: 1:6.1.2-0ubuntu1.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

  $ apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:6.1.2-0ubuntu1.1
Version table:
   1:6.1.2-0ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 
Packages
   1:6.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Thu Nov 22 13:10:52 2018
  InstallationDate: Installed on 2018-11-15 (7 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1804688/+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 1804688] Re: libreoffice always crashes when I do this

2018-11-22 Thread Bjlockie
The files were attached so look at the attachments.

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

Title:
  libreoffice always crashes when I do this

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I reported the crash using ubuntu-bug and I think it uploaded the .crash but 
then did nothing after.
  Maybe it didn't upload.
  I put it here:
  
http://lockie.ca/libreoffice/_usr_lib_libreoffice_program_soffice.bin.1000.crash

  The way to crash it is to open this file:
  http://lockie.ca/libreoffice/convertible_sofas
  1. select the columns E to G
  2. press control-c to copy them
  3. observe the crash

  If you create a new calc document and try to copy 2 empty columns, it
  freezes but doesn't crash.

  Version: 6.1.2.1
  Build ID: 1:6.1.2-0ubuntu1.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

  $ apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:6.1.2-0ubuntu1.1
Version table:
   1:6.1.2-0ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 
Packages
   1:6.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Thu Nov 22 13:10:52 2018
  InstallationDate: Installed on 2018-11-15 (7 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1804688/+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 1804688] Re: libreoffice always crashes when I do this

2018-11-22 Thread Bjlockie
The sample

** Attachment added: "convertible_sofas.ods"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1804688/+attachment/5215371/+files/convertible_sofas.ods

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

Title:
  libreoffice always crashes when I do this

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I reported the crash using ubuntu-bug and I think it uploaded the .crash but 
then did nothing after.
  Maybe it didn't upload.
  I put it here:
  
http://lockie.ca/libreoffice/_usr_lib_libreoffice_program_soffice.bin.1000.crash

  The way to crash it is to open this file:
  http://lockie.ca/libreoffice/convertible_sofas
  1. select the columns E to G
  2. press control-c to copy them
  3. observe the crash

  If you create a new calc document and try to copy 2 empty columns, it
  freezes but doesn't crash.

  Version: 6.1.2.1
  Build ID: 1:6.1.2-0ubuntu1.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

  $ apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:6.1.2-0ubuntu1.1
Version table:
   1:6.1.2-0ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 
Packages
   1:6.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Thu Nov 22 13:10:52 2018
  InstallationDate: Installed on 2018-11-15 (7 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1804688/+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 1804688] [NEW] libreoffice always crashes when I do this

2018-11-22 Thread Bjlockie
Public bug reported:

I reported the crash using ubuntu-bug and I think it uploaded the .crash but 
then did nothing after.
Maybe it didn't upload.
I put it here:
http://lockie.ca/libreoffice/_usr_lib_libreoffice_program_soffice.bin.1000.crash

The way to crash it is to open this file:
http://lockie.ca/libreoffice/convertible_sofas
1. select the columns E to G
2. press control-c to copy them
3. observe the crash

If you create a new calc document and try to copy 2 empty columns, it
freezes but doesn't crash.

Version: 6.1.2.1
Build ID: 1:6.1.2-0ubuntu1.1
CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
Locale: en-CA (en_CA.UTF-8); Calc: group threaded

$ apt-cache policy libreoffice
libreoffice:
  Installed: (none)
  Candidate: 1:6.1.2-0ubuntu1.1
  Version table:
 1:6.1.2-0ubuntu1.1 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 
Packages
 1:6.1.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Thu Nov 22 13:10:52 2018
InstallationDate: Installed on 2018-11-15 (7 days ago)
InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  libreoffice always crashes when I do this

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I reported the crash using ubuntu-bug and I think it uploaded the .crash but 
then did nothing after.
  Maybe it didn't upload.
  I put it here:
  
http://lockie.ca/libreoffice/_usr_lib_libreoffice_program_soffice.bin.1000.crash

  The way to crash it is to open this file:
  http://lockie.ca/libreoffice/convertible_sofas
  1. select the columns E to G
  2. press control-c to copy them
  3. observe the crash

  If you create a new calc document and try to copy 2 empty columns, it
  freezes but doesn't crash.

  Version: 6.1.2.1
  Build ID: 1:6.1.2-0ubuntu1.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

  $ apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:6.1.2-0ubuntu1.1
Version table:
   1:6.1.2-0ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 
Packages
   1:6.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Thu Nov 22 13:10:52 2018
  InstallationDate: Installed on 2018-11-15 (7 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1804688/+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 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

2018-11-22 Thread Jonathan Polak
** Description changed:

  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.
  
  Device Lenovo T460s. Ubuntu-Mate 18.10.
  
- Plugging in External monitor using mini-display port causes keyboard to be 
unresponsive. Mouse buttons as well. though can still move mouse on screen. 
Plugging in and out using arndr sometimes resolves this. Notwithstanding, no 
smooth transition to multimonitor mode.
- --- 
+ Plugging in External monitor using mini-display port causes keyboard to
+ be unresponsive. Mouse buttons as well. though can still move mouse on
+ screen. Plugging in and out using arndr sometimes resolves this.
+ Notwithstanding, no smooth transition to multi-monitor mode.
+ 
+ 
+ EDIT: 2018-11-22 // The problems are not observed when using HDMI instead of 
mini display-port. Moreover, if one can regain control of HID devices when mini 
DP plugged in, the resolution of the monitor plugged in is completely wrong. 
+ 
+ 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins:
-  (gconftool-2:31954): GConf-WARNING **: 21:41:20.841: Client failed to 
connect to the D-BUS daemon:
-  Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
-  Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
+  (gconftool-2:31954): GConf-WARNING **: 21:41:20.841: Client failed to 
connect to the D-BUS daemon:
+  Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
+  Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: 2018-10-17 21:42:48,989 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
-Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
+  Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
+    Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
  InstallationDate: Installed on 2016-07-23 (848 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmDisplayLog:
-  (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
-  (II) AIGLX: Suspending AIGLX clients for VT switch
-  (II) AIGLX: Suspending AIGLX clients for VT switch
-  (II) AIGLX: Suspending AIGLX clients for VT switch
+  (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
+  (II) AIGLX: Suspending AIGLX clients for VT switch
+  (II) AIGLX: Suspending AIGLX clients for VT switch
+  (II) AIGLX: Suspending AIGLX clients for VT switch
  MachineType: LENOVO 20F9004FUS
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=074ff7b7-c074-4137-8cf7-d46cdd7dd723 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic ubuntu
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (32 days ago)
  UserGroups:
-  
+ 
  _MarkForUpload: True
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9004FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20F9004FUS:pvrThinkPadT460s:rvnLENOVO:rn20F9004FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20F9004FUS
  dmi.product.sku: LENOVO_MT_20F9_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No 

[Desktop-packages] [Bug 1802569] Re: RM openssl1.0 from Ubuntu

2018-11-22 Thread Bug Watch Updater
** Changed in: opal (Debian)
   Status: New => Fix Released

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

Title:
  RM openssl1.0 from Ubuntu

Status in cfengine2 package in Ubuntu:
  Confirmed
Status in ckermit package in Ubuntu:
  Confirmed
Status in conserver package in Ubuntu:
  Confirmed
Status in cqrlog package in Ubuntu:
  Confirmed
Status in ekiga package in Ubuntu:
  Confirmed
Status in freerdp package in Ubuntu:
  New
Status in libpam-ssh package in Ubuntu:
  New
Status in mailavenger package in Ubuntu:
  Confirmed
Status in moonshot-trust-router package in Ubuntu:
  Confirmed
Status in netkit-ftp-ssl package in Ubuntu:
  Confirmed
Status in netty-tcnative-1.1 package in Ubuntu:
  New
Status in opal package in Ubuntu:
  Confirmed
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in osslsigncode package in Ubuntu:
  New
Status in pam-ssh-agent-auth package in Ubuntu:
  New
Status in pidentd package in Ubuntu:
  New
Status in ptlib package in Ubuntu:
  Confirmed
Status in qpid-proton package in Ubuntu:
  New
Status in radsecproxy package in Ubuntu:
  New
Status in reconserver package in Ubuntu:
  Confirmed
Status in resiprocate package in Ubuntu:
  New
Status in stunserver package in Ubuntu:
  New
Status in t38modem package in Ubuntu:
  Confirmed
Status in validns package in Ubuntu:
  New
Status in cfengine2 package in Debian:
  New
Status in ckermit package in Debian:
  New
Status in conserver package in Debian:
  New
Status in cqrlog package in Debian:
  New
Status in ekiga package in Debian:
  Fix Released
Status in freerdp package in Debian:
  Fix Released
Status in libpam-ssh package in Debian:
  New
Status in mailavenger package in Debian:
  Confirmed
Status in moonshot-trust-router package in Debian:
  New
Status in netkit-ftp-ssl package in Debian:
  New
Status in netty-tcnative-1.1 package in Debian:
  New
Status in opal package in Debian:
  Fix Released
Status in openssl1.0 package in Debian:
  New
Status in osslsigncode package in Debian:
  New
Status in pam-ssh-agent-auth package in Debian:
  New
Status in pidentd package in Debian:
  New
Status in ptlib package in Debian:
  Fix Released
Status in qpid-proton package in Debian:
  New
Status in radsecproxy package in Debian:
  Confirmed
Status in reconserver package in Debian:
  New
Status in resiprocate package in Debian:
  Confirmed
Status in stunserver package in Debian:
  Confirmed
Status in t38modem package in Debian:
  Fix Released
Status in validns package in Debian:
  Confirmed

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  opal/ptlib all of their reverse-deps are included for removal in this
  bug too.

  freerdp is superseeded by freerdp2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfengine2/+bug/1802569/+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 1717573] Re: Bad query error when searching in GNOME Software (special chars snap)

2018-11-22 Thread Paweł Stołowski
** Changed in: snapd
   Importance: Undecided => High

** Changed in: snapd
   Status: In Progress => Fix Committed

** Changed in: snapd
   Status: Fix Committed => Fix Released

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

Title:
  Bad query error when searching in GNOME Software (special chars snap)

Status in snapd:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  If a user types "=" into the search bar in GNOME Software when
  searching for an application, he gets a "bad query" error instead of
  the actual search results.

  Steps to reproduce:
  1. Open GNOME Software.
  2. Type "someapp=".

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1717573/+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 1766020] Re: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

2018-11-22 Thread Juan Alonso
Same problem, solution in #9 helped me.  (I am running Linux Mint 19)
saludos

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

Title:
  package python3 3.6.5-3 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Hello, error came up while updating. Paketmanager has canceled the
  update completely. Not yet analyzed for errors with console ...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3
  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-0ubuntu6
  Architecture: amd64
  Date: Sun Apr 22 00:01:23 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-04-04 (17 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1766020/+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 1804685] [NEW] icon view captions display in the wrong positions

2018-11-22 Thread Dan Green
Public bug reported:

In the Preferences for Nautilus, under the Views tab, the user has the
option to select information to appear in the "First", "Second", and
"Third" position beneath icons.  However, in icon view,  whatever the
user selects to appear in the "First" position will appear in the second
location beneath the icon.  Whatever the user selects to appear in the
"Second" position will appear in the third, or bottom, position.
Whatever the user selects to appear in the "Third" position will appear
in the first, or top, position.

I'm on

Ubuntu 18.04.1 LTS 
Nautilus 3.26.4-0~ubuntu18.04.2

Thanks!

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

** Attachment added: "screenshot of icon view caption incorrect mapping."
   
https://bugs.launchpad.net/bugs/1804685/+attachment/5215363/+files/Screenshot%20from%202018-11-22%2010-13-40.png

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

Title:
  icon view captions display in the wrong positions

Status in nautilus package in Ubuntu:
  New

Bug description:
  In the Preferences for Nautilus, under the Views tab, the user has the
  option to select information to appear in the "First", "Second", and
  "Third" position beneath icons.  However, in icon view,  whatever the
  user selects to appear in the "First" position will appear in the
  second location beneath the icon.  Whatever the user selects to appear
  in the "Second" position will appear in the third, or bottom,
  position.  Whatever the user selects to appear in the "Third" position
  will appear in the first, or top, position.

  I'm on

  Ubuntu 18.04.1 LTS 
  Nautilus 3.26.4-0~ubuntu18.04.2

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804685/+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 1772711] Re: Static library for libyajl is "libyajl_s.a" and pkg-config lies about it

2018-11-22 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately it's probably too far down our backlog to
ever make it to the top. In the meantime, patches welcome - though those
would probably be better going to Debian or upstream first.

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

Title:
  Static library for libyajl is "libyajl_s.a" and pkg-config lies about
  it

Status in yajl package in Ubuntu:
  Triaged
Status in yajl package in Debian:
  New

Bug description:
  The static library for libyajl-dev is installed as /usr/lib/x86_64
  -linux-gnu/libyajl_s.a and not /usr/lib/x86_64-linux-gnu/libyajl.a.
  This means that static linking with "-lyajl" will not find it; you
  need to use "-lyajl_s".

  This has not been explained to pkg-config (and I suspect the pkg-
  config file format can't express it). So when you do "pkg-config
  --static --libs yajl", you get back "-lyajl" and not "-lyajl_s". You
  also get the erroneous "-lyajl" when you ask pkg-config about anything
  that *depends* on yajl, such as raptor2:

  $ pkg-config --libs --static raptor2
  -lraptor2 -lcurl -lxml2 -lxslt -lxml2 -lyajl

  This makes pkg-config not work for linking statically against any
  library that depends on yajl.

  The Debian bug for this problem is at https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=877285 and has been sitting idel for several
  months. I've also opened an upstream bug at
  https://github.com/lloyd/yajl/issues/209 but the upstream project
  seems suspiciously quiet, and I think the upstream maintainer may have
  quit.

  I believe the actual problem with the upstream code is at
  
https://github.com/lloyd/yajl/blob/5e3a7856e643b4d6410ddc3f84bc2f38174f2872/src/CMakeLists.txt#L38-L40
  where CMake is told to build a static library and a dynamic library
  with different names. (This might be necessary on Windows, but nobody
  knows how to deal with it in Linux.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libyajl-dev 2.1.0-2
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 22 12:37:28 2018
  Dependencies:
   gcc-6-base 6.2.0-3ubuntu11~12.04 [origin: unknown]
   libc6 2.23-0ubuntu10
   libgcc1 1:6.2.0-3ubuntu11~12.04 [origin: unknown]
   libyajl2 2.1.0-2
   multiarch-support 2.23-0ubuntu10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-18 (1859 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: yajl
  UpgradeStatus: Upgraded to xenial on 2018-02-26 (85 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yajl/+bug/1772711/+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 1804663] Re: audio of web is off

2018-11-22 Thread giuseppe salvo
now i find out it is right excuse me

Il giorno gio 22 nov 2018 alle ore 15:50 Sebastien Bacher 
ha scritto:

> what do you call "web"? what web browser do you use? do you have sound
> in other places?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1804663
>
> Title:
>   audio of web is off
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   i don't hear anything from web
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
>   Uname: Linux 4.15.0-39-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Thu Nov 22 15:11:04 2018
>   DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed,
> re-reading
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if
> 00 [VGA controller])
>  Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT
> 530] [174b:7162]
>   InstallationDate: Installed on 2016-08-05 (838 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   MachineType: Packard Bell imedia S3840
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic
> root=UUID=562bbd01-6a42-4bcd-b109-080f909cc9ae ro quiet splash
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to bionic on 2018-08-31 (82 days ago)
>   dmi.bios.date: 07/08/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: P01-B1
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: imedia S3840
>   dmi.board.vendor: Packard Bell
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Packard Bell
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr:
>   dmi.product.family: Packard Bell Desktop
>   dmi.product.name: imedia S3840
>   dmi.product.version: P01-B1
>   dmi.sys.vendor: Packard Bell
>   version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
>   version.libdrm2: libdrm2 2.4.91-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.5-1ubuntu1
>   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
>   xserver.bootTime: Fri Aug 31 16:50:45 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 Logitech Wheel Mouse MOUSE, id 9
>   xserver.errors:
>Failed to load module "nvidia" (module does not exist, 0)
>Failed to load module "nvidia" (module does not exist, 0)
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-0ubuntu0.8
>   xserver.video_driver: nouveau
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1804663/+subscriptions
>

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

Title:
  audio of web is off

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  i don't hear anything from web

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov 22 15:11:04 2018
  DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 530] 
[174b:7162]
  InstallationDate: Installed on 2016-08-05 (838 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Packard Bell imedia S3840
  

[Desktop-packages] [Bug 1683445] Re: E6430 brightness control not working

2018-11-22 Thread Launchpad Bug Tracker
This bug was fixed in the package unity-settings-daemon -
15.04.1+16.04.20160701-0ubuntu2

---
unity-settings-daemon (15.04.1+16.04.20160701-0ubuntu2) xenial; urgency=medium

  [ Kai-Heng Feng ]
  * power: Choose correct backlight device on laptops with hybrid graphics
(LP: #1683445)
Backported from gnome-settings-daemon commit ed7c2744

 -- Sebastien Bacher   Tue, 03 Jul 2018 16:31:09
+0200

** Changed in: unity-settings-daemon (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  E6430 brightness control not working

Status in GNOME Settings Daemon:
  Fix Released
Status in Nouveau Xorg driver:
  Won't Fix
Status in OEM Priority Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in gnome-settings-daemon source package in Zesty:
  Fix Released
Status in unity-settings-daemon source package in Zesty:
  Won't Fix
Status in unity-settings-daemon source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+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 1772711] Re: Static library for libyajl is "libyajl_s.a" and pkg-config lies about it

2018-11-22 Thread Robie Basak
** Changed in: yajl (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: yajl (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Static library for libyajl is "libyajl_s.a" and pkg-config lies about
  it

Status in yajl package in Ubuntu:
  Triaged
Status in yajl package in Debian:
  New

Bug description:
  The static library for libyajl-dev is installed as /usr/lib/x86_64
  -linux-gnu/libyajl_s.a and not /usr/lib/x86_64-linux-gnu/libyajl.a.
  This means that static linking with "-lyajl" will not find it; you
  need to use "-lyajl_s".

  This has not been explained to pkg-config (and I suspect the pkg-
  config file format can't express it). So when you do "pkg-config
  --static --libs yajl", you get back "-lyajl" and not "-lyajl_s". You
  also get the erroneous "-lyajl" when you ask pkg-config about anything
  that *depends* on yajl, such as raptor2:

  $ pkg-config --libs --static raptor2
  -lraptor2 -lcurl -lxml2 -lxslt -lxml2 -lyajl

  This makes pkg-config not work for linking statically against any
  library that depends on yajl.

  The Debian bug for this problem is at https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=877285 and has been sitting idel for several
  months. I've also opened an upstream bug at
  https://github.com/lloyd/yajl/issues/209 but the upstream project
  seems suspiciously quiet, and I think the upstream maintainer may have
  quit.

  I believe the actual problem with the upstream code is at
  
https://github.com/lloyd/yajl/blob/5e3a7856e643b4d6410ddc3f84bc2f38174f2872/src/CMakeLists.txt#L38-L40
  where CMake is told to build a static library and a dynamic library
  with different names. (This might be necessary on Windows, but nobody
  knows how to deal with it in Linux.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libyajl-dev 2.1.0-2
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 22 12:37:28 2018
  Dependencies:
   gcc-6-base 6.2.0-3ubuntu11~12.04 [origin: unknown]
   libc6 2.23-0ubuntu10
   libgcc1 1:6.2.0-3ubuntu11~12.04 [origin: unknown]
   libyajl2 2.1.0-2
   multiarch-support 2.23-0ubuntu10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-18 (1859 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: yajl
  UpgradeStatus: Upgraded to xenial on 2018-02-26 (85 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yajl/+bug/1772711/+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 1768271] Re: sudo update-desktop-database results in "font/ttf" is an invalid MIME type ("font" is an unregistered media type)

2018-11-22 Thread Launchpad Bug Tracker
This bug was fixed in the package desktop-file-utils - 0.23-3ubuntu3

---
desktop-file-utils (0.23-3ubuntu3) cosmic; urgency=medium

  * debian/patches/add-font-as-valid-media-type.patch:
- backport debian change to fix update-desktop-error with
  gnome-font-viewer 3.28 (LP: #1768271)

 -- Sebastien Bacher   Tue, 06 Nov 2018 16:25:03
+0100

** Changed in: desktop-file-utils (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  sudo update-desktop-database results in "font/ttf" is an invalid MIME
  type ("font" is an unregistered media type)

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Bionic:
  Fix Committed
Status in desktop-file-utils source package in Cosmic:
  Fix Released

Bug description:
  * Impact

  The "update-desktop-database" command outputs some "invalid MIME type"
  warnings

  * Test case

  - install gnome-font-viewer if it's not installed
  - $ sudo update-desktop-database

  you should not get warnings like those
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/otf" is an invalid MIME type ("font" is an unregistered media type)

  * Regression potential

  Check that fonts files can still be opened from nautilus and preview
  (browse e.g /usr/share/fonts/type1/gsfonts in nautilus and open a file
  from there)

  --

  I think this is the same bug as this one:
  https://bugzilla.redhat.com/show_bug.cgi?id=1564650

  Other info:
  1.
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  2.
  $ apt-cache policy desktop-file-utils
  desktop-file-utils:
    Installed: 0.23-1ubuntu3
    Candidate: 0.23-1ubuntu3
    Version table:
   *** 0.23-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Expected `sudo update-desktop-database` to not return an error
  4. Error regarding invalid MIME type (see above) was returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 11:11:05 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: desktop-file-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1768271/+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 1739468] Re: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered

2018-11-22 Thread Phil Hanson
I see this when I try to install Microstack snap on Bionic

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

Title:
  Repeated [AppIndicatorSupport-WARN] Item
  :1.51/org/ayatana/NotificationItem/multiload is already registered

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in indicator-multiload package in Ubuntu:
  Confirmed

Bug description:
  The following message is continuously logged to /var/log/syslog (every
  few seconds):

  Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] 
Attempting to re-register :1.51/org/ayatana/NotificationItem/multiload; 
resetting instead
  Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Item 
:1.51/org/ayatana/NotificationItem/multiload is already registered


  It's hard to find anything in syslog because thousands of these
  messages intermingle with everything else

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 20 10:28:49 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-13 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1739468/+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 1802958] Re: libgs9-common not upgraded when libgs9 upgraded

2018-11-22 Thread Launchpad Bug Tracker
This bug was fixed in the package ghostscript -
9.25~dfsg+1-0ubuntu0.14.04.3

---
ghostscript (9.25~dfsg+1-0ubuntu0.14.04.3) trusty; urgency=medium

  * Fix dependency for libgs9-common (LP: #1802958)

 -- Ioanna Alifieraki   Mon, 12
Nov 2018 18:09:10 +

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

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

Title:
  libgs9-common not upgraded when libgs9 upgraded

Status in ghostscript package in Ubuntu:
  Fix Released
Status in ghostscript source package in Trusty:
  Fix Released
Status in ghostscript source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  ps2pdf stops working after upgrade of ghostscript to 
9.25~dfsg+1-0ubuntu0.14.04.2 .
  ghostscript and libgs9 are upgrated to 9.25~dfsg+1-0ubuntu0.14.04.2,
  but not libgs9-common which reamins at 9.25~dfsg+1-0ubuntu0.14.04.1 version.

  
  [Test Case]

  To reproduce the bug:
  Install 9.25~dfsg+1-0ubuntu0.14.04.1 version of ghostscript, libgs9 and 
libgs9-common.
  At this point ps2pdf should be working fine.
  Then sudo apt install ghostscript.
  ghostscript and libgs9 are upgraded but not libgs9-common.
  ps2pdf stops working :
  $ ps2pdf ascii.ps
  Unrecoverable error: typecheck in .bind
  Operand stack:
  --nostringval--  typecheck  --nostringval--  scheck  .gcheck

  
  [Regression Potential]

  Might cause problems when upgrading or installing ghostscript or
  libgs9

  
  [Other Info]

  This bug affects trusty and xenial.
  It is already fixed in bionic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1802958/+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 1768271] Update Released

2018-11-22 Thread Łukasz Zemczak
The verification of the Stable Release Update for desktop-file-utils has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  sudo update-desktop-database results in "font/ttf" is an invalid MIME
  type ("font" is an unregistered media type)

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Bionic:
  Fix Committed
Status in desktop-file-utils source package in Cosmic:
  Fix Released

Bug description:
  * Impact

  The "update-desktop-database" command outputs some "invalid MIME type"
  warnings

  * Test case

  - install gnome-font-viewer if it's not installed
  - $ sudo update-desktop-database

  you should not get warnings like those
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
  Error in file "/usr/share/applications/org.gnome.font-viewer.desktop": 
"font/otf" is an invalid MIME type ("font" is an unregistered media type)

  * Regression potential

  Check that fonts files can still be opened from nautilus and preview
  (browse e.g /usr/share/fonts/type1/gsfonts in nautilus and open a file
  from there)

  --

  I think this is the same bug as this one:
  https://bugzilla.redhat.com/show_bug.cgi?id=1564650

  Other info:
  1.
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  2.
  $ apt-cache policy desktop-file-utils
  desktop-file-utils:
    Installed: 0.23-1ubuntu3
    Candidate: 0.23-1ubuntu3
    Version table:
   *** 0.23-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. Expected `sudo update-desktop-database` to not return an error
  4. Error regarding invalid MIME type (see above) was returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 11:11:05 2018
  InstallationDate: Installed on 2018-04-29 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: desktop-file-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1768271/+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 1721893] Re: /usr/bin/gkbd-keyboard-display:11:get_preferred_height_for_width:gtk_widget_query_size_for_orientation:gtk_widget_compute_size_for_orientation:gtk_widget_get_prefe

2018-11-22 Thread Sebastien Bacher
** Description changed:

+ * Impact
+ The keyboard layout preview code segfault in some cases
+ 
+ * Test case
+ - call "gkbd-keyboard-display -l default", it should displays a keyboard 
drawing without segfaulting
+ 
+ also check that reports stop for the new version on the error tracker
+ url mentioned below
+ 
+ * Regression potential
+ check that the right keyboard layout is being drawn (in case where it was 
segfaulting before, it shouldn't impact on cases which were working)
+ 
+ -
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
libgnomekbd.  This problem was most recently seen with package version 
3.26.0-2, the problem page at 
https://errors.ubuntu.com/problem/7523168870802b9f73ecbee36701129263dcfaaa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Changed in: libgnomekbd (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  /usr/bin/gkbd-keyboard-
  
display:11:get_preferred_height_for_width:gtk_widget_query_size_for_orientation:gtk_widget_compute_size_for_orientation:gtk_widget_get_preferred_height_for_width:gtk_box_compute_size_for_orientation

Status in libgnomekbd :
  Confirmed
Status in libgnomekbd package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  The keyboard layout preview code segfault in some cases

  * Test case
  - call "gkbd-keyboard-display -l default", it should displays a keyboard 
drawing without segfaulting

  also check that reports stop for the new version on the error tracker
  url mentioned below

  * Regression potential
  check that the right keyboard layout is being drawn (in case where it was 
segfaulting before, it shouldn't impact on cases which were working)

  -

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgnomekbd/+bug/1721893/+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 1758290] Re: package libreoffice-common 1:4.2.8-0ubuntu5.2 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/www-graf/gryquest.gif.dpkg-new': Operat

2018-11-22 Thread Olivier Tilloy
This looks like a corrupted package problem.

Udo, did this go away with the latest libreoffice update
(1:4.2.8-0ubuntu5.3 on trusty)?

Or does re-installing the package solve the issue?

sudo apt install --reinstall libreoffice-common

** Changed in: libreoffice (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libreoffice-common 1:4.2.8-0ubuntu5.2 failed to
  install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery
  /www-graf/gryquest.gif.dpkg-new': Operation not permitted

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When starting Ubuntu 14.04 I get the Message "System program problem 
detected".
  Kind regards
  Udo

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-common 1:4.2.8-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Wed Mar 21 13:57:39 2018
  DuplicateSignature: package:libreoffice-common:1:4.2.8-0ubuntu5.2:unable to 
open '/usr/lib/libreoffice/share/gallery/www-graf/gryquest.gif.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/lib/libreoffice/share/gallery/www-graf/gryquest.gif.dpkg-new': Operation 
not permitted
  InstallationDate: Installed on 2016-03-03 (749 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.17
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:4.2.8-0ubuntu5.2 failed to 
install/upgrade: unable to open 
'/usr/lib/libreoffice/share/gallery/www-graf/gryquest.gif.dpkg-new': Operation 
not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1758290/+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 597851] Re: Cursor stays as busy cursor after launching Thunderbird

2018-11-22 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Thunderbird since that
time.

Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

Do you still see a problem related to the one that you reported in a
currently supported version of Ubuntu?

Please let us know if you do otherwise this bug report can be left to
expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  Cursor stays as busy cursor after launching Thunderbird

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: thunderbird

  When you launch Thunderbird, if you move the cursor off the
  Thunderbird application window it will appear as a busy cursor long
  after Thunderbird has finished loading.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.4+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Wed Jun 23 13:57:42 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/597851/+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 797283] Re: When closing thunderbird the thunderbird process stays at 100% the whole time

2018-11-22 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Thunderbird since that
time.

Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

Do you still see a problem related to the one that was reported in a
currently supported version of Ubuntu?

Please let us know if you do otherwise this bug report can be left to
expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


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

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

Title:
  When closing thunderbird the thunderbird process stays at 100% the
  whole time

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: thunderbird

  When closing thunderbird the thunderbird process stays at 100% the
  whole time

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: thunderbird 3.1.10+build1+nobinonly-0ubuntu0.11.04.2
  ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 2892cad67f71a4db0df94c8bed57c940
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  Date: Tue Jun 14 18:33:14 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to natty on 2011-04-14 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/797283/+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 220991] Re: Thunderbird corrupts attachments from IMAP exchange server

2018-11-22 Thread Paul White
Upstream bug is a duplicate of #92111 which was
closed "RESOLVED FIXED" on 2012-07-06
Target release - Thunderbird 16.0
No comments for over six years
Closing by marking "Fix Released"


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

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

Title:
  Thunderbird corrupts attachments from IMAP exchange server

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: thunderbird

  For the last two weeks, all the attachments I download from our
  exchange server via IMAP cannot be opened. After downloading or double
  clicking, PDFs and DOCs are reported broken, whereas before they
  opened correctly.

  I've been accessing my single Thunderbird profile on Ubuntu's EXT3
  file system both from Ubuntu and Windows XP for three months now. Both
  have the same problem. Roughly a month a go, some addresses of our
  exchange server changed, but I do not know if that was the only
  change. Downloading the attachments with Outlook via the Exchange
  Server connection or a IMAP connection still works.

  After downloading, the corrupt attachments are 20% smaller than the
  ones downloaded with Outlook.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Apr 23 14:18:37 2008
  DistroRelease: Ubuntu 7.10
  NonfreeKernelModules: fglrx
  Package: mozilla-thunderbird 2.0.0.12+nobinonly-0ubuntu0.7.10.0
  PackageArchitecture: all
  SourcePackage: thunderbird
  Uname: Linux DS1 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/220991/+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 118176] Re: No newlines in signature (*nix)

2018-11-22 Thread Paul White
To anyone affected by this bug,

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu and Thunderbird since that
time.

Do you still see a problem related to the one that was reported in a
currently supported version of Ubuntu?

Please let us know if you do otherwise this bug report can be left to
expire in approximately 60 days time.

I've tested using Ubuntu 18.04 and Thunderbird 60.2.1 and I don't see an
issue here.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: thunderbird (Ubuntu)
 Assignee: Mozilla Bugs (mozilla-bugs) => (unassigned)

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

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

Title:
  No newlines in signature (*nix)

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: mozilla-thunderbird

  My signature file - that is formated with \n newlines, since i use
  Linux - is copyed to the emails without the newlines. (probably the
  routine that attaches the signature to the message is expecting \r\n
  newlines)

  ProblemType: Bug
  Architecture: i386
  Date: Fri Jun  1 02:40:52 2007
  DistroRelease: Ubuntu 7.04
  Package: mozilla-thunderbird 1.5.0.10-0ubuntu3
  PackageArchitecture: i386
  SourcePackage: mozilla-thunderbird
  Uname: Linux rolo 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 
GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/118176/+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 1802569] Re: RM openssl1.0 from Ubuntu

2018-11-22 Thread Bug Watch Updater
** Changed in: ptlib (Debian)
   Status: New => Fix Released

** Changed in: t38modem (Debian)
   Status: New => Fix Released

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

Title:
  RM openssl1.0 from Ubuntu

Status in cfengine2 package in Ubuntu:
  Confirmed
Status in ckermit package in Ubuntu:
  Confirmed
Status in conserver package in Ubuntu:
  Confirmed
Status in cqrlog package in Ubuntu:
  Confirmed
Status in ekiga package in Ubuntu:
  Confirmed
Status in freerdp package in Ubuntu:
  New
Status in libpam-ssh package in Ubuntu:
  New
Status in mailavenger package in Ubuntu:
  Confirmed
Status in moonshot-trust-router package in Ubuntu:
  Confirmed
Status in netkit-ftp-ssl package in Ubuntu:
  Confirmed
Status in netty-tcnative-1.1 package in Ubuntu:
  New
Status in opal package in Ubuntu:
  Confirmed
Status in openssl1.0 package in Ubuntu:
  Incomplete
Status in osslsigncode package in Ubuntu:
  New
Status in pam-ssh-agent-auth package in Ubuntu:
  New
Status in pidentd package in Ubuntu:
  New
Status in ptlib package in Ubuntu:
  Confirmed
Status in qpid-proton package in Ubuntu:
  New
Status in radsecproxy package in Ubuntu:
  New
Status in reconserver package in Ubuntu:
  Confirmed
Status in resiprocate package in Ubuntu:
  New
Status in stunserver package in Ubuntu:
  New
Status in t38modem package in Ubuntu:
  Confirmed
Status in validns package in Ubuntu:
  New
Status in cfengine2 package in Debian:
  New
Status in ckermit package in Debian:
  New
Status in conserver package in Debian:
  New
Status in cqrlog package in Debian:
  New
Status in ekiga package in Debian:
  Fix Released
Status in freerdp package in Debian:
  Fix Released
Status in libpam-ssh package in Debian:
  New
Status in mailavenger package in Debian:
  Confirmed
Status in moonshot-trust-router package in Debian:
  New
Status in netkit-ftp-ssl package in Debian:
  New
Status in netty-tcnative-1.1 package in Debian:
  New
Status in opal package in Debian:
  New
Status in openssl1.0 package in Debian:
  New
Status in osslsigncode package in Debian:
  New
Status in pam-ssh-agent-auth package in Debian:
  New
Status in pidentd package in Debian:
  New
Status in ptlib package in Debian:
  Fix Released
Status in qpid-proton package in Debian:
  New
Status in radsecproxy package in Debian:
  Confirmed
Status in reconserver package in Debian:
  New
Status in resiprocate package in Debian:
  Confirmed
Status in stunserver package in Debian:
  Confirmed
Status in t38modem package in Debian:
  Fix Released
Status in validns package in Debian:
  Confirmed

Bug description:
  RM openssl1.0 from Ubuntu

  reconserver has multiple ftbfs issues / bugs.

  opal/ptlib all of their reverse-deps are included for removal in this
  bug too.

  freerdp is superseeded by freerdp2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfengine2/+bug/1802569/+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 1804657] Re: Double-clicking on Old Hungarian doesn't select the whole word in Writer

2018-11-22 Thread Olivier Tilloy
Note: on a default Ubuntu install there's no font to render Old
Hungarian. I downloaded the font from https://github.com/OldHungarian
/old-hungarian-font and unpacked the ttf file in ~/.fonts/ to get the
document to render as intended.

That's interesting. I tried the following Ubuntu/Libreoffice versions:

  6.0.6.2 from the Ubuntu 18.04 repositories, double-click to select a
word in Old Hungarian works as expected

  6.1.2.1 from the Ubuntu 18.10 repositories, works as expected too

  6.1.3.2 snap (candidate channel) on 18.04 and 18.10, works as expected
too

  6.1.3.2 snap (stable channel) on 18.04, I can reproduce the problem
you described

So it looks like this is a problem that affects only the snap in the
stable channel. The snap in the candidate channel was rebuilt against
core18 on bionic, see https://forum.snapcraft.io/t/call-for-testing-
libreoffice-based-on-core18/8620 for details.

Can you confirm that switching to the snap in the candidate channel
fixes the problem for you?

** Summary changed:

- Double-clicking on Old Hungarian doesn't select the whole word in Writer
+ [snap] Double-clicking on Old Hungarian doesn't select the whole word in 
Writer

** Tags added: snap

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

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

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  [snap] Double-clicking on Old Hungarian doesn't select the whole word
  in Writer

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that there is a regression that was introduced
  somewhere between LibreOffice 6.0.6.2 and 6.1.3.2, which I installed
  as a snap (version number 90) on Ubuntu 18.04. Steps to reproduce:

  1) Write a paragraph in Old Hungarian (Unicode block U+10C80 to
  U+10CFF).

  2) Double-click anywhere in the text.

  Double-clicking should select the whole word, and it works that way
  for most scripts (Latin, Arabic, and even Gothic), but for some reason
  for Old Hungarian, double-clicking only selects the individual
  character under the cursor. In LibreOffice 6.0.6.2 selecting Old
  Hungarian works as expected. For a sample paragraph in Old Hungarian,
  see the attached document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1804657/+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 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix

2018-11-22 Thread Paweł Stołowski
** Changed in: snapd
   Status: Fix Committed => Fix Released

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

Title:
  "Sorry, something went wrong cannot authenticate to snap store ..."
  without any way to fix

Status in snapd:
  Fix Released
Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  When I open this application, I see a message near the top that says
  "Sorry, something went wrong cannot authenticate to snap store:
  Provided email/password is not correct."

  I can close this message dialog, but there appears to be no way to
  remedy the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-software 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 13:08:16 2017
  EcryptfsInUse: Yes
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu2
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to artful on 2017-10-16 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1724316/+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 1704827] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

2018-11-22 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1705925 ***
https://bugs.launchpad.net/bugs/1705925

** This bug has been marked a duplicate of bug 1705925
   package libreoffice-gtk 1:5.1.6~rc2-0ubuntu1~xenial2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should 
reinstall it before attempting configuration

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libreoffice package in Ubuntu:
  New

Bug description:
  After a crash on the computer, Libreoffice no longer works. I can't
  remove it completely, so i can't reinstall the package. I'm not
  completely sure that libreoffice is the problem, but it's the only
  program i have found that does not work anymore.

  I have other computers, so i'm in no panic about this :-)

  The following is copied from a terminal window (in danish language):

  
  pbn@gigagoegler:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  pbn@gigagoegler:~$ apt-cache policy libreoffice
  libreoffice:
Installeret: (ingen)
Kandidat:1:5.1.6~rc2-0ubuntu1~xenial2
Versionstabel:
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://dk.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://dk.archive.ubuntu.com/ubuntu xenial-security/universe 
amd64 Packages
   1:5.1.2-0ubuntu1 500
  500 http://dk.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  pbn@gigagoegler:~$

  pbn@gigagoegler:~$ apt-cache policy libreoffice-common 
1:5.1.6~rc2-0ubuntu1~xenial2
  libreoffice-common:
Installeret: 1:5.1.6~rc2-0ubuntu1~xenial2
Kandidat:1:5.1.6~rc2-0ubuntu1~xenial2
Versionstabel:
   *** 1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://dk.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://dk.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://dk.archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://dk.archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1:5.1.2-0ubuntu1 500
  500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://dk.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  N: Kunne ikke lokalisere pakken 1:5.1.6~rc2-0ubuntu1~xenial2
  N: Kunne ikke finde nogle pakker med glob »1:5.1.6~rc2-0ubuntu1~xenial2«
  N: Kunne ikke finde nogle pakker med regulært udtryk 
»1:5.1.6~rc2-0ubuntu1~xenial2«
  pbn@gigagoegler:~$

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Mon Jul 17 09:22:15 2017
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial2
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package libreoffice-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-06-22 (390 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1704827/+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 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2018-11-22 Thread Christopher Barrington-Leigh
Same/very similar problem in 18.10.

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Unknown
Status in GNOME Shell:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions

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


  1   2   >