[Desktop-packages] [Bug 1811946] [NEW] black stripe in scans using canon lide 200 usb scanner

2019-01-16 Thread Jaroslav Hron
Public bug reported:

thick vertical black stripe in the middle scans using canon lide 200 usb
scanner

lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

apt-cache policy libsane1
libsane1:
  Installed: 1.0.27-1~experimental3ubuntu2
  Candidate: 1.0.27-1~experimental3ubuntu2
  Version table:
 *** 1.0.27-1~experimental3ubuntu2 500
500 http://ftp.cvut.cz/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libsane1 1.0.27-1~experimental3ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 16 09:16:04 2019
InstallationDate: Installed on 2019-01-14 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: sane-backends
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  black stripe in scans using canon lide 200 usb scanner

Status in sane-backends package in Ubuntu:
  New

Bug description:
  thick vertical black stripe in the middle scans using canon lide 200
  usb scanner

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  apt-cache policy libsane1
  libsane1:
Installed: 1.0.27-1~experimental3ubuntu2
Candidate: 1.0.27-1~experimental3ubuntu2
Version table:
   *** 1.0.27-1~experimental3ubuntu2 500
  500 http://ftp.cvut.cz/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental3ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 09:16:04 2019
  InstallationDate: Installed on 2019-01-14 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1811946/+subscriptions

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


[Desktop-packages] [Bug 1810929] Re: totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from _cogl_driver_update_features() from _cogl_winsys_context_init()

2019-01-16 Thread preethi
Thank you Daniel!

Reinstalling the nvidia-340 driver resolved the issue.

It was causing us a significant delay in our work. Thank you for helping
in resolution.

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

Title:
  totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from
  _cogl_driver_update_features() from _cogl_winsys_context_init()

Status in cogl package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Incomplete
Status in totem package in Ubuntu:
  Invalid

Bug description:
  ubuntu-bug /var/crash/_usr_bin_totem.2110.crash

  result of the  [Totem does not play MOV file with x264 encoding ]
  Bug # - 1810022

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Jan  8 04:41:26 2019
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 154218
  InstallationDate: Installed on 2018-11-12 (56 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Wed 2018-11-28 05:17:05 IST, end at Tue 2019-01-08 16:24:54 
IST. --
   -- No entries --
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcCmdline: totem DJI_0001.MOV
  ProcCwd: /data/data/home/blackbug/Data2017/9March/eve1
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ()
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_context_new () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1810929] Re: totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from _cogl_driver_update_features() from _cogl_winsys_context_init()

2019-01-16 Thread Daniel van Vugt
** Changed in: cogl (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  totem crashed with SIGSEGV in_cogl_context_get_gl_extensions() from
  _cogl_driver_update_features() from _cogl_winsys_context_init()

Status in cogl package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  ubuntu-bug /var/crash/_usr_bin_totem.2110.crash

  result of the  [Totem does not play MOV file with x264 encoding ]
  Bug # - 1810022

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Tue Jan  8 04:41:26 2019
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 154218
  InstallationDate: Installed on 2018-11-12 (56 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  JournalErrors:
   Hint: You are currently not seeing messages from other users and the system.
 Users in groups 'adm', 'systemd-journal' can see all messages.
 Pass -q to turn off this notice.
   -- Logs begin at Wed 2018-11-28 05:17:05 IST, end at Tue 2019-01-08 16:24:54 
IST. --
   -- No entries --
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcCmdline: totem DJI_0001.MOV
  ProcCwd: /data/data/home/blackbug/Data2017/9March/eve1
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ()
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_context_new () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1811717] Re: Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop disappear

2019-01-16 Thread Iain Lane
thx

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop
  disappear

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released

Bug description:
  I have some icons on desktop (applications folders and files)
  Changing Dock Icon size (Settings-Dock-Icon size) the icons on desktop 
disappear, they reappear creating a file or a folder in the desktop or in 
/Home/Desktop
  sometimes they reappear also changing Icon size again.

  Problem happen both with x11 and wayland session.

  corrado@corrado-p6-dd-1227:~$ inxi -SCGx
  System:
Host: corrado-p6-dd-1227 Kernel: 4.18.0-11-generic x86_64 bits: 64 
compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2 
Distro: Ubuntu 19.04 (Disco Dingo) 
  CPU:
Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 18.2.6 direct render: Yes 
  corrado@corrado-p6-dd-1227:~$ 

  corrado@corrado-p6-dd-1227:~$ apt policy nautilus
  nautilus:
Installed: 1:3.30.4-1ubuntu1
Candidate: 1:3.30.4-1ubuntu1
Version table:
   *** 1:3.30.4-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p6-dd-1227:~$ 

  gnome-shell-extension-desktop-icons:
Installed: 18.11~rc+git20181217-1
Candidate: 18.11~rc+git20181217-1
Version table:
   *** 18.11~rc+git20181217-1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu disco/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 20:10:16 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1252, 581)'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2018-12-27 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181227)
  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/gnome-shell-extension-desktop-icons/+bug/1811717/+subscriptions

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


[Desktop-packages] [Bug 1811924] Re: package libreoffice-help-es 1:6.0.3-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/share/libreoffice/help/es/swriter.tree' before install

2019-01-16 Thread Olivier Tilloy
This looks like a corrupt package or filesystem error.
Try running the following command in a terminal, does this fix the problem?

sudo apt install --reinstall libreoffice-help-es

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

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

Title:
  package libreoffice-help-es 1:6.0.3-0ubuntu1 failed to
  install/upgrade: unable to make backup link of
  './usr/share/libreoffice/help/es/swriter.tree' before installing new
  version: Input/output error

Status in libreoffice-l10n package in Ubuntu:
  Incomplete

Bug description:
  trying to run sudo apt upgrade and this happened

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-help-es 1:6.0.3-0ubuntu1
  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.5
  Architecture: amd64
  CasperVersion: 1.394
  Date: Wed Jan 16 05:15:07 2019
  ErrorMessage: unable to make backup link of 
'./usr/share/libreoffice/help/es/swriter.tree' before installing new version: 
Input/output error
  LiveMediaBuild: 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/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libreoffice-l10n
  Title: package libreoffice-help-es 1:6.0.3-0ubuntu1 failed to 
install/upgrade: unable to make backup link of 
'./usr/share/libreoffice/help/es/swriter.tree' before installing new version: 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-l10n/+bug/1811924/+subscriptions

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


[Desktop-packages] [Bug 1811887] Re: Firefox freezes when trying to download a file

2019-01-16 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1811105 ***
https://bugs.launchpad.net/bugs/1811105

This looks very similar to bug #1811105, so I'm going to mark it as a
duplicate. Please check out the screencast attached to that other bug
and confirm whether it's the same problem. If not, feel free to remove
the duplicate status. Thanks!

** This bug has been marked a duplicate of bug 1811105
   Browser hangs when 'open with' dialog opens.

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

Title:
  Firefox freezes when trying to download a file

Status in firefox package in Ubuntu:
  New

Bug description:
  When I browse to a file in Firefox, it opens a popup asking me if I
  want to open it or download it. At this moment, Firefox starts using
  100% CPU and freezes.

  I started having this problem after a recent update.
  It also happens with safe mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: firefox 64.0+build3-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1936 F pulseaudio
  BuildID: 20181207224759
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Tue Jan 15 20:12:38 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (1014 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp2s0 scope link metric 1000
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.21 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207224759 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1811105] Re: Browser hangs when 'open with' dialog opens.

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

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

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

Title:
  Browser hangs when 'open with' dialog opens.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 18.04.1 LTS x86_64 with GNOME 3.28.3.
  2) Firefox: Installed: 64.0+build3-0ubuntu0.18.04.1
  3) Dialog box 'open as' to respond to click events in elements and whole 
browser not get inoperable.
  4) Dialog box 'open as' hangs, gets inoperable to click commands (close, 
cancel, ok, save file) when trying to open some attacked file.

  My browser started to hang when the dialog 'open as' appears. It's
  very useful since it quickly opens an attached file from gmail or
  browsing pdf/doc files.

  When the dialog opens, both the dialog and the browser window get
  extremely slow and i have to click several times for the dialog to
  close. No other button responds and sometimes the crash dialog asks if
  i want to force quit or wait.

  I'm having this problem for two weeks now and got so annoyed that
  sadly had to switch back to chrome. This is a very nice feature that
  doesn't work on said browser.

  I already uninstalled/installed, cleaned data and installed a nightly
  build without success. I suspect it's something related to window
  manager or nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 64.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilherme   3261 F pulseaudio
  BuildID: 20181207224003
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  9 13:28:59 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet dhcp
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-14 (785 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (140 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 234
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K45A
  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.:bvr234:bd11/25/2014:svnASUSTeKCOMPUTERINC.:pnK45A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK45A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K45A
  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/firefox/+bug/1811105/+subscriptions

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


[Desktop-packages] [Bug 1811105] Re: Browser hangs when 'open with' dialog opens.

2019-01-16 Thread Olivier Tilloy
** Changed in: firefox (Ubuntu)
   Status: Incomplete => New

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

Title:
  Browser hangs when 'open with' dialog opens.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 18.04.1 LTS x86_64 with GNOME 3.28.3.
  2) Firefox: Installed: 64.0+build3-0ubuntu0.18.04.1
  3) Dialog box 'open as' to respond to click events in elements and whole 
browser not get inoperable.
  4) Dialog box 'open as' hangs, gets inoperable to click commands (close, 
cancel, ok, save file) when trying to open some attacked file.

  My browser started to hang when the dialog 'open as' appears. It's
  very useful since it quickly opens an attached file from gmail or
  browsing pdf/doc files.

  When the dialog opens, both the dialog and the browser window get
  extremely slow and i have to click several times for the dialog to
  close. No other button responds and sometimes the crash dialog asks if
  i want to force quit or wait.

  I'm having this problem for two weeks now and got so annoyed that
  sadly had to switch back to chrome. This is a very nice feature that
  doesn't work on said browser.

  I already uninstalled/installed, cleaned data and installed a nightly
  build without success. I suspect it's something related to window
  manager or nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 64.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilherme   3261 F pulseaudio
  BuildID: 20181207224003
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  9 13:28:59 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet dhcp
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-11-14 (785 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207224003
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (140 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 234
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K45A
  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.:bvr234:bd11/25/2014:svnASUSTeKCOMPUTERINC.:pnK45A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK45A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K45A
  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/firefox/+bug/1811105/+subscriptions

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


[Desktop-packages] [Bug 1810902] Re: firefox picks unpredictable window for opening new content when using i3 as a window manager

2019-01-16 Thread Olivier Tilloy
Does the bug occur if you disable the focus-follows-mouse policy?

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

Title:
  firefox picks unpredictable window for opening new content when using
  i3 as a window manager

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When a firefox instance is running with multiple windows, typing
  "firefox somepage" should open somepage in an existing window.
  Previously, that window was the last window accessed.  Now, it is
  difficult to predict in which window the new tab will open.  Indeed,
  it may open in a window in a different workspace even though the a
  window in the current workspace has been used more recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 64.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   4822 F pulseaudio
   /dev/snd/pcmC1D0p:   jeff   4822 F...m pulseaudio
   /dev/snd/controlC1:  jeff   4822 F pulseaudio
  BuildID: 20181207224003
  Channel: Unavailable
  CurrentDesktop: i3
  Date: Tue Jan  8 08:43:06 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-23 (1172 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.2.1 dev eth1 proto dhcp metric 100 
   169.254.0.0/16 dev eth1 scope link metric 1000 
   192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.87 metric 100
  MostRecentCrashID: bp-a0847816-1a40-4e81-8110-dc8171180221
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins:
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2Plugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4PrefSources: prefs.js
  Profile4Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=64.0/20181207224003 (In use)
   Profile1 - LastVersion=50.0.2/20161130094234 (Out of date)
   Profile2 - LastVersion=56.0/20171003100843 (Out of date)
   Profile3 - LastVersion=64.0/20181207224003 (In use)
   Profile4 - LastVersion=60.0.2/20180607190419 (Out of date)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-06-14 (207 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B220P007
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID92/ZBOX-IQ01
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB220P007:bd05/21/2014:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID92/ZBOX-IQ01
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

To manage notif

[Desktop-packages] [Bug 1811887] Re: Firefox freezes when trying to download a file

2019-01-16 Thread Pierre Rudloff
*** This bug is a duplicate of bug 1811105 ***
https://bugs.launchpad.net/bugs/1811105

I confirm that it looks very similar and is probably the same bug. Sorry
for the duplicate.

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

Title:
  Firefox freezes when trying to download a file

Status in firefox package in Ubuntu:
  New

Bug description:
  When I browse to a file in Firefox, it opens a popup asking me if I
  want to open it or download it. At this moment, Firefox starts using
  100% CPU and freezes.

  I started having this problem after a recent update.
  It also happens with safe mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: firefox 64.0+build3-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1936 F pulseaudio
  BuildID: 20181207224759
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Tue Jan 15 20:12:38 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (1014 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp2s0 scope link metric 1000
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.21 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207224759 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1810902] Re: firefox picks unpredictable window for opening new content

2019-01-16 Thread Olivier Tilloy
The use of i3 is likely relevant. I can't reproduce the problem with
gnome shell.

** Summary changed:

- firefox picks unpredictable window for opening new content
+ firefox picks unpredictable window for opening new content when using i3 as a 
window manager

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

Title:
  firefox picks unpredictable window for opening new content when using
  i3 as a window manager

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When a firefox instance is running with multiple windows, typing
  "firefox somepage" should open somepage in an existing window.
  Previously, that window was the last window accessed.  Now, it is
  difficult to predict in which window the new tab will open.  Indeed,
  it may open in a window in a different workspace even though the a
  window in the current workspace has been used more recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 64.0+build3-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   4822 F pulseaudio
   /dev/snd/pcmC1D0p:   jeff   4822 F...m pulseaudio
   /dev/snd/controlC1:  jeff   4822 F pulseaudio
  BuildID: 20181207224003
  Channel: Unavailable
  CurrentDesktop: i3
  Date: Tue Jan  8 08:43:06 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-23 (1172 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.2.1 dev eth1 proto dhcp metric 100 
   169.254.0.0/16 dev eth1 scope link metric 1000 
   192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.87 metric 100
  MostRecentCrashID: bp-a0847816-1a40-4e81-8110-dc8171180221
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins:
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2Plugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profile4Extensions: extensions.sqlite corrupt or missing
  Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile4Locales: extensions.sqlite corrupt or missing
  Profile4PrefSources: prefs.js
  Profile4Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=64.0/20181207224003 (In use)
   Profile1 - LastVersion=50.0.2/20161130094234 (Out of date)
   Profile2 - LastVersion=56.0/20171003100843 (Out of date)
   Profile3 - LastVersion=64.0/20181207224003 (In use)
   Profile4 - LastVersion=60.0.2/20180607190419 (Out of date)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-06-14 (207 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B220P007
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID92/ZBOX-IQ01
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB220P007:bd05/21/2014:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/Z

[Desktop-packages] [Bug 40610] Re: History wiped out if disk full when firefox exits

2019-01-16 Thread Paul White
Upstream bug showing "RESOLVED WORKSFORME" since 2015-05-28
Reporter has said not an issue since Firefox 38
No further comments for nearly 4 years so closing.


** Changed in: firefox (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  History wiped out if disk full when firefox exits

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox-3.0 package in Ubuntu:
  Invalid

Bug description:
  If the disk is full when Firefox is closed (or crashes, or is OOM-
  killed by the kernel) the history will be completely wiped out.  This
  is a grave bug as it leads to data loss.

  Of course it can't save the new history if the disk is full but it
  should fall back to the last saved history rather than losing data.

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

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


[Desktop-packages] [Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Fusion
This is not the same bug. After resuming from suspend with a new
installation of ubuntu 18.10 and no extensions installed this happened:

https://i.postimg.cc/XJqGb1xy/photo-2019-01-16-11-54-12.jpg

The left panel is over the purple-like lock screen and unusable (the only thing 
is that icons illuminate with mouse movement but they don't respond on click.
The top panel respond but it has only suspend option enabled.

So, the solution for me is:
1. ctrl+alt+F1 , put my password and see all opened windows once again (without 
restart)
2. restart
3. enable asking password after suspend*


*to explain that (because of the other bug): 
The change I did is to disable from gnome-settings the privacy/lock 
screen/automatic lock screen option.

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  my system:
  ubuntu 18.10
  4k monitor with 1 scale and 1.5 font scale
  nvidia 410 and 390 drivers are checked

  when happened:
  lock screen or suspend. return after that.
  if I have user password prompt enabled: everything ok
  if I haven't user password prompt enabled, system started with gnome crashed

  I expect:
  ubuntu to has the same behaviour either I have a password either not.

  What happened:
  in case of no password (I should just 'swipe up' or press 'space' and 
everything should be ready.. but) most of the times I can not return to desktop.
  - freezes on a screen with panels but no desktop
  - freezes on a purple screen that no command is working (as ctrl+alt+t)
  - freezes on a useless gnome panels (dash and topbar) mode

  solution chosen:
  I press ctrl+alt+F1 to change environment, I enter my password... BUT again 
the gnome is too slow, app icon is always on and everything is acting weird 
(some apps' icon that I have opened on the other session is liked pined on dash 
without have the option to unpin it - like I see it but it is not pinned)
  So, I just save what I can through the new session and just restart the pc 
(in new session is available - in the previous is only suspend available)

  frequency: about 80% of the times. If lock-screen showed up normally
  (and I have to press space to unlock) everything works like a charm
  afterwards. If not.. it will be the mess I described above

  hope it helps
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-08-28 (84 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (32 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1015751] Re: Text is randomly rendered bold when scrolling

2019-01-16 Thread Paul White
Big did not expire due to bug watch
Upstream bug showing "RESOLVED WORKSFORME" since 2012-12-21
No reply to comment #7
So closing as no comments re issue for over 6 years


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

** Changed in: firefox (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  Text is randomly rendered bold when scrolling

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  I noticed that on some sites (reddit.com and a few forums) text
  appears randomly bolded, even if it shouldn't be. Its appearance
  reverts to a normal state after selecting the text, taking a
  screenshot, opening a window over the text etc.

  What you expected to happen:
  Firefox displaying normal text.

  What happened instead:
  Firefox displays randomly bolded text when scrolling a website.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 13.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
  Uname: Linux 3.2.0-25-generic-pae i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  romano 1832 F pulseaudio
   /dev/snd/pcmC0D0p:   romano 1832 F...m pulseaudio
  BuildID: 20120601173917
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xdbff8000 irq 22'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,18493662,00100101'
 Controls  : 32
 Simple ctrls  : 17
  Channel: release
  Date: Wed Jun 20 20:36:18 2012
  DefaultProfilePrefErrors: Unexpected character before close parenthesis @ 
[Profile]/extensions/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}/defaults/preferences/greasemonkey.js:4
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MostRecentCrashID: bp-5da2c515-dd81-4bf0-8a39-9929f2120503
  PciNetwork:
   
  ProcEnviron:
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile0 (Default) - LastVersion=13.0/20120601173917 (In use)
   Profile1 - LastVersion=13.0/20120601173917
   Profile2 - LastVersion=13.0/20120601173917
  RelatedPackageVersions:
   gnome-shell   3.4.1-0ubuntu2
   icedtea-6-plugin  1.2-2ubuntu1
   rhythmbox-mozilla 2.96-0ubuntu4
   totem-mozilla 3.0.1-0ubuntu21
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-5da2c515-dd81-4bf0-8a39-9929f2120503
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: ALiveNF6P-VSTA
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd04/09/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6P-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 651771] Re: Spellchecker always causing SEGFAULT

2019-01-16 Thread Paul White
Report is over 8 years old
No reply to comment #8
Bug did not expire
So closing

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

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

Title:
  Spellchecker always causing SEGFAULT

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Firefix barely gets started before it segfaults. After installing
  debug symbols and running with --debug with no addons in a guest
  session, I can get the following stack trace pointing to the spell
  checker. Turning off the 'check my spelling' option stops the crashes.

  
  guest@:~$ firefox --debug
  /usr/lib/firefox-3.6.10/run-mozilla.sh -g /usr/lib/firefox-3.6.10/firefox-bin
  MOZILLA_FIVE_HOME=/usr/lib/firefox-3.6.10

LD_LIBRARY_PATH=/usr/lib/firefox-3.6.10:/usr/lib/firefox-3.6.10/plugins:/usr/lib/firefox-3.6.10
  DISPLAY=:3.0
  DYLD_LIBRARY_PATH=/usr/lib/firefox-3.6.10:/usr/lib/firefox-3.6.10
   
LIBRARY_PATH=/usr/lib/firefox-3.6.10:/usr/lib/firefox-3.6.10/components:/usr/lib/firefox-3.6.10
 SHLIB_PATH=/usr/lib/firefox-3.6.10:/usr/lib/firefox-3.6.10
LIBPATH=/usr/lib/firefox-3.6.10:/usr/lib/firefox-3.6.10
 ADDON_PATH=/usr/lib/firefox-3.6.10
MOZ_PROGRAM=/usr/lib/firefox-3.6.10/firefox-bin
MOZ_TOOLKIT=
  moz_debug=1
   moz_debugger=
  /usr/bin/gdb /usr/lib/firefox-3.6.10/firefox-bin -x /tmp/mozargs.SapGeZ
  GNU gdb (GDB) 7.2-ubuntu
  Copyright (C) 2010 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  ...
  Reading symbols from /usr/lib/firefox-3.6.10/firefox-bin...Reading symbols 
from /usr/lib/debug/usr/lib/firefox-3.6.10/firefox-bin...done.
  done.
  (gdb) run
  Starting program: /usr/lib/firefox-3.6.10/firefox-bin 
  [Thread debugging using libthread_db enabled]
  [New Thread 0x7fffe79ff710 (LWP 6323)]
  [New Thread 0x7fffe71fe710 (LWP 6324)]
  [New Thread 0x7fffe66ff710 (LWP 6325)]
  [New Thread 0x7fffe5efe710 (LWP 6326)]
  [New Thread 0x7fffe56fd710 (LWP 6327)]
  [Thread 0x7fffe56fd710 (LWP 6327) exited]
  [Thread 0x7fffe66ff710 (LWP 6325) exited]
  [Thread 0x7fffe5efe710 (LWP 6326) exited]
  [Thread 0x7fffe71fe710 (LWP 6324) exited]
  [Thread 0x7fffe79ff710 (LWP 6323) exited]
  process 6320 is executing new program: /usr/lib/firefox-3.6.10/firefox-bin
  [Thread debugging using libthread_db enabled]
  [New Thread 0x7fffe79ff710 (LWP 6328)]
  [New Thread 0x7fffe6ffa710 (LWP 6329)]
  [New Thread 0x7fffe64ff710 (LWP 6330)]
  [New Thread 0x7fffe5cfe710 (LWP 6331)]
  [New Thread 0x7fffe54fd710 (LWP 6332)]
  [New Thread 0x7fffe4cfc710 (LWP 6333)]
  [New Thread 0x7fffe29f6710 (LWP 6334)]
  [Thread 0x7fffe29f6710 (LWP 6334) exited]
  [New Thread 0x7fffe29f6710 (LWP 6335)]
  [Thread 0x7fffe54fd710 (LWP 6332) exited]
  [Thread 0x7fffe29f6710 (LWP 6335) exited]
  [Thread 0x7fffe4cfc710 (LWP 6333) exited]
  [Thread 0x7fffe5cfe710 (LWP 6331) exited]
  [Thread 0x7fffe64ff710 (LWP 6330) exited]
  [Thread 0x7fffe6ffa710 (LWP 6329) exited]
  [Thread 0x7fffe79ff710 (LWP 6328) exited]
  process 6320 is executing new program: /usr/lib/firefox-3.6.10/firefox-bin
  [Thread debugging using libthread_db enabled]
  [New Thread 0x7fffe79ff710 (LWP 6336)]
  [New Thread 0x7fffe6ffa710 (LWP 6337)]
  [New Thread 0x7fffe64ff710 (LWP 6338)]
  [New Thread 0x7fffe5cfe710 (LWP 6339)]
  [New Thread 0x7fffe54fd710 (LWP 6340)]
  [New Thread 0x7fffe4cfc710 (LWP 6341)]
  [New Thread 0x7fffe26ff710 (LWP 6342)]
  [Thread 0x7fffe26ff710 (LWP 6342) exited]
  [New Thread 0x7fffe26ff710 (LWP 6343)]
  [New Thread 0x7fffe15ff710 (LWP 6344)]
  [New Thread 0x7fffdecff710 (LWP 6345)]
  [New Thread 0x7fffdd7b9710 (LWP 6346)]
  [New Thread 0x7fffdcfb8710 (LWP 6347)]
  [New Thread 0x7fffdc5ff710 (LWP 6348)]
  [New Thread 0x7fffdbbff710 (LWP 6349)]
  *** NSPlugin Viewer  *** WARNING: unhandled variable 18 () 
in NPN_GetValue()
  *** NSPlugin Viewer  *** WARNING: unhandled variable 18 () 
in NPN_GetValue()

  Program received signal SIGSEGV, Segmentation fault.
  0x771c8fe1 in AffixMgr::parse_file (this=0x7fffd61bf000, 
  affpath=, key=)
  at affixmgr.cpp:759
  759   affixmgr.cpp: No such file or directory.
in affixmgr.cpp
  (gdb) bt
  #0  0x771c8fe1 in AffixMgr::parse_file (this=0x7fffd61bf000, 
  affpath=, key=)
  at affixmgr.cpp:759
  #1  0x771c9417 in AffixMgr::AffixMgr (this=0x7fffd61bf000, 
  affpath=0x0, ptr=, md=0x0, key=0x77eb1040 "")
  at affixmgr.cpp:168
  #2  0x771d22d2 in Hun

[Desktop-packages] [Bug 1811887] Re: Firefox freezes when trying to download a file

2019-01-16 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1811105 ***
https://bugs.launchpad.net/bugs/1811105

Don't be sorry, that's what triaging is for :)
Thanks for the confirmation.

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

Title:
  Firefox freezes when trying to download a file

Status in firefox package in Ubuntu:
  New

Bug description:
  When I browse to a file in Firefox, it opens a popup asking me if I
  want to open it or download it. At this moment, Firefox starts using
  100% CPU and freezes.

  I started having this problem after a recent update.
  It also happens with safe mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: firefox 64.0+build3-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1936 F pulseaudio
  BuildID: 20181207224759
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Tue Jan 15 20:12:38 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-04-06 (1014 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp2s0 scope link metric 1000
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.21 metric 600
  MostRecentCrashID: bp-cf7fd7ab-ccc0-4602-903e-12ff90180908
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=64.0/20181207224759 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W510LU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:svnNotebook:pnW510LU:pvrNotApplicable:rvnNotebook:rnW510LU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W510LU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1712587] Re: Firefox 55 instantly crashes on Google Maps

2019-01-16 Thread Paul White
Bug did not close due bug watch
Upstream report has since been closed "RESOLVED WORKSFORME"
No reply from reporter so closing


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

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

Title:
  Firefox 55 instantly crashes on Google Maps

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  To reproduce:

  1. Go to http://maps.google.co.uk

  Result: Firefox instantly crashes.

  I tried disabling hardware acceleration. It didn't make any
  difference.

  This crash is 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  al 2782 F pulseaudio
   /dev/snd/controlC1:  al 2782 F pulseaudio
   /dev/snd/controlC2:  al 2782 F pulseaudio
   /dev/snd/controlC0:  al 2782 F pulseaudio
  BuildID: 20170816210634
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Wed Aug 23 14:46:26 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-07-12 (773 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  IpRoute:
   default via 192.168.0.1 dev enp0s31f6  proto static  metric 100 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.0.0/24 dev enp0s31f6  proto kernel  scope link  src 192.168.0.5  
metric 100
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
   
   docker0   no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-b982df2a-0748-4395-a586-f88c01170823
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816210634 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-b982df2a-0748-4395-a586-f88c01170823
   bp-93cc1950-6206-4734-99b7-7cfea1170823
   bp-7dec83a1-282b-4c55-9b8f-3f5690170823
   bp-d61de9e9-55ac-4c4d-8f89-867360170823
   bp-f907228f-d818-4d12-8ff5-cef060170823
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd03/24/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Desktop-packages] [Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Fusion
ps. on /var/crash there is only a "_user_bin_variety.1000.crash" and
some variety and rhythmbox .uploaded

With the "journalctl -b 0" log may I have a little more details? I
should suspend, return and then ctrl+alt+F1 , login and write
"journalctl -b 0" on terminal? how can I export it on file? or just
copy-paste the results? Thanks again and forgive my ignorance.

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

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  my system:
  ubuntu 18.10
  4k monitor with 1 scale and 1.5 font scale
  nvidia 410 and 390 drivers are checked

  when happened:
  lock screen or suspend. return after that.
  if I have user password prompt enabled: everything ok
  if I haven't user password prompt enabled, system started with gnome crashed

  I expect:
  ubuntu to has the same behaviour either I have a password either not.

  What happened:
  in case of no password (I should just 'swipe up' or press 'space' and 
everything should be ready.. but) most of the times I can not return to desktop.
  - freezes on a screen with panels but no desktop
  - freezes on a purple screen that no command is working (as ctrl+alt+t)
  - freezes on a useless gnome panels (dash and topbar) mode

  solution chosen:
  I press ctrl+alt+F1 to change environment, I enter my password... BUT again 
the gnome is too slow, app icon is always on and everything is acting weird 
(some apps' icon that I have opened on the other session is liked pined on dash 
without have the option to unpin it - like I see it but it is not pinned)
  So, I just save what I can through the new session and just restart the pc 
(in new session is available - in the previous is only suspend available)

  frequency: about 80% of the times. If lock-screen showed up normally
  (and I have to press space to unlock) everything works like a charm
  afterwards. If not.. it will be the mess I described above

  hope it helps
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-08-28 (84 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (32 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1811530] Re: Impress embeded video files show flickering white stripes

2019-01-16 Thread Olivier Tilloy
Thanks! Looking forward to your feedback on the upstream packages.

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

Title:
  Impress embeded video files show flickering white stripes

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1105328] Re: Firefox renders text poorly on some sites

2019-01-16 Thread Paul White
No reply for info from reporter
Bug did not expire due to bugwatch
Comments 15 and 17 suggest fixed so closing

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

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

Title:
  Firefox renders text poorly on some sites

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Firefox has begun rendering fonts incorrectly in some situations.  I
  have noticed this mostly in Gmail and Google Docs, where red text will
  have dark pixels on the left side of characters (see attachment; left
  is Firefox, right is Chrome).  On some other websites, lightly-colored
  text will have lighter-colored pixels drawn on the left side of the
  characters.  However, the issue is not limited to red text.  Even
  black text seems rendered/smoothed poorly in Firefox compared to
  Chrome (perhaps this part is subjective).

  Oddly it also does not happen on every website.  Writing "Gmail" and
  "Inbox" in red 12pt Arial in Google Documents exhibits the problem
  seen in the attached screenshot, while writing the same text in Zoho
  Writer does not.  In Google Documents, I can actually see the text
  rendered without this problem for a moment as the page loads, but
  something gets applied during the page loading process that changes
  the rendering to its final distorted state.

  Finally, running in safe mode or using a new profile do not affect
  this problem.  I do not recall seeing this problem in versions before
  18.0, but it could have been around in later revisions of v17.  I also
  haven't been able to notice this problem in other desktop
  applications.

  Release: Ubuntu 12.10
  Package: Firefox 18.0.1+build1-0ubuntu0.12.10.1
  Expected: Fonts are drawn correctly.
  Instead: Colored fonts have incorrectly-colored features on the left side.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: firefox 18.0.1+build1-0ubuntu0.12.10.1
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fourwood   1988 F pulseaudio
  BuildID: 20130116231921
  Channel: Unavailable
  Date: Fri Jan 25 11:45:31 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2011-10-16 (467 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  IpRoute:
   default via 192.168.5.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.5.0/24 dev eth0  proto kernel  scope link  src 192.168.5.165  metric 
1
  MarkForUpload: True
  MostRecentCrashID: bp-ea3fb463-f6c0-499e-b262-b35e42120312
  PrefSources:
   prefs.js
   [Profile]/extensions/twitternotif...@naan.net/defaults/preferences/pref.js
  Profiles: Profile0 (Default) - LastVersion=18.0.1/20130116231921 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.97-1ubuntu6.1
   icedtea-7-plugin  1.3-1ubuntu1.1
   totem-mozilla 3.4.3-0ubuntu5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-ea3fb463-f6c0-499e-b262-b35e42120312
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (98 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/10/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0HT027
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd10/10/2008:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0HT027:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1811966] Re: ibus-daemon crashed with SIGABRT

2019-01-16 Thread Apport retracing service
*** This bug is a duplicate of bug 1545811 ***
https://bugs.launchpad.net/bugs/1545811

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  ibus-daemon crashed with SIGABRT

Status in ibus package in Ubuntu:
  New

Bug description:
  I have this error message via making each boot of Ubuntu.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: ibus 1.5.19-1ubuntu1
  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-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 10 23:11:06 2019
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2018-04-29 (261 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180421.1)
  ProcCmdline: ibus-daemon --xim --panel disable
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1591772] Re: clicking on a file or folder on the file picker sets mouse in drag mode

2019-01-16 Thread Paul White
Bug did not expire due bug watch
Upstream report showing "RESOLVED FIXED" on 2018-03-01
No reply for further information so closing


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

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

Title:
  clicking on a file or folder on the file picker sets mouse in drag
  mode

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  After a recent Firefox update, clicking on a file or folder on the gtk
  file picker window sets the mouse in drag mode.

  This is exactly the same problem reported here:

  
https://m.reddit.com/r/linuxquestions/comments/4njk9g/why_is_my_firefox_gtk_file_dialog_acting_like/

  Firefox 47 on Ubuntu 14.04 with KDE.

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

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


[Desktop-packages] [Bug 583122] Re: firefox occasionally highlights contents of form fields while typing thereby overwriting previously entered keystrokes

2019-01-16 Thread Paul White
Bug did not expire due bug watch
No comments from anyone affected since 2011 so closing
No reply to comment #39


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

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

Title:
  firefox occasionally highlights contents of form fields while typing
  thereby overwriting previously entered keystrokes

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

Bug description:
  Binary package hint: firefox

  On occasion while typing into a form field in firefox (search field,
  url field, webpage form field), after typing a few characters, the
  browser will automatically highlight the previously entered
  characters, causing my subsequently entered keystrokes to overwrite
  the previously entered keystrokes.  I cannot reproduce this behavior
  reliably, though it does happen quite often.  There are various
  methods that I have used to make the problem go away, though none work
  reliably.  These include closing the tab, hitting enter to cause a
  pageload, restarting the browser.

  I am using Ubuntu 10.04.  This problem was not present in Ubuntu 9.10
  on the same hardware.  The firefox package version is 3.6.3+nobinonly-
  0ubuntu4.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  Architecture: amd64
  CheckboxSubmission: e8b67d75e6dc3e68647d9c34878edc73
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Wed May 19 20:21:20 2010
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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


[Desktop-packages] [Bug 1779615] Re: Shell text and some icons have sharp edges during zoom

2019-01-16 Thread Treviño
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Shell text and some icons have sharp edges during zoom

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Shell text and some icons have sharp edges during zoom. Screenshot
  attached.

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

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

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


[Desktop-packages] [Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt

2019-01-16 Thread Treviño
** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell assert failure: double free or corruption (fasttop) in
  g_free() from g_error_free() from cogl_error_free() from
  cogl_texture_new_with_size() from
  clutter_offscreen_effect_real_create_texture()

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Problem is occurring if dual monitor is used. Second monitor is
  repeatingly blank and activated again. At the bottom it probably
  contains the upper part of the first monitor. I had the same problem
  at 18.04 when using gdm3 without wayland during logon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic i686
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: i386
  AssertionMessage: double free or corruption (fasttop)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  3 21:02:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_signal_restore_set (set=0xbfcd5e9c) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
   __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
   __GI_abort () at abort.c:79
   __libc_message (action=do_abort, fmt=) at 
../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption 
(fasttop)") at malloc.c:5350
  Title: gnome-shell assert failure: double free or corruption (fasttop)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_text

2019-01-16 Thread Treviño
** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in
  cogl_texture_get_height(texture=0x0) from
  clutter_offscreen_effect_real_paint_target() from
  clutter_offscreen_effect_paint_texture() from
  clutter_offscreen_effect_paint() from clutter_actor_continue_paint()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress

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

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

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


[Desktop-packages] [Bug 1214846] Re: Restart button starts wrong profile when running multiple

2019-01-16 Thread Paul White
Bug did not expire due bug watch
Upstream report is still open but not confirmed
No reply from reporter
So closing as no-one else affected

@era, please feel free to re-open if problem seen again

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

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

Title:
  Restart button starts wrong profile when running multiple

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I have two instances of Firefox running with different extensions,
  different default window size, different preferences, etc.

  I have found that when Firefox requires a restart (such as when the
  Ubuntu Firefox package receives an upgrade, or when I have installed
  an extension which requires it), the "Restart" button does not work
  correctly in the secondary instance.  Instead, it will close the
  secondary instance, and start a new empty window in the primary
  instance.

  Steps to repro:

  1. Run your regular Firefox
  2. Start a second Firefox by running

  firefox -ufnord -profileManager &

  Create a new profile, populate it with some settings to distinguish it
  from your primary instance (window size? web developer tools?
  experimental extensions?)

  3. Receive an uprade to Firefox, or install an extension which
  requires a reboot.  For the latter case, I found that e.g.
  https://addons.mozilla.org/en-us/firefox/addon/hide-tab-bar-with-one-
  tab/ does that.

  4. When Firefox displays a Restart button at the top of your browser
  window, press it

  Expected outcome:

  The secondary instance closes, then restarts with the same settings
  (same profile)

  Actual outcome:

  A new empty window in the primary instance is spawned.

  Workaround:

  Run firefox -ufnord -profileManager & again and select the profile you
  want.

  (The -ufnord is a known bug; I'm too lazy to dig it up, but it's been
  there like forever.)

  xvbvntv$ lsb_release -rd
  Description:Ubuntu 12.04.3 LTS
  Release:12.04

  xvbvntv$ apt-cache policy firefox
  firefox:
Installed: 23.0+build2-0ubuntu0.12.04.1
Candidate: 23.0+build2-0ubuntu0.12.04.1
Version table:
   *** 23.0+build2-0ubuntu0.12.04.1 0
  500 http://fi.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
  500 http://mirrors.nic.funet.fi/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   11.0+build1-0ubuntu4 0
  500 http://fi.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

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

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


[Desktop-packages] [Bug 340668] Re: bug opening a new shell tab

2019-01-16 Thread Paul White
Bug did not expire due assignment
Report almost 10 years old and refers to GNOME 2


** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  bug opening a new shell tab

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-terminal

  There is a bug when opening a new tab if the old tab is in the last line of 
the display.
  The following steps reproduce the bug:

  1. Open a shell and ping www.google.com (for example)
  2. Let it run until the output fills the display
  3. Open a new tab and do something (hit enter, for example)
  4. Return to the old tab, there will be a few lines missing in the output.

  The attached screenshot shows the output of this experiment, note that
  the output lines for  icmp_seq=22 and 23 are missing.

  I'm using Ubuntu 8.10.

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/gnome-terminal
  NonfreeKernelModules: nvidia
  Package: gnome-terminal 2.24.1.1-0ubuntu1
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  Uname: Linux 2.6.27-7-generic x86_64

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

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


[Desktop-packages] [Bug 1441474] Re: gnome-keyring-daemon uses a lot of memory

2019-01-16 Thread James Niland
This is for Ubuntu-gnome
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
that also uses gnome shell although I am not sure why as it seems it does not 
work either
Both Opera browser and any version of Chrome or google-chrome demand it. 
However at start just below gnome-panel it is the second highest use of memory 
at startup. Currently sitting at over 32Mb real and 384 virtual memory. There 
is only one login is [Passwords and Keys]. Others seem unhappy with 1mb of ram, 
I however wish I could get it this low.
/usr/bin/gnome-keyring-daemon --daemonize --login is the command loaded.
Version gnome-keyring 3.10.1-1ubuntu4.3
Killing the process my system is entirely more responsive

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

Title:
  gnome-keyring-daemon uses a lot of memory

Status in Linux Mint:
  New
Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) The version and edition of Linux Mint and version of gnome-keyring:

  $ cat /etc/lsb-release
  DISTRIB_ID=LinuxMint
  DISTRIB_RELEASE=17.1
  DISTRIB_CODENAME=rebecca
  DISTRIB_DESCRIPTION="Linux Mint 17.1 Rebecca"

  $ cinnamon --version
  Cinnamon 2.4.7

  $ dpkg -l gnome-keyring   
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  gnome-keyring  3.10.1-1ubun amd64GNOME keyring services (daemon an

  2) How to reproduce it.

  Start one or more gnome-terminal sessions connected to remote server
  by ssh and leave them open for at least half an hour or more, e.g.
  snippet from pstree:

  |-gnome-terminal(404)-+-bash(463)
  | |-bash(4195)
  | |-bash(14698)---ssh(14759)
  | |-bash(16908)
  | |-bash(18025)
  | |-bash(19604)
  | |-bash(20717)---man(20779)---pager(20795)
  | |-bash(23307)
  | |-bash(23607)-+-less(24019)
  | | `-pstree(24018)

  
  3) The result in an hour or more is gnome-kerying-daemon process is using 
almost 1/6 of all of the host memory:

  $ ps -p 32051 -o pcpu,pmem,pid,comm
  %CPU %MEM   PID COMMAND
   1.1 15.8 32051 gnome-keyring-d

  $ cat /proc/32051/cmdline 
  /usr/bin/gnome-keyring-daemon--daemonize--login

  If freshly started it is using not more than 1MB or less.

  4) The expected is to leave the session for days at a time without any
  need for gnome-keyring-daemon to be restarted.

  5) The problem is reproducible always, just have to leave some
  terminals open for some time.

  Some remarks:
  - Tried to reproduce similar behaviour with Ubuntu 14.04 and 14.10 without 
success.
  - The same issue was reproducible also in Linux Mint 17 Qiana. In fact the 
host was upgraded from Quiana to Rebecca some months ago.
  - Logging out and log-in back resolves the issue as the keyring daemon is 
restarted.
  - Attempting to restart just the process results in:
  /usr/bin/gnome-keyring-daemon -r --daemonize
  ** Message: couldn't communicate with already running 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.
  ** Message: Replacing daemon, using directory: /run/user/1000/keyring-PQyeQe
  GNOME_KEYRING_CONTROL=/run/user/1000/keyring-PQyeQe
  SSH_AUTH_SOCK=/run/user/1000/keyring-PQyeQe/ssh
  GPG_AGENT_INFO=/run/user/1000/keyring-PQyeQe/gpg:0:1
  GNOME_KEYRING_PID=28477

  Password unlock prompt opens for every gnome-terminal window or
  session opened.

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

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


[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze

2019-01-16 Thread Dilip
As suggested by @Daniel, I have removed all extensions and been using
default Ubuntu DE all day. Sadly, the keyboard freeze is annoyingly
present in default Ubuntu session as well.The workaround fixes the issue
as discussed before.

PS : I also removed the Yaru install through Ubuntu Software to make
sure that it is not interfering. The freeze is still there, but much
less annoying than in the Yaru session.

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

Title:
  Occasional Keyboard freeze

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/907

  ---

  I am using 18.04 and sometimes, whatever I type does not work. It is
  as if there is no keyboard connected while I have my laptop keyboard
  and an external keyboard connected to the machine. I even enabled On
  Screen Keyboard and tried to type through it. Same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Dec  6 05:41:04 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Fusion
ps. there is a catch. Since my previous comment I am trying to reproduce
the error. In the beginning it asks password no matter what. After that
I tried this: "gsettings set org.gnome.desktop.screensaver ubuntu-lock-
on-suspend false" that I found it here:
"https://askubuntu.com/questions/1029696/disable-password-request-from-
from-suspend-18-04". So the password is gone again. But I test it
without addons installed (as in the first place (with the photo of my
screen I sent above) and with the two addons I use (Advanced Volume
Mixer by Hatell and GSConnect by andyholmes). The problem seems not to
be reproducible. Although today morning as the day before, it was there.
I suspend and resume over 10 times now, and it seems to be ok. I will
try to let it more on stand by and let you know (I cannot understand the
causes - like no logic at all).

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

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  my system:
  ubuntu 18.10
  4k monitor with 1 scale and 1.5 font scale
  nvidia 410 and 390 drivers are checked

  when happened:
  lock screen or suspend. return after that.
  if I have user password prompt enabled: everything ok
  if I haven't user password prompt enabled, system started with gnome crashed

  I expect:
  ubuntu to has the same behaviour either I have a password either not.

  What happened:
  in case of no password (I should just 'swipe up' or press 'space' and 
everything should be ready.. but) most of the times I can not return to desktop.
  - freezes on a screen with panels but no desktop
  - freezes on a purple screen that no command is working (as ctrl+alt+t)
  - freezes on a useless gnome panels (dash and topbar) mode

  solution chosen:
  I press ctrl+alt+F1 to change environment, I enter my password... BUT again 
the gnome is too slow, app icon is always on and everything is acting weird 
(some apps' icon that I have opened on the other session is liked pined on dash 
without have the option to unpin it - like I see it but it is not pinned)
  So, I just save what I can through the new session and just restart the pc 
(in new session is available - in the previous is only suspend available)

  frequency: about 80% of the times. If lock-screen showed up normally
  (and I have to press space to unlock) everything works like a charm
  afterwards. If not.. it will be the mess I described above

  hope it helps
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-08-28 (84 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (32 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Josh Holland
** Attachment added: "Output of `lscpu`"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229622/+files/lscpu

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

Title:
  Tearing and/or flickering when using Intel graphics

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

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

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


[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Josh Holland
** Attachment added: "Output of `lspci -k`"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229624/+files/lspci

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

Title:
  Tearing and/or flickering when using Intel graphics

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

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

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


[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Josh Holland
Removing gstreamer1.0-vaapi doesn't appear to help.

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

Title:
  Tearing and/or flickering when using Intel graphics

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

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

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


[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

2019-01-16 Thread Josh Holland
** Attachment added: "Output of `vainfo`"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229623/+files/vainfo

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

Title:
  Tearing and/or flickering when using Intel graphics

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  When using Intel graphics on my hybrid Nvidia laptop, videos in Totem
  have awful tearing/flickering which makes them essentially
  unwatchable.

  With default X settings, I get tearing across the top of the screen
  (but I also get very noticeable tearing in other applications); if I
  enable TearFree (which eliminates tearing in Chrome), the tearing
  turns into jagged black flickers which extend from the top of the
  screen right down to near the bottom of the screen on some frames.

  The flickers are visible in screenshots, so I have attached one.

  Ubuntu version: Ubuntu 18.04.1
  Totem version: 3.26.0-0ubuntu6.1

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

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


[Desktop-packages] [Bug 1726688] Re: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works

2019-01-16 Thread Robie Basak
Accepting, but "there isn't really any regression risk here" isn't OK as
documented at https://wiki.ubuntu.com/StableReleaseUpdates - see "It's
just a one-line change!" and the documentation of this entry in the
Procedure section. Please could you fix this?

For example, what if this SRU inadvertently breaks
data/org.gnome.Totem.desktop.in.in somehow (eg. a syntax error that
we've missed)? Or if we trigger some latent bug by expanding src/totem-
menu.c:app_entries? During SRU verification, can we make sure that the
existing functionality being modified here still works?

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

** Tags added: verification-needed verification-needed-bionic

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

Status in totem package in Ubuntu:
  Fix Released
Status in totem source package in Bionic:
  Fix Committed
Status in totem source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  --
  None of the extra Desktop Actions for the Videos app (Totem) work

  Test Case
  -
  1. Install the update.
  2. You might need to log out and log back in.
  3. Open the Videos app
  4. Click the + button.
  5. Navigate to /usr/share/example-content/ and both media files
  6. After adding the files, click the Check button at the top of the app.
 Select both videos and click Play. (This adds both videos to the current
 playlist.)
  7. Play a video
  8. Right-click on the videos icon in the Ubuntu Dock. Make sure that the 5 
actions starting at Play/Pause and ending at Fullscreen work.

  Regression Potential
  ---
  Since none of the actions worked before and the changes are minimal, there 
isn't really any regression risk here.

  Original Bug Report
  ---
  totem media player in the Ubuntu dock right click menu does not work, rewind 
does not work, nor full screen works.

  I'm completely aware that there is a similar bug report of Ubuntu DBUS
  PlayPause() Function. However it is no longer just Play and Pause
  anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:22:01 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen

2019-01-16 Thread MN
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

effects me either :/ the dock is visible, and extensions are not re-
enabled after login...

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

Title:
  Icon dock visible on lock screen

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When locking the machine with alt-L the icon dock is still visible.

  After Login, the dock does not get adjusted to the top menu.

  In rare cases, the dock does not respond any more. This requires a
  reboot of the machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: mutter 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 12:59:27 2018
  InstallationDate: Installed on 2018-04-30 (176 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions

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


[Desktop-packages] [Bug 1726688] Please test proposed package

2019-01-16 Thread Robie Basak
Hello David, or anyone else affected,

Accepted totem into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/totem/3.26.2-1ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

Status in totem package in Ubuntu:
  Fix Released
Status in totem source package in Bionic:
  Fix Committed
Status in totem source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  --
  None of the extra Desktop Actions for the Videos app (Totem) work

  Test Case
  -
  1. Install the update.
  2. You might need to log out and log back in.
  3. Open the Videos app
  4. Click the + button.
  5. Navigate to /usr/share/example-content/ and both media files
  6. After adding the files, click the Check button at the top of the app.
 Select both videos and click Play. (This adds both videos to the current
 playlist.)
  7. Play a video
  8. Right-click on the videos icon in the Ubuntu Dock. Make sure that the 5 
actions starting at Play/Pause and ending at Fullscreen work.

  Regression Potential
  ---
  Since none of the actions worked before and the changes are minimal, there 
isn't really any regression risk here.

  Original Bug Report
  ---
  totem media player in the Ubuntu dock right click menu does not work, rewind 
does not work, nor full screen works.

  I'm completely aware that there is a similar bug report of Ubuntu DBUS
  PlayPause() Function. However it is no longer just Play and Pause
  anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:22:01 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1726688] Please test proposed package

2019-01-16 Thread Robie Basak
Hello David, or anyone else affected,

Accepted totem into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/totem/3.26.0-0ubuntu6.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed-cosmic

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

Status in totem package in Ubuntu:
  Fix Released
Status in totem source package in Bionic:
  Fix Committed
Status in totem source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  --
  None of the extra Desktop Actions for the Videos app (Totem) work

  Test Case
  -
  1. Install the update.
  2. You might need to log out and log back in.
  3. Open the Videos app
  4. Click the + button.
  5. Navigate to /usr/share/example-content/ and both media files
  6. After adding the files, click the Check button at the top of the app.
 Select both videos and click Play. (This adds both videos to the current
 playlist.)
  7. Play a video
  8. Right-click on the videos icon in the Ubuntu Dock. Make sure that the 5 
actions starting at Play/Pause and ending at Fullscreen work.

  Regression Potential
  ---
  Since none of the actions worked before and the changes are minimal, there 
isn't really any regression risk here.

  Original Bug Report
  ---
  totem media player in the Ubuntu dock right click menu does not work, rewind 
does not work, nor full screen works.

  I'm completely aware that there is a similar bug report of Ubuntu DBUS
  PlayPause() Function. However it is no longer just Play and Pause
  anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:22:01 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency

2019-01-16 Thread Dan Candeto
Persists on a freshly reinstalled system.

Output from ping -i6 [host] follows.  Note the spike in ping time and
high packet loss.

64 bytes from [host]: icmp_seq=3833 ttl=64 time=0.223 ms
64 bytes from [host]: icmp_seq=3834 ttl=64 time=0.212 ms
64 bytes from [host]: icmp_seq=3835 ttl=64 time=0.156 ms
64 bytes from [host]: icmp_seq=3836 ttl=64 time=0.347 ms
64 bytes from [host]: icmp_seq=3837 ttl=64 time=0.216 ms
64 bytes from [host]: icmp_seq=3838 ttl=64 time=0.316 ms
64 bytes from [host]: icmp_seq=3839 ttl=64 time=0.320 ms
64 bytes from [host]: icmp_seq=3840 ttl=64 time=0.168 ms
64 bytes from [host]: icmp_seq=3841 ttl=64 time=336 ms
64 bytes from [host]: icmp_seq=3843 ttl=64 time=216 ms
64 bytes from [host]: icmp_seq=3845 ttl=64 time=515 ms
64 bytes from [host]: icmp_seq=3846 ttl=64 time=423 ms
64 bytes from [host]: icmp_seq=3847 ttl=64 time=498 ms
64 bytes from [host]: icmp_seq=3849 ttl=64 time=569 ms
64 bytes from [host]: icmp_seq=3851 ttl=64 time=532 ms
64 bytes from [host]: icmp_seq=3853 ttl=64 time=496 ms
64 bytes from [host]: icmp_seq=3855 ttl=64 time=502 ms
64 bytes from [host]: icmp_seq=3857 ttl=64 time=424 ms
64 bytes from [host]: icmp_seq=3859 ttl=64 time=346 ms
64 bytes from [host]: icmp_seq=3861 ttl=64 time=352 ms
64 bytes from [host]: icmp_seq=3863 ttl=64 time=358 ms
64 bytes from [host]: icmp_seq=3865 ttl=64 time=573 ms
64 bytes from [host]: icmp_seq=3867 ttl=64 time=495 ms
64 bytes from [host]: icmp_seq=3869 ttl=64 time=627 ms
64 bytes from [host]: icmp_seq=3871 ttl=64 time=465 ms
64 bytes from [host]: icmp_seq=3873 ttl=64 time=261 ms
64 bytes from [host]: icmp_seq=3875 ttl=64 time=518 ms
64 bytes from [host]: icmp_seq=3877 ttl=64 time=440 ms
64 bytes from [host]: icmp_seq=3879 ttl=64 time=400 ms
64 bytes from [host]: icmp_seq=3881 ttl=64 time=410 ms
64 bytes from [host]: icmp_seq=3883 ttl=64 time=542 ms
64 bytes from [host]: icmp_seq=3885 ttl=64 time=338 ms
64 bytes from [host]: icmp_seq=3887 ttl=64 time=511 ms
64 bytes from [host]: icmp_seq=3889 ttl=64 time=475 ms
64 bytes from [host]: icmp_seq=3891 ttl=64 time=230 ms
64 bytes from [host]: icmp_seq=3893 ttl=64 time=571 ms
64 bytes from [host]: icmp_seq=3894 ttl=64 time=564 ms
64 bytes from [host]: icmp_seq=3896 ttl=64 time=598 ms
64 bytes from [host]: icmp_seq=3898 ttl=64 time=604 ms
64 bytes from [host]: icmp_seq=3900 ttl=64 time=317 ms
64 bytes from [host]: icmp_seq=3902 ttl=64 time=239 ms
64 bytes from [host]: icmp_seq=3904 ttl=64 time=538 ms
64 bytes from [host]: icmp_seq=3906 ttl=64 time=795 ms
64 bytes from [host]: icmp_seq=3907 ttl=64 time=453 ms
64 bytes from [host]: icmp_seq=3909 ttl=64 time=571 ms
64 bytes from [host]: icmp_seq=3911 ttl=64 time=535 ms
64 bytes from [host]: icmp_seq=3913 ttl=64 time=373 ms
64 bytes from [host]: icmp_seq=3915 ttl=64 time=463 ms
64 bytes from [host]: icmp_seq=3917 ttl=64 time=385 ms
64 bytes from [host]: icmp_seq=3919 ttl=64 time=265 ms
64 bytes from [host]: icmp_seq=3921 ttl=64 time=564 ms
64 bytes from [host]: icmp_seq=3923 ttl=64 time=444 ms
64 bytes from [host]: icmp_seq=3925 ttl=64 time=367 ms
64 bytes from [host]: icmp_seq=3927 ttl=64 time=0.123 ms
64 bytes from [host]: icmp_seq=3928 ttl=64 time=0.284 ms
64 bytes from [host]: icmp_seq=3929 ttl=64 time=0.239 ms
64 bytes from [host]: icmp_seq=3930 ttl=64 time=0.214 ms
64 bytes from [host]: icmp_seq=3931 ttl=64 time=0.280 ms
64 bytes from [host]: icmp_seq=3932 ttl=64 time=0.314 ms
64 bytes from [host]: icmp_seq=3933 ttl=64 time=0.318 ms
64 bytes from [host]: icmp_seq=3934 ttl=64 time=0.318 ms
64 bytes from [host]: icmp_seq=3935 ttl=64 time=0.312 ms
64 bytes from [host]: icmp_seq=3936 ttl=64 time=0.218 ms
64 bytes from [host]: icmp_seq=3937 ttl=64 time=0.221 ms
64 bytes from [host]: icmp_seq=3938 ttl=64 time=0.308 ms
64 bytes from [host]: icmp_seq=3939 ttl=64 time=0.329 ms
64 bytes from [host]: icmp_seq=3940 ttl=64 time=0.244 ms
64 bytes from [host]: icmp_seq=3941 ttl=64 time=0.235 ms
64 bytes from [host]: icmp_seq=3942 ttl=64 time=0.250 ms
64 bytes from [host]: icmp_seq=3943 ttl=64 time=0.309 ms
64 bytes from [host]: icmp_seq=3944 ttl=64 time=0.132 ms
64 bytes from [host]: icmp_seq=3945 ttl=64 time=0.228 ms
64 bytes from [host]: icmp_seq=3946 ttl=64 time=0.223 ms
64 bytes from [host]: icmp_seq=3947 ttl=64 time=0.202 ms
64 bytes from [host]: icmp_seq=3948 ttl=64 time=0.211 ms
64 bytes from [host]: icmp_seq=3949 ttl=64 time=0.245 ms
64 bytes from [host]: icmp_seq=3950 ttl=64 time=0.248 ms
64 bytes from [host]: icmp_seq=3951 ttl=64 time=0.186 ms
64 bytes from [host]: icmp_seq=3952 ttl=64 time=0.192 ms
64 bytes from [host]: icmp_seq=3953 ttl=64 time=0.321 ms
64 bytes from [host]: icmp_seq=3954 ttl=64 time=0.231 ms
64 bytes from [host]: icmp_seq=3955 ttl=64 time=0.309 ms
64 bytes from [host]: icmp_seq=3956 ttl=64 time=0.307 ms
64 bytes from [host]: icmp_seq=3957 ttl=64 time=0.154 ms
64 bytes from [host]: icmp_seq=3958 ttl=64 time=0.189 ms
64 bytes from [host]: icmp_seq=3959 ttl=64 time=0.303 ms
64 bytes from [host]: icmp_seq=3960 ttl=64 time=0.197 m

[Desktop-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2019-01-16 Thread Dan Candeto
Persists on a freshly reinstalled system.

Output from ping -i6 [host] follows.  Note the spike in ping time and
high packet loss.

64 bytes from [host]: icmp_seq=3833 ttl=64 time=0.223 ms
64 bytes from [host]: icmp_seq=3834 ttl=64 time=0.212 ms
64 bytes from [host]: icmp_seq=3835 ttl=64 time=0.156 ms
64 bytes from [host]: icmp_seq=3836 ttl=64 time=0.347 ms
64 bytes from [host]: icmp_seq=3837 ttl=64 time=0.216 ms
64 bytes from [host]: icmp_seq=3838 ttl=64 time=0.316 ms
64 bytes from [host]: icmp_seq=3839 ttl=64 time=0.320 ms
64 bytes from [host]: icmp_seq=3840 ttl=64 time=0.168 ms
64 bytes from [host]: icmp_seq=3841 ttl=64 time=336 ms
64 bytes from [host]: icmp_seq=3843 ttl=64 time=216 ms
64 bytes from [host]: icmp_seq=3845 ttl=64 time=515 ms
64 bytes from [host]: icmp_seq=3846 ttl=64 time=423 ms
64 bytes from [host]: icmp_seq=3847 ttl=64 time=498 ms
64 bytes from [host]: icmp_seq=3849 ttl=64 time=569 ms
64 bytes from [host]: icmp_seq=3851 ttl=64 time=532 ms
64 bytes from [host]: icmp_seq=3853 ttl=64 time=496 ms
64 bytes from [host]: icmp_seq=3855 ttl=64 time=502 ms
64 bytes from [host]: icmp_seq=3857 ttl=64 time=424 ms
64 bytes from [host]: icmp_seq=3859 ttl=64 time=346 ms
64 bytes from [host]: icmp_seq=3861 ttl=64 time=352 ms
64 bytes from [host]: icmp_seq=3863 ttl=64 time=358 ms
64 bytes from [host]: icmp_seq=3865 ttl=64 time=573 ms
64 bytes from [host]: icmp_seq=3867 ttl=64 time=495 ms
64 bytes from [host]: icmp_seq=3869 ttl=64 time=627 ms
64 bytes from [host]: icmp_seq=3871 ttl=64 time=465 ms
64 bytes from [host]: icmp_seq=3873 ttl=64 time=261 ms
64 bytes from [host]: icmp_seq=3875 ttl=64 time=518 ms
64 bytes from [host]: icmp_seq=3877 ttl=64 time=440 ms
64 bytes from [host]: icmp_seq=3879 ttl=64 time=400 ms
64 bytes from [host]: icmp_seq=3881 ttl=64 time=410 ms
64 bytes from [host]: icmp_seq=3883 ttl=64 time=542 ms
64 bytes from [host]: icmp_seq=3885 ttl=64 time=338 ms
64 bytes from [host]: icmp_seq=3887 ttl=64 time=511 ms
64 bytes from [host]: icmp_seq=3889 ttl=64 time=475 ms
64 bytes from [host]: icmp_seq=3891 ttl=64 time=230 ms
64 bytes from [host]: icmp_seq=3893 ttl=64 time=571 ms
64 bytes from [host]: icmp_seq=3894 ttl=64 time=564 ms
64 bytes from [host]: icmp_seq=3896 ttl=64 time=598 ms
64 bytes from [host]: icmp_seq=3898 ttl=64 time=604 ms
64 bytes from [host]: icmp_seq=3900 ttl=64 time=317 ms
64 bytes from [host]: icmp_seq=3902 ttl=64 time=239 ms
64 bytes from [host]: icmp_seq=3904 ttl=64 time=538 ms
64 bytes from [host]: icmp_seq=3906 ttl=64 time=795 ms
64 bytes from [host]: icmp_seq=3907 ttl=64 time=453 ms
64 bytes from [host]: icmp_seq=3909 ttl=64 time=571 ms
64 bytes from [host]: icmp_seq=3911 ttl=64 time=535 ms
64 bytes from [host]: icmp_seq=3913 ttl=64 time=373 ms
64 bytes from [host]: icmp_seq=3915 ttl=64 time=463 ms
64 bytes from [host]: icmp_seq=3917 ttl=64 time=385 ms
64 bytes from [host]: icmp_seq=3919 ttl=64 time=265 ms
64 bytes from [host]: icmp_seq=3921 ttl=64 time=564 ms
64 bytes from [host]: icmp_seq=3923 ttl=64 time=444 ms
64 bytes from [host]: icmp_seq=3925 ttl=64 time=367 ms
64 bytes from [host]: icmp_seq=3927 ttl=64 time=0.123 ms
64 bytes from [host]: icmp_seq=3928 ttl=64 time=0.284 ms
64 bytes from [host]: icmp_seq=3929 ttl=64 time=0.239 ms
64 bytes from [host]: icmp_seq=3930 ttl=64 time=0.214 ms
64 bytes from [host]: icmp_seq=3931 ttl=64 time=0.280 ms
64 bytes from [host]: icmp_seq=3932 ttl=64 time=0.314 ms
64 bytes from [host]: icmp_seq=3933 ttl=64 time=0.318 ms
64 bytes from [host]: icmp_seq=3934 ttl=64 time=0.318 ms
64 bytes from [host]: icmp_seq=3935 ttl=64 time=0.312 ms
64 bytes from [host]: icmp_seq=3936 ttl=64 time=0.218 ms
64 bytes from [host]: icmp_seq=3937 ttl=64 time=0.221 ms
64 bytes from [host]: icmp_seq=3938 ttl=64 time=0.308 ms
64 bytes from [host]: icmp_seq=3939 ttl=64 time=0.329 ms
64 bytes from [host]: icmp_seq=3940 ttl=64 time=0.244 ms
64 bytes from [host]: icmp_seq=3941 ttl=64 time=0.235 ms
64 bytes from [host]: icmp_seq=3942 ttl=64 time=0.250 ms
64 bytes from [host]: icmp_seq=3943 ttl=64 time=0.309 ms
64 bytes from [host]: icmp_seq=3944 ttl=64 time=0.132 ms
64 bytes from [host]: icmp_seq=3945 ttl=64 time=0.228 ms
64 bytes from [host]: icmp_seq=3946 ttl=64 time=0.223 ms
64 bytes from [host]: icmp_seq=3947 ttl=64 time=0.202 ms
64 bytes from [host]: icmp_seq=3948 ttl=64 time=0.211 ms
64 bytes from [host]: icmp_seq=3949 ttl=64 time=0.245 ms
64 bytes from [host]: icmp_seq=3950 ttl=64 time=0.248 ms
64 bytes from [host]: icmp_seq=3951 ttl=64 time=0.186 ms
64 bytes from [host]: icmp_seq=3952 ttl=64 time=0.192 ms
64 bytes from [host]: icmp_seq=3953 ttl=64 time=0.321 ms
64 bytes from [host]: icmp_seq=3954 ttl=64 time=0.231 ms
64 bytes from [host]: icmp_seq=3955 ttl=64 time=0.309 ms
64 bytes from [host]: icmp_seq=3956 ttl=64 time=0.307 ms
64 bytes from [host]: icmp_seq=3957 ttl=64 time=0.154 ms
64 bytes from [host]: icmp_seq=3958 ttl=64 time=0.189 ms
64 bytes from [host]: icmp_seq=3959 ttl=64 time=0.303 ms
64 bytes from [host]: icmp_seq=3960 ttl=64 time=0.197 m

[Desktop-packages] [Bug 1726688] Re: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works

2019-01-16 Thread Jeremy Bicha
Yes, verifying the SRU requires verifying that the .desktop works and
that the Actions work.

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

Status in totem package in Ubuntu:
  Fix Released
Status in totem source package in Bionic:
  Fix Committed
Status in totem source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  --
  None of the extra Desktop Actions for the Videos app (Totem) work

  Test Case
  -
  1. Install the update.
  2. You might need to log out and log back in.
  3. Open the Videos app
  4. Click the + button.
  5. Navigate to /usr/share/example-content/ and both media files
  6. After adding the files, click the Check button at the top of the app.
 Select both videos and click Play. (This adds both videos to the current
 playlist.)
  7. Play a video
  8. Right-click on the videos icon in the Ubuntu Dock. Make sure that the 5 
actions starting at Play/Pause and ending at Fullscreen work.

  Regression Potential
  ---
  Since none of the actions worked before and the changes are minimal, there 
isn't really any regression risk here.

  Original Bug Report
  ---
  totem media player in the Ubuntu dock right click menu does not work, rewind 
does not work, nor full screen works.

  I'm completely aware that there is a similar bug report of Ubuntu DBUS
  PlayPause() Function. However it is no longer just Play and Pause
  anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:22:01 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1803021] Re: No tutorials

2019-01-16 Thread Mattia Rizzolo
They are in the separate inkscape-tutorials package, please install that
and it will work.  See LP: #238276

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

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

Title:
  No tutorials

Status in inkscape package in Ubuntu:
  Invalid

Bug description:
  When selecting `Help -> Tutorials` the error message is shown and no
  tutorial is loaded.

  Failed to load the requested file /usr/share/inkscape/tutorials
  /tutorial-basic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: inkscape 0.92.3-4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Nov 13 05:18:54 2018
  InstallationDate: Installed on 2018-11-01 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 239669] Re: Inkscape saves imported images from openclipart to /tmp

2019-01-16 Thread Mattia Rizzolo
as such, I'm marking it as fixed also in ubuntu.

** Changed in: inkscape (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Inkscape saves imported images from openclipart to /tmp

Status in Inkscape:
  Fix Released
Status in inkscape package in Ubuntu:
  Fix Released
Status in inkscape package in Debian:
  Confirmed

Bug description:
  Hello to all!!!

  I have created a design and I have imported a clipart from openclipart.
  I have done some work and the next day I have reopened it.

  But in the place of all the openclipart, there's a "Linked image not
  found"

  I have inspectioned more this and the problem is that inkscape save the 
imported images
  by default in /tmp (i'm on ubuntu linux)
  and the path to this images point to /tmp also
  and when the system is restarted, on linux /tmp is cleared.

  And when I click search, for each click is imported and created an
  image in /tmp

  see for example the attached image, i have clicked on horse cuissard, horse 
and man, horse (lego)
  and then restarted with horse cuissard and on the left is my /tmp folder

  I think that import from openclipart should ask where to put all imported 
clipart
  (maybe in ~/.inkscape/clipart/myclipart or better in the same folder as .svg 
file)
  or incorporate the image in the .svg file
  (in this manner if I need to send the file to another person he/she don't 
lost all
  the imported clipart.

  Thanks for your work!!

  Nicola Lunghi

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

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


[Desktop-packages] [Bug 1811988] [NEW] Please add Provides: lightning

2019-01-16 Thread Jeremy Bicha
Public bug reported:

Please add Provides: lightning to the debian/control metadata for xul-
ext-lightning.

Debian's package is named lightning and that would help compatibility.

For instance, see https://bugs.debian.org/914615 (there are 2 other
related packages with the same problem).

** Affects: thunderbird (Ubuntu)
 Importance: Low
 Status: New

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

Title:
  Please add Provides: lightning

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Please add Provides: lightning to the debian/control metadata for xul-
  ext-lightning.

  Debian's package is named lightning and that would help compatibility.

  For instance, see https://bugs.debian.org/914615 (there are 2 other
  related packages with the same problem).

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

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


[Desktop-packages] [Bug 1514161] Re: address book search view makes full show after delete

2019-01-16 Thread Paul White
Reported upstream as I can confirm this with Thunderbird 60.2.1

** Bug watch added: Mozilla Bugzilla #1520450
   https://bugzilla.mozilla.org/show_bug.cgi?id=1520450

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1520450
   Importance: Unknown
   Status: Unknown

** Tags removed: vivid

** Summary changed:

- address book search view makes full show after delete
+ Address Book search loses filter when multiple entries found and one is 
deleted

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

Title:
  Address Book search loses filter when multiple entries found and one
  is deleted

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  just an annoyance: imagine you want to delete an email from all the
  address books. you click on the top item "All Address Books" and then
  enter the email into the search box. let's assume the search shows you
  several hits which all appear in the window below the search box. you
  click on the first one and you press the delete key. a dialog appears
  and you confirm the action with ok. the window, which was up until now
  showing several hits to your search, refreshes and shows you *all*
  your emails, in spite that the search box is still showing your
  selection restriction. imho, this is a contradiction. either the
  search box has to be reset to empty or the window should again show
  the corresponding selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: thunderbird 1:38.3.0+build1-0ubuntu0.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darko  1420 F pulseaudio
darko  1471 F panel-9-mixer
  BuildID: 20150930121410
  Channel: Unavailable
  Date: Sun Nov  8 10:29:05 2015
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-05-11 (545 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.137.1 dev wlan0  proto static  metric 400 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.137.0/24 dev wlan0  proto kernel  scope link  metric 400
  MostRecentCrashID: bp-0bc56969-cc4e-4ff3-89e8-8d0362150210
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=38.3.0/20150930121410
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-0bc56969-cc4e-4ff3-89e8-8d0362150210
   bp-2fa34b3f-107c-41a7-a6e8-658802141210
   bp-1f961c1a-58af-44fa-bd99-4c15a2140830
   bp-41a8c3c1-e179-4dcf-89ea-32a182120701
  UpgradeStatus: Upgraded to vivid on 2015-05-05 (186 days ago)
  WifiSyslog:
   Nov 03 02:25:31 darth NetworkManager[685]:  Policy set 'dorka' (wlan0) 
as default for IPv6 routing and DNS.
   Nov 05 08:38:03 darth kernel: psmouse serio4: TouchPad at 
isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.
   Nov 06 07:41:37 darth kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as 
advertised by 60:e7:01:34:cb:a2
   Nov 06 07:42:51 darth kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as 
advertised by 60:e7:01:34:cb:a2
   Nov 07 02:24:37 darth NetworkManager[685]:  Policy set 'dorka' (wlan0) 
as default for IPv6 routing and DNS.
  dmi.bios.date: 09/14/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PAD Ver. F.0F
  dmi.board.name: 30EC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.22
  dmi.chassis.asset.tag: CNU9400DYB
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PADVer.F.0F:bd09/14/2009:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.0F:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.22:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8730w
  dmi.product.version: F.0F
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darko  1488 F pulseaudio
  BuildID: 20180710084133
  Channel: Unavailable
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface

[Desktop-packages] [Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

2019-01-16 Thread Josh Holland
@Alberto: would you be open to adding it again? I need to enable
TearFree and select the Intel driver when using my integrated GPU (but
if I have `Driver "intel"` in my config when using the Nvidia GPU, I get
a black screen on login), so it would be nice to have a way to
automatically put a file in xorg.conf.d when switching the GPU.

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

Title:
  gpu-manager should also support using custom xorg.conf files for
  Nvidia

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released
Status in ubuntu-drivers-common source package in Zesty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Different GPUs may require different options in the xorg.conf file. Currently 
this is not possible, since the options have been hardcoded in gpu-manager to 
configure the system automatically.

  This new (backported) feature allows users to tell gpu-manager to use
  their own custom xorg.confs for their NVIDIA GPUs.

  [Test Case]
  1) Enable the xenial-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime packages.

  2) Install the nvidia driver.

  3) Place your configuration file(s) in the /usr/share/gpu-manager.d
  directory.

  If you are using a non-hybrid system, you can create the /usr/share
  /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
  specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
  /gpu-manager.d/hybrid-power-saving, depending on the power profile you
  intend to apply your settings to.

  4) Restart the system and see if it boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  5) Make sure that the /etc/X11/xorg.conf matches the file you
  specified in 3)

  [Regression Potential]
  Low, the above mentioned changes are already in Artful, and will not affect 
the system's behaviour unless new configuration files are put in the 
/usr/share/gpu-manager.d/ directory.

  __
  This feature has been implemented for Intel (ex. gpumanager_uxa), which is 
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).

  And now Nvidia also need this feature to add Option
  "nvidiaXineramaInfo" "off" to fix some issues.

  Btw, I'm thinking it might be a more flexible to have a config file
  which user could add all options as they want so that we could prevent
  keeping change gpu-manager when some more options are needed in the
  future.

  Needed by LP: #1653592

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1667198/+subscriptions

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


[Desktop-packages] [Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

2019-01-16 Thread Christian Sarrasin
Hi Daniel,

Thanks to the pointer.  I now have 3.30.1-2ubuntu1.18.10.2 and it seems
the issue is resolved (not sure if this is the new version or the manual
fix below, which I applied thanks to your pointer).

I'd installed the Pop theme manually (through apt) atop stock 18.10.
The slightly unorthodox thing I'd done was a soft-link from /usr/share
/gnome-shell/theme/Yaru/gnome-shell.css onto ../gnome-shell.css, which
is itself a soft-link to /usr/share/themes/Pop/gnome-shell/gnome-
shell.css  This would consistent theming of the lock screen, which
doesn't appear to obey the control panel setting.  Using the soft-links
also makes it easier to spot when those files get overwritten by
updates.

So it looks like the changes introduced in 3.30.1-2ubuntu1.18.10.1 makes
it impossible to follow symlinks from /usr/share/gnome-shell/theme/Yaru
/gnome-shell.css ?  I guess it's perhaps debatable whether the standard
gnome-shell package should reference a hardcoded theme (or maybe that's
a GNOME limitation?)

Anyway, since I've worked around this issue, I guess this bug can be
closed.

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

Title:
  gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR:
  Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  An upgrade to gnome-shell on 18.10 was recently released which made it
  impossible for me to log in to my DE.  Upon typing my password, the
  gdm screen would disappear, only to re-appear a few seconds later.
  This was not a password typo as I didn't get the usual msg to that
  effect (I made at least 5 attempts, carefully typing my passwd).

  I solved the issue by switching to a terminal screen (using
  CTRL+ALT+F6 I believe), logging in, analyzing recent changes through
  /var/log/apt/history.log.  Beside the gnome-shell packages, a handful
  of Wayland packages were also upgraded as follows (I use X.org so left
  those alone):

  Start-Date: 2018-12-19  09:13:20
  Commandline: aptdaemon role='role-commit-packages' sender=':1.8821'
  Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), 
keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 
2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 
3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), 
libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), 
gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), 
gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), 
libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), 
libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1)
  End-Date: 2018-12-19  09:13:31

  I solved the issue by downgrading the just-updated gnome-shell
  packages as follows:

  sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome-
  shell=3.30.1-2ubuntu1

  Having done this, I switched back to the GDM screen and managed to log
  in as normal.  I couldn't find any smoking gun in system logs but
  please let me know if there's a way to collect any useful debug info.

  One thing I'm using which differs from stock 18.10 is the System76
  "Pop" theme (let me know if you need details).  Presumably a theme
  cannot cause such issues and/or if the new version of gnome-shell is
  meant to be incompatible with themes other than Yaru, this should be
  clearly documented.

  The problematic versions are the "Candidate" shown below:

  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1.18.10.1
    Version table:
   3.30.1-2ubuntu1.18.10.1 500
  500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.1-2ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell-common:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1.18.10.1
    Version table:
   3.30.1-2ubuntu1.18.10.1 500
  500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 
Packages
   *** 3.30.1-2ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-01-16 Thread Andrei
Happens to me as well with the same error. Thought it might be related
to the Nvidia driver, but the initial reporter clearly mentions it only
started to happen after upgrading to 18.04. Have any of you guys managed
to track down the issue or find a workaround?

Thanks!

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

Title:
  Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1514161] Re: Address Book search loses filter when multiple entries found and one is deleted

2019-01-16 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1520450.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-01-16T12:45:32+00:00 Paul White wrote:

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0)
Gecko/20100101 Firefox/64.0

Steps to reproduce:

This was originally reported against Thunderbird 38 on Launchpad
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1514161

Scenario: remove an email address from all address books

To reproduce:
1) Start Address Book
2) Select "All Address Books"
3) In Search box type enough characters to match all required entries
2) Delete any of the entries found


Actual results:

Entry is deleted but the list is no longer filtered


Expected results:

Entry to be deleted and the list to remain filtered

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1514161/comments/25


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

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

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

Title:
  Address Book search loses filter when multiple entries found and one
  is deleted

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  just an annoyance: imagine you want to delete an email from all the
  address books. you click on the top item "All Address Books" and then
  enter the email into the search box. let's assume the search shows you
  several hits which all appear in the window below the search box. you
  click on the first one and you press the delete key. a dialog appears
  and you confirm the action with ok. the window, which was up until now
  showing several hits to your search, refreshes and shows you *all*
  your emails, in spite that the search box is still showing your
  selection restriction. imho, this is a contradiction. either the
  search box has to be reset to empty or the window should again show
  the corresponding selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: thunderbird 1:38.3.0+build1-0ubuntu0.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darko  1420 F pulseaudio
darko  1471 F panel-9-mixer
  BuildID: 20150930121410
  Channel: Unavailable
  Date: Sun Nov  8 10:29:05 2015
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-05-11 (545 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.137.1 dev wlan0  proto static  metric 400 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.137.0/24 dev wlan0  proto kernel  scope link  metric 400
  MostRecentCrashID: bp-0bc56969-cc4e-4ff3-89e8-8d0362150210
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=38.3.0/20150930121410
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-0bc56969-cc4e-4ff3-89e8-8d0362150210
   bp-2fa34b3f-107c-41a7-a6e8-658802141210
   bp-1f961c1a-58af-44fa-bd99-4c15a2140830
   bp-41a8c3c1-e179-4dcf-89ea-32a182120701
  UpgradeStatus: Upgraded to vivid on 2015-05-05 (186 days ago)
  WifiSyslog:
   Nov 03 02:25:31 darth NetworkManager[685]:  Policy set 'dorka' (wlan0) 
as default for IPv6 routing and DNS.
   Nov 05 08:38:03 darth kernel: psmouse serio4: TouchPad at 
isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.
   Nov 06 07:41:37 darth kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as 
advertised by 60:e7:01:34:cb:a2
   Nov 06 07:42:51 darth kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as 
advertised by 60:e7:01:34:cb:a2
   Nov 07 02:24:37 darth NetworkManager[685]:  Policy set 'dorka' (wlan0) 
as default for IPv6 routing and DNS.
  dmi.bios.date: 09/14/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PAD Ver. F.0F
  dmi.board.name: 30EC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.22
  dmi.chassis.asset.tag: CNU9400DY

[Desktop-packages] [Bug 1811999] [NEW] [USB-Audio - Audioengine D3, playback] fails after a while (a second)

2019-01-16 Thread usman
Public bug reported:

USB DAC stops playing sound after a second.
I had problem with kernel 4.15. 
So, I tried upgrading to 4.19 but still issue persists. 
I think, we might need to add it to sound/usb/quirks.c

I see following in dmesg

[ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16
[ 5955.721597] usb 1-1.4.1: new full-speed USB device number 17 using xhci_hcd
[ 5956.302910] usb 1-1.4.1: New USB device found, idVendor=2912, 
idProduct=120b, bcdDevice= 1.0c
[ 5956.302917] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 5956.302921] usb 1-1.4.1: Product: Audioengine D3
[ 5956.302926] usb 1-1.4.1: Manufacturer: Audioengine
[ 5956.302929] usb 1-1.4.1: SerialNumber: Audioengine
[ 5956.320621] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1
[ 5956.920844] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1
[ 5956.938929] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1

And lsusb -v has following entry for the device.

Bus 001 Device 017: ID 2912:120b
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x2912
  idProduct  0x120b
  bcdDevice1.0c
  iManufacturer   1
  iProduct2
  iSerial 3
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  131
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  200mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass 1 Audio
  bInterfaceSubClass  1 Control Device
  bInterfaceProtocol  0
  iInterface  0
  AudioControl Interface Descriptor:
bLength 9
bDescriptorType36
bDescriptorSubtype  1 (HEADER)
bcdADC   1.00
wTotalLength   43
bInCollection   1
baInterfaceNr( 0)   1
  AudioControl Interface Descriptor:
bLength12
bDescriptorType36
bDescriptorSubtype  2 (INPUT_TERMINAL)
bTerminalID 5
wTerminalType  0x0101 USB Streaming
bAssocTerminal  0
bNrChannels 2
wChannelConfig 0x0003
  Left Front (L)
  Right Front (R)
iChannelNames   0
iTerminal   0
  AudioControl Interface Descriptor:
bLength13
bDescriptorType36
bDescriptorSubtype  6 (FEATURE_UNIT)
bUnitID 7
bSourceID   5
bControlSize2
bmaControls( 0)  0x01
bmaControls( 0)  0x00
  Mute Control
bmaControls( 1)  0x02
bmaControls( 1)  0x00
  Volume Control
bmaControls( 2)  0x02
bmaControls( 2)  0x00
  Volume Control
iFeature0
  AudioControl Interface Descriptor:
bLength 9
bDescriptorType36
bDescriptorSubtype  3 (OUTPUT_TERMINAL)
bTerminalID 8
wTerminalType  0x0301 Speaker
bAssocTerminal  0
bSourceID   7
iTerminal   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass 1 Audio
  bInterfaceSubClass  2 Streaming
  bInterfaceProtocol  0
  iInterface  0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   1
  bNumEndpoints   2
  bInterfaceClass 1 Audio
  bInterfaceSubClass  2 Streaming
  bInterfaceProtocol  0
  iInterface  0
  AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType36
bDescriptorSubtype  1 (AS_GENERAL)
bTerminalLink   5
bDelay  1 frames
wFormatTag  1 PCM
  AudioStreaming Interface Descriptor:
bLength20
bDescriptorType36
bDescriptorSubtype  2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize   3
bBitResolution 

[Desktop-packages] [Bug 1812002] [NEW] package tex-common 6.09 failed to install/upgrade: geïnstalleerd tex-common pakket post-installation script subproces meldde een fout afsluitstatus 1

2019-01-16 Thread Stefaan Willaert
Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: tex-common 6.09
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
Date: Wed Jan 16 13:00:33 2019
ErrorMessage: geïnstalleerd tex-common pakket post-installation script 
subproces meldde een fout afsluitstatus 1
InstallationDate: Installed on 2011-03-03 (2875 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: tex-common
Title: package tex-common 6.09 failed to install/upgrade: geïnstalleerd 
tex-common pakket post-installation script subproces meldde een fout 
afsluitstatus 1
UpgradeStatus: Upgraded to bionic on 2019-01-16 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package bionic i386

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

Title:
  package tex-common 6.09 failed to install/upgrade: geïnstalleerd tex-
  common pakket post-installation script subproces meldde een fout
  afsluitstatus 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: tex-common 6.09
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Wed Jan 16 13:00:33 2019
  ErrorMessage: geïnstalleerd tex-common pakket post-installation script 
subproces meldde een fout afsluitstatus 1
  InstallationDate: Installed on 2011-03-03 (2875 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: tex-common
  Title: package tex-common 6.09 failed to install/upgrade: geïnstalleerd 
tex-common pakket post-installation script subproces meldde een fout 
afsluitstatus 1
  UpgradeStatus: Upgraded to bionic on 2019-01-16 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1812002/+subscriptions

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


[Desktop-packages] [Bug 996304] Re: Typo in manpage of 'xdg-icon-resource'

2019-01-16 Thread Paul White
Closing as bug fixed some time ago

** Changed in: hundredpapercuts
   Status: Confirmed => Fix Released

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

Title:
  Typo in manpage of 'xdg-icon-resource'

Status in One Hundred Papercuts:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Fix Released

Bug description:
  --noupdate
 Postpone updating the desktop icon system. If multiple icons are
 added in sequence this flag can be used to indicate that additional
 changes will follow and that it is not necassery to update the
 desktop icon system right away.

  "necassery" should be "necessary"

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xdg-utils 1.1.0~rc1-2ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
  Uname: Linux 3.2.14-kroqernel+ x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CheckboxSubmission: 7f98738f6663bda1ae1c2900a3a1db71
  CheckboxSystem: 577751a334467e78ed04da699e5debc9
  Date: Mon May  7 22:13:40 2012
  Dependencies:
   
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to precise on 2012-02-11 (86 days ago)

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

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


[Desktop-packages] [Bug 1772497] Re: gkbd-keyboard-display symbols overlap on RTL keyboards

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

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

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

Title:
  gkbd-keyboard-display symbols overlap on RTL keyboards

Status in libgnomekbd package in Ubuntu:
  Confirmed

Bug description:
  gkbd-keyboard-display, which shows the current keyboard layout on
  Gnome / Unity desktop, doesn't handle keyboards with RTL characters
  well. See the attached screenshot for the standard Hebrew keyboard,
  where the key labeled "Y" should have "ט" on lower left (key pressed
  without modifiers) and "װ" on lower right (key pressed with Alt).
  Currently both characters are marked on top of each other on lower
  right, which makes it impossible to distinguish what characters are
  created by the keypress.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gkbd-capplet 3.26.0-2
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 19:53:02 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.utf-8
   SHELL=/bin/bash
  SourcePackage: libgnomekbd
  UpgradeStatus: Upgraded to artful on 2017-11-05 (197 days ago)

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

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


[Desktop-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default

2019-01-16 Thread Pedro Côrte-Real
I agree with your point so won't be opening a bug to change the
defaults. But it should be easy to enable somewhere in the GUI sound
settings at least for specific applications. Video conferencing like
appear.in is only really usable with headphones because of this.
Adjusting text config files is not a good user experience. And I suspect
most people only care about the microphone because of these kinds of
uses.

According to this:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/196

It's possible for apps to request echo cancelation with 'filter.want
=echo-cancel' so maybe this is actually a bug in firefox?

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

Title:
  Echo cancelation should be enabled by default

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Echo cancellation is a basic feature for anything where you are using
  a video or audio conference. According to instructions like these:

  https://bugs.launchpad.net/elementaryos/+bug/1682253
  
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation
  
https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb

  There is now enough support in pulseaudio to do this well, but it's
  just not enabled by default. Users shouldn't need to fish around for
  strange things to add to config files. More complete defaults should
  be included.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pedrocr2684 F...m pulseaudio
   /dev/snd/controlC0:  pedrocr2684 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 23:45:10 2019
  InstallationDate: Installed on 2018-05-31 (229 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  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: 20FAS5TS00
  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:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1812014] [NEW] keyboard not responding after suspend after some time plus performance problem

2019-01-16 Thread Krzysztof
Public bug reported:

I work on Lenovo laptop y-700. When I resume system after suspend,
keyboards stop working, and sometimes there are performance problems
visible when playing videos. It happens not immediately but after a few
minutes or even a few hours of working. Restart or shutdown does not
finish correctly and I need to hold the power button for a few seconds.

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

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

Title:
  keyboard not responding after suspend after some time plus performance
  problem

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend,
  keyboards stop working, and sometimes there are performance problems
  visible when playing videos. It happens not immediately but after a
  few minutes or even a few hours of working. Restart or shutdown does
  not finish correctly and I need to hold the power button for a few
  seconds.

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

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


[Desktop-packages] [Bug 1812015] [NEW] Xwayland crashed and looped back to login gdm3

2019-01-16 Thread lotuspsychje
Public bug reported:

ubuntu 18.04.1 up to date @ 16/1/2019

after some time working on wayland, system crashed and looped me back to
login gdm3

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu4.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 16 16:06:32 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 anbox, 1, 4.15.0-42-generic, x86_64: installed
 anbox, 1, 4.15.0-43-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01]
InstallationDate: Installed on 2018-08-17 (152 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0025 Intel Corp. 
 Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook N7x0WU
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=6f47c936-5a01-46a0-ba45-9e56ecd8fd07 ro
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 7.009
dmi.board.asset.tag: Tag 12345
dmi.board.name: N7x0WU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.009:bd05/14/2018:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N7x0WU
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz N/A
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 N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Xwayland crashed and looped back to login gdm3

Status in xorg-server package in Ubuntu:
  New

Bug description:
  ubuntu 18.04.1 up to date @ 16/1/2019

  after some time working on wayland, system crashed and looped me back
  to login gdm3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu4.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 16:06:32 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-42-generic, x86_64: installed
   anbox, 1, 4.15.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01]
  InstallationDate: Installed on 2018-08-17 (152 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=6f47c936-5a01-46a0-ba45-9e56ecd8fd07 ro
  SourcePackage: xorg-

[Desktop-packages] [Bug 937054] Re: Allow renaming all files when copying or moving files

2019-01-16 Thread Helder
Reported at https://gitlab.gnome.org/GNOME/nautilus/issues/835.

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

Title:
  Allow renaming all files when copying or moving files

Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  Suppose we cut or copy 1000 files from a folder and paste them on a
  second folder containing among its files 500 files whose names
  coincide with those which are being pasted on the folder. Although the
  program currently detects the conflicting names and provide, for each
  conflicting file, the option to rename the new file to keep both in
  the target folder, the user will need to rename all 500 files by hand
  during the process, and this is very unpractical.

  The option to apply the (rename) action to all files shouldn't be
  disabled.

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

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


[Desktop-packages] [Bug 1812015] Re: Xwayland crashed and looped back to login gdm3

2019-01-16 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  Xwayland crashed and looped back to login gdm3

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 18.04.1 up to date @ 16/1/2019

  after some time working on wayland, system crashed and looped me back
  to login gdm3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu4.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 16 16:06:32 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-42-generic, x86_64: installed
   anbox, 1, 4.15.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01]
  InstallationDate: Installed on 2018-08-17 (152 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0025 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=6f47c936-5a01-46a0-ba45-9e56ecd8fd07 ro
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.009
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.009:bd05/14/2018:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2019-01-16 Thread Jacobi Kosiarek
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547

This issue is still alive and well in 2019. I encountered it while
upgrading from 18.04 to 18.10.

Advice from comment six resolved it, but it wasted several hours of my
time. Please apply a fix or at least more thorough log messages so that
medium to low skill users like myself can solve this problem for
themselves.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions

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


[Desktop-packages] [Bug 1760349] Re: Cannot log in to public open Wifi connection because not being redirected to login site

2019-01-16 Thread Ryan
** Description changed:

  I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to
  public Wifi hotspots without wifi security, that require login through a
  web page. I don't know if this is reproducible on arbitrary public
  networks, or only on the few I tried.
  
  The solution was as follows:
  - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll 
need root or sudo).
  - Add the following lines as recommended by Guruprasad 
(https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/):
  
  [connectivity]
  uri=http://network-test.debian.org/nm
  response=NetworkManager is online
  interval=300
  
  - Restart the network manager with service network-manager restart (will
  need sudo or root again).
  
  This is a very annoying and unnecessary default behavior it seems. Maybe
  a good idea to fix it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Mar 31 22:48:21 2018
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2018-02-18 (41 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180218)
  IpRoute:
-  default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600 
-  10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 
600 
-  169.254.0.0/16 dev wlp1s0 scope link metric 1000
+  default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600
+  10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 
600
+  169.254.0.0/16 dev wlp1s0 scope link metric 1000
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
  ProcEnviron:
-  LANGUAGE=
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
-  DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
-  wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
SuedtirolSpot_1  c4464785-b548-4655-b06b-48a0aec06a87  
/org/freedesktop/NetworkManager/ActiveConnection/3 
-  lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
+  DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
+  wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
SuedtirolSpot_1  c4464785-b548-4655-b06b-48a0aec06a87  
/org/freedesktop/NetworkManager/ActiveConnection/3
+  lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
-  running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  Cannot log in to public open Wifi connection because not being
  redirected to login site

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to
  public Wifi hotspots without wifi security, that require login through
  a web page. I don't know if this is reproducible on arbitrary public
  networks, or only on the few I tried.

  The solution was as follows:
  - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll 
need root or sudo).
  - Add the following lines as recommended by Guruprasad 
(https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/):

  [connectivity]
  uri=http://network-test.debian.org/nm
  response=NetworkManager is online
  int

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-01-16 Thread Lev Levchenko
And bug reproduces again. +WIN key blocked again at that moment.
Interesting observation: unplug-plug mouse helps, hit becomes correct and WIN 
key working again.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

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


[Desktop-packages] [Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Fusion
I manage to record the crash. I resume from suspend 5 hours later (pc
was suspended for about 5h) and the following behavior happened:

First video: exactly after I resume from suspend. I can press buttons but 
nothing happens. Finally I press suspend again.
https://mega.nz/#!joQ0WK7Q!5dXLMBzUr3yboqH5k6FtoeIIN3JDwVBGbKBzPLLErCI


Second video: I resume after a few seconds from the previous suspend (video 1). 
Ubuntu were not responding at all. When I move the mouse screen opens in black 
and then closes again. Also ctrl+alt+F1 does not work.
https://mega.nz/#!CkIGGKrY!mu5P4eW0275oJuxwv7CI7-flJUJgExqADVfP07XIdTU

I also tried to copy as more lines as I could from the results of
"journalctl -b 0" command on terminal. The results are here:
https://pastebin.com/PCccKQDh

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

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  my system:
  ubuntu 18.10
  4k monitor with 1 scale and 1.5 font scale
  nvidia 410 and 390 drivers are checked

  when happened:
  lock screen or suspend. return after that.
  if I have user password prompt enabled: everything ok
  if I haven't user password prompt enabled, system started with gnome crashed

  I expect:
  ubuntu to has the same behaviour either I have a password either not.

  What happened:
  in case of no password (I should just 'swipe up' or press 'space' and 
everything should be ready.. but) most of the times I can not return to desktop.
  - freezes on a screen with panels but no desktop
  - freezes on a purple screen that no command is working (as ctrl+alt+t)
  - freezes on a useless gnome panels (dash and topbar) mode

  solution chosen:
  I press ctrl+alt+F1 to change environment, I enter my password... BUT again 
the gnome is too slow, app icon is always on and everything is acting weird 
(some apps' icon that I have opened on the other session is liked pined on dash 
without have the option to unpin it - like I see it but it is not pinned)
  So, I just save what I can through the new session and just restart the pc 
(in new session is available - in the previous is only suspend available)

  frequency: about 80% of the times. If lock-screen showed up normally
  (and I have to press space to unlock) everything works like a charm
  afterwards. If not.. it will be the mess I described above

  hope it helps
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-08-28 (84 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (32 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1812101] [NEW] libreoffice-kde5 file dialog/picker doesn't add extension automatically

2019-01-16 Thread Hans P Möller
Public bug reported:

Description:
libreoffice-kde5 file dialog doesn't add automatically the file extension which 
are important for.docx .xlsx, otherwise the system recognize them as zip.

When removing that package and letting only libreoffice-gtk, extension
are added automatically.

Steps to Reproduce:
1. if isn't installed install libreoffice-kde5 package
2. save a writer document as .docx but doesn't add manually the extension

Actual Results:
file are saved without .docx extension.

Expected Results:
file should be saved with the .docx extension

Additional Info:
Using lubuntu 18.10
Version: 6.1.4.2
Build ID: 1:6.1.4-0ubuntu1
CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
Locale: es-CL (es_CL.UTF-8); Calc: group threaded

I filed a bug against libreoffice to because I don't know who is
responsible for libreoffice-kde5 package
https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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


** Tags: kde libreoffice-kde libreoffice-kde5

** Description changed:

- escription:
+ Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.
  
  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.
  
  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension
  
  Actual Results:
  file are saved without .docx extension.
  
  Expected Results:
  file should be saved with the .docx extension
  
  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
- CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
+ CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded
  
  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Description:
  libreoffice-kde5 file dialog doesn't add automatically the file extension 
which are important for.docx .xlsx, otherwise the system recognize them as zip.

  When removing that package and letting only libreoffice-gtk, extension
  are added automatically.

  Steps to Reproduce:
  1. if isn't installed install libreoffice-kde5 package
  2. save a writer document as .docx but doesn't add manually the extension

  Actual Results:
  file are saved without .docx extension.

  Expected Results:
  file should be saved with the .docx extension

  Additional Info:
  Using lubuntu 18.10
  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu1
  CPU threads: 2; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
  Locale: es-CL (es_CL.UTF-8); Calc: group threaded

  I filed a bug against libreoffice to because I don't know who is
  responsible for libreoffice-kde5 package
  https://bugs.documentfoundation.org/show_bug.cgi?id=122752

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

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


[Desktop-packages] [Bug 1811999] Re: [USB-Audio - Audioengine D3, playback] fails after a while (a second)

2019-01-16 Thread usman
Okay, I am confused now. 
I have another system for with usb DAC works just fine. 

Distributor ID: Ubuntu
Description:Ubuntu 18.10
Release:18.10
Codename:   cosmic

Linux 4.18.0-13-generic x86_64

And dmesg show me same issue:

[ 3649.034233] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 3649.651192] usb 3-1: New USB device found, idVendor=2912, idProduct=120b, 
bcdDevice= 1.0c
[ 3649.651199] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3649.651204] usb 3-1: Product: Audioengine D3
[ 3649.651208] usb 3-1: Manufacturer: Audioengine
[ 3649.651212] usb 3-1: SerialNumber: Audioengine
[ 3649.696266] usb 3-1: 1:1: cannot get freq at ep 0x1
[ 3649.719070] usbcore: registered new interface driver snd-usb-audio
[ 3649.762678] usb 3-1: 1:1: cannot get freq at ep 0x1
[ 3649.785497] usb 3-1: 1:1: cannot get freq at ep 0x1

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

Title:
  [USB-Audio - Audioengine D3, playback] fails after a while (a second)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  USB DAC stops playing sound after a second.
  I had problem with kernel 4.15. 
  So, I tried upgrading to 4.19 but still issue persists. 
  I think, we might need to add it to sound/usb/quirks.c

  I see following in dmesg

  [ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16
  [ 5955.721597] usb 1-1.4.1: new full-speed USB device number 17 using xhci_hcd
  [ 5956.302910] usb 1-1.4.1: New USB device found, idVendor=2912, 
idProduct=120b, bcdDevice= 1.0c
  [ 5956.302917] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 5956.302921] usb 1-1.4.1: Product: Audioengine D3
  [ 5956.302926] usb 1-1.4.1: Manufacturer: Audioengine
  [ 5956.302929] usb 1-1.4.1: SerialNumber: Audioengine
  [ 5956.320621] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1
  [ 5956.920844] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1
  [ 5956.938929] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1

  And lsusb -v has following entry for the device.

  Bus 001 Device 017: ID 2912:120b
  Couldn't open device, some information will be missing
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   1.00
    bDeviceClass0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor   0x2912
    idProduct  0x120b
    bcdDevice1.0c
    iManufacturer   1
    iProduct2
    iSerial 3
    bNumConfigurations  1
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength  131
  bNumInterfaces  2
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0x80
    (Bus Powered)
  MaxPower  200mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   0
    bInterfaceClass 1 Audio
    bInterfaceSubClass  1 Control Device
    bInterfaceProtocol  0
    iInterface  0
    AudioControl Interface Descriptor:
  bLength 9
  bDescriptorType36
  bDescriptorSubtype  1 (HEADER)
  bcdADC   1.00
  wTotalLength   43
  bInCollection   1
  baInterfaceNr( 0)   1
    AudioControl Interface Descriptor:
  bLength12
  bDescriptorType36
  bDescriptorSubtype  2 (INPUT_TERMINAL)
  bTerminalID 5
  wTerminalType  0x0101 USB Streaming
  bAssocTerminal  0
  bNrChannels 2
  wChannelConfig 0x0003
    Left Front (L)
    Right Front (R)
  iChannelNames   0
  iTerminal   0
    AudioControl Interface Descriptor:
  bLength13
  bDescriptorType36
  bDescriptorSubtype  6 (FEATURE_UNIT)
  bUnitID 7
  bSourceID   5
  bControlSize2
  bmaControls( 0)  0x01
  bmaControls( 0)  0x00
    Mute Control
  bmaControls( 1)  0x02
  bmaControls( 1)  0x00
    Volume Control
  bmaControls( 2)  0x02
  bmaControls( 2)  0x00
    Volume Control
  iFeature0
    AudioControl Interface Descriptor:
  bLength 9
  bDescriptorType36
  bDescriptorSubtype  3 (OUTPUT_TERMINAL)
  bTerminalID 8
  wTer

[Desktop-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time plus performance problem

2019-01-16 Thread Sebastien Bacher
the description sounds a bit similar to bug #1807056

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

Title:
  keyboard not responding after suspend after some time plus performance
  problem

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend,
  keyboards stop working, and sometimes there are performance problems
  visible when playing videos. It happens not immediately but after a
  few minutes or even a few hours of working. Restart or shutdown does
  not finish correctly and I need to hold the power button for a few
  seconds.

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

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


[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-01-16 Thread Sebastien Bacher
Could those having the issue add their journalctl log from the boot
which showed the bug? Also comment #6 is about
org.gnome.SettingsDaemon.Keyboard.desktop which is a different component
(and it looks like xorg got issue and that impacted other components
too)

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

Title:
  Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1760349] Re: Cannot log in to public open Wifi connection because not being redirected to login site

2019-01-16 Thread Sebastien Bacher
Thank you for your bug report, that's not a network-manager issue
though, there is no need to create that file since the package already
provides a binary with that configuration 'network-manager-config-
connectivity-ubuntu' which is installed by default on Ubuntu. The issue
could be that Kubuntu doesn't install that package by default though,
which would be a problem to bring to the kubuntu team

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Cannot log in to public open Wifi connection because not being
  redirected to login site

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to
  public Wifi hotspots without wifi security, that require login through
  a web page. I don't know if this is reproducible on arbitrary public
  networks, or only on the few I tried.

  The solution was as follows:
  - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll 
need root or sudo).
  - Add the following lines as recommended by Guruprasad 
(https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/):

  [connectivity]
  uri=http://network-test.debian.org/nm
  response=NetworkManager is online
  interval=300

  - Restart the network manager with service network-manager restart
  (will need sudo or root again).

  This is a very annoying and unnecessary default behavior it seems.
  Maybe a good idea to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Mar 31 22:48:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-02-18 (41 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180218)
  IpRoute:
   default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600
   10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 
600
   169.254.0.0/16 dev wlp1s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
SuedtirolSpot_1  c4464785-b548-4655-b06b-48a0aec06a87  
/org/freedesktop/NetworkManager/ActiveConnection/3
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1760349/+subscriptions

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


[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2019-01-16 Thread Sebastien Bacher
the gnome-shell error is a bit weird, maybe there is an issue on this
component

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

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

2019-01-16 Thread Sebastien Bacher
** Changed in: ubuntu-geoip (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Triaged
Status in ubuntu-geoip source package in Artful:
  Won't Fix

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  
  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

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

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


[Desktop-packages] [Bug 1788005] Re: print-playing-formats %aa and %aA report wrong value

2019-01-16 Thread Sebastien Bacher
Thanks, that has been now reported upstream on
https://gitlab.gnome.org/GNOME/rhythmbox/issues/1688

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

** Changed in: rhythmbox (Ubuntu)
   Status: New => Triaged

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

Title:
  print-playing-formats %aa and %aA report wrong value

Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  These formats incorrectly supply the value of the track artist,
  instead of the album artist.

  To fix this in 3.4.2 (Ubuntu 18.04), edit remote/dbus/rb-client.c
  lines 301 and 308 to say "xesam:albumArtist" instead of
  "xesam:artist". In 3.3 (Ubuntu 16.04) the corresponding lines are 288
  and 295.

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

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


[Desktop-packages] [Bug 1812057] [NEW] Upgrade Lost Firefox ESR

2019-01-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

System was upgraded from Xubuntu 14 to 16 by DVD.  It wiped out many
things, including the installation of Firefox ESR.

ESR was manually reinstalled, but there appears to be no integration
with the former profiles.  While they still exist, both Firefox Quantum
and Firefox ESR see the exact same profiles.  There appears to be no way
to remedy the problem.

No crash is involved.  If -profilemanager is used in Firefox, the same
choices appear in both versions.  This was not the case prior to the
upgrade.


Description:Ubuntu 16.04.5 LTS
Release:16.04

firefox-esr:
  Installed: 52.9.0esr-1~16.04.york0
  Candidate: 52.9.0esr-1~16.04.york0
  Version table:
 *** 52.9.0esr-1~16.04.york0 500
500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu 
xenial/main amd64 Packages
100 /var/lib/dpkg/status

firefox:
  Installed: 64.0+build3-0ubuntu0.16.04.1
  Candidate: 64.0+build3-0ubuntu0.16.04.1
  Version table:
 *** 64.0+build3-0ubuntu0.16.04.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 45.0.2+build1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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


** Tags: bot-comment esr firefox upgrade
-- 
Upgrade Lost Firefox ESR
https://bugs.launchpad.net/bugs/1812057
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox 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 1812057] Re: Upgrade Lost Firefox ESR

2019-01-16 Thread Ubuntu User
dpkg -S /usr/bin/firefox
diversion by firefox-esr from: /usr/bin/firefox
diversion by firefox-esr to: /usr/bin/firefox.real
firefox-esr, firefox: /usr/bin/firefox


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

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

Title:
  Upgrade Lost Firefox ESR

Status in firefox package in Ubuntu:
  New

Bug description:
  System was upgraded from Xubuntu 14 to 16 by DVD.  It wiped out many
  things, including the installation of Firefox ESR.

  ESR was manually reinstalled, but there appears to be no integration
  with the former profiles.  While they still exist, both Firefox
  Quantum and Firefox ESR see the exact same profiles.  There appears to
  be no way to remedy the problem.

  No crash is involved.  If -profilemanager is used in Firefox, the same
  choices appear in both versions.  This was not the case prior to the
  upgrade.


  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  firefox-esr:
Installed: 52.9.0esr-1~16.04.york0
Candidate: 52.9.0esr-1~16.04.york0
Version table:
   *** 52.9.0esr-1~16.04.york0 500
  500 http://ppa.launchpad.net/jonathonf/firefox-esr-52/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  firefox:
Installed: 64.0+build3-0ubuntu0.16.04.1
Candidate: 64.0+build3-0ubuntu0.16.04.1
Version table:
   *** 64.0+build3-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   45.0.2+build1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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


[Desktop-packages] [Bug 1760345] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

2019-01-16 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1725480 ***
https://bugs.launchpad.net/bugs/1725480

** This bug is no longer a duplicate of private bug 1726398
** This bug has been marked a duplicate of bug 1725480
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Rhythmbox worked after I first used it. Somme 5xx songs were added and
  everything went fine. Then I added one more song to my music folder
  ans started rhythmbox again in order to add this new song to my music.
  From then on rhythmbox keeps on crashing. That meens, it stars, but
  closes some seconds later.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Mar 31 21:41:10 2018
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2018-03-31 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha i386 
(20180307.1)
  ProcCmdline: rhythmbox
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb77b1b90 :  mov
(%eax),%eax
   PC (0xb77b1b90) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   gtk_tree_view_set_model () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/librhythmbox-core.so.10
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1761367] Re: found solution rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

2019-01-16 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1725480 ***
https://bugs.launchpad.net/bugs/1725480

** This bug is no longer a duplicate of private bug 1726398
** This bug has been marked a duplicate of bug 1725480
   rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

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

Title:
  found solution rhythmbox crashed with SIGSEGV in
  gtk_tree_view_get_column()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 18.04 Beta. I de-installed the alternative toolbar. Now
  everything works for me.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Thu Apr  5 05:48:37 2018
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2018-03-18 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  ProcCmdline: rhythmbox
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f7992d49724 :  mov
(%rax),%rax
   PC (0x7f7992d49724) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_view_set_model () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1775909] Re: Anytime when i start the Programm. It Closed and Crashed

2019-01-16 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  Anytime when i start the Programm. It Closed and Crashed

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  I have my Music on a Debian Server with a Samba share. In Unbuntu
  16.04 was all good.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun  8 19:04:21 2018
  InstallationDate: Installed on 2018-04-27 (42 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1790624] Re: rhythmbox periodically hangs during playback via SFTP

2019-01-16 Thread Sebastien Bacher
Thank you for your bug report. How is the sftp mounting done? Do you use the 
gvfs location or a fuse mount or similar? Can you access/Read from that mount 
using e.g nautilus when rhythmbox is blocking?
In any case that's probably an upstream issue and should be reported on 
https://gitlab.gnome.org/GNOME/rhythmbox/issues/new

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

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

Title:
  rhythmbox periodically hangs during playback via SFTP

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Scenario: a server is available via LAN from which content is played
  back via SFTP (ssh, gvfs).

  After some time (could be an hour) rhythmbox hangs and a window comes
  up suggesting that you can either wait or terminate rhythmbox.

  There are no network interruptions that would cause something like
  this (the issue comes up quite frequently) and plus I do not see any
  of the threads to be in the D state.

  strace shows that there is a futex wait for some condition.

  ps:

  redacted 20291  3.3  1.0 1989228 173472 tty2   Sl+  12:14   4:49
  rhythmbox

  ➜  ~ ps -T -o pid,tid,class,rtprio,ni,pri,psr,pcpu,stat,wchan:14,comm -p 
20291 
PID   TID CLS RTPRIO  NI PRI PSR %CPU STAT WCHAN  COMMAND
  20291 20291 TS   -   0  19   6  0.9 Sl+  futex_wait_que rhythmbox
  20291 20294 TS   -   0  19   6  0.0 Sl+  poll_schedule_ gmain
  20291 20295 TS   -   0  19   7  0.0 Sl+  poll_schedule_ gdbus
  20291 20296 TS   -   0  19   7  0.0 Sl+  poll_schedule_ dconf worker
  20291 20298 TS   -   0  19   2  0.2 Sl+  futex_wait_que typefind:sink
  20291 20306 TS   -   0  19   5  0.0 Sl+  futex_wait_que rhythmdb-thread
  20291 20344 TS   -   0  19   4  0.1 Sl+  futex_wait_que id3demux167:sin
  20291 20346 TS   -   0  19   7  0.1 Sl+  poll_schedule_ mpegaudioparse1
  20291 20392 TS   -   0  19   4  0.2 Sl+  futex_wait_que mpegaudioparse1
  20291 20393 TS   -   0  19   4  0.0 Sl+  futex_wait_que id3demux168:sin
  20291 12125 TS   -   0  19   4  0.0 Sl+  futex_wait_que typefind:sink

  
  sudo strace -f -p 20291
  strace: Process 20291 attached with 11 threads
  [pid 12125] futex(0x55eacb8dc778, FUTEX_WAIT_PRIVATE, 1, NULL 
  [pid 20393] futex(0x7fe7201320b8, FUTEX_WAIT_PRIVATE, 1, NULL 
  [pid 20392] futex(0x7fe6f4013538, FUTEX_WAIT_PRIVATE, 1, NULL 
  [pid 20346] restart_syscall(<... resuming interrupted poll ...> 
  [pid 20344] futex(0x7fe6f0004898, FUTEX_WAIT_PRIVATE, 1, NULL 
  [pid 20306] futex(0x55eacab00580, FUTEX_WAIT_PRIVATE, 2, NULL 
  [pid 20298] futex(0x55eacb8dcf58, FUTEX_WAIT_PRIVATE, 1, NULL 
  [pid 20296] restart_syscall(<... resuming interrupted poll ...> 
  [pid 20295] restart_syscall(<... resuming interrupted poll ...> 
  [pid 20294] restart_syscall(<... resuming interrupted poll ...> 
  [pid 20291] futex(0x55eacf0ea9a0, FUTEX_WAIT_PRIVATE, 2, NULL 

  # after killing via the GUI button
  [pid 20344] <... futex resumed> )   = ? ERESTARTSYS (To be restarted if 
SA_RESTART is set)
  [pid 12125] <... futex resumed>)= ?
  [pid 20393] <... futex resumed>)= ?
  [pid 20392] <... futex resumed>)= ?
  [pid 12125] +++ killed by SIGKILL +++
  [pid 20393] +++ killed by SIGKILL +++
  [pid 20392] +++ killed by SIGKILL +++
  [pid 20346] <... restart_syscall resumed>) = ?
  [pid 20344] +++ killed by SIGKILL +++
  [pid 20346] +++ killed by SIGKILL +++
  [pid 20306] <... futex resumed>)= ?
  [pid 20296] <... restart_syscall resumed>) = ?
  [pid 20295] <... restart_syscall resumed>) = ?
  [pid 20306] +++ killed by SIGKILL +++
  [pid 20296] +++ killed by SIGKILL +++
  [pid 20298] <... futex resumed>)= ?
  [pid 20295] +++ killed by SIGKILL +++
  [pid 20298] +++ killed by SIGKILL +++
  [pid 20294] <... restart_syscall resumed>) = ?
  [pid 20291] <... futex resumed>)= ?
  [pid 20294] +++ killed by SIGKILL +++
  +++ killed by SIGKILL +++

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  4 14:44:50 2018
  InstallationDate: Installed on 2018-07-12 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768364] Re: Combo boxes close immediately after opening

2019-01-16 Thread Sebastien Bacher
** Changed in: rhythmbox (Ubuntu)
   Status: New => Invalid

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

Title:
  Combo boxes close immediately after opening

Status in gtk+3.0 package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Sometimes when a select box is clicked, it opens and then closes
  almost immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 14:39:28 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-27 (4 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1768364/+subscriptions

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


[Desktop-packages] [Bug 1780444] Re: rhythmbox on Ubuntu 18.04 does not adopt CSD even when default alternative toolbar plugin is ON

2019-01-16 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1720649 ***
https://bugs.launchpad.net/bugs/1720649

** This bug has been marked a duplicate of bug 1720649
   unity patch makes a menubar displays when GNOME-app-menu is disabled

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

Title:
  rhythmbox on Ubuntu 18.04 does not adopt CSD even when default
  alternative toolbar plugin is ON

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  rhythmbox:
Installed: 3.4.2-4ubuntu1
Candidate: 3.4.2-4ubuntu1
Version table:
   *** 3.4.2-4ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I expect to see GNOME CSD in Rhythmbox, but today I saw that CSD was
  not being implemented and the old giant titlebar was implemented. Not
  sure when this change took place, but I noticed it today. I checked
  the plugins and Alternative Toolbar plugin was turned ON. I'd not
  touched plugin settings at all since installation. I was using stock
  Rhythmbox - never touched settings.

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

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


[Desktop-packages] [Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep

2019-01-16 Thread Sebastien Bacher
** Changed in: rhythmbox (Ubuntu)
   Status: New => Invalid

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

Title:
  Pressing Print Screen in keyboard makes Rhythmbox go to sleep

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Steps:

  1. Start Rhythmbox and play music
  2. Press Print Screen in keyboard
  3. Music stops and cannot be played again in Rhythmbox
  4. If the music does not stop from the first time try step 2 again and again 
until it stops

  I can navigate the UI of Rhythmbox, but I cannot play music. I have to
  kill the sleeping process in order to play music.

  I can reproduce this bug in Totem and Clementine too.

  Clementine and Totem present this error:

  pa_stream_writable_size() failed: Connection terminated

  This bug affects Bionic too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr9438 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 14:42:55 2018
  InstallationDate: Installed on 2017-06-21 (296 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09

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

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


[Desktop-packages] [Bug 1750141] Re: rhythmbox crashed with SIGABRT in g_assertion_message()

2019-01-16 Thread Sebastien Bacher
https://errors.ubuntu.com/problem/edc91a5e55a32a4483bcf051a36a7c7b8123cbf3

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

Title:
  rhythmbox crashed with SIGABRT in g_assertion_message()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Right clicked Rhytmbox in the Dash, then clicked Stop & Quit.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 14:53:45 2018
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2018-01-31 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  ProcCmdline: rhythmbox
  Signal: 6
  SourcePackage: rhythmbox
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_tree_store_remove () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: rhythmbox crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1725480] Re: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

2019-01-16 Thread Sebastien Bacher
https://errors.ubuntu.com/problem/8ae0367905ba05bf620d0194fb83f741a7e717de

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

Title:
  rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  Just had it open.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: rhythmbox 3.4.1-2ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 22:42:17 2017
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: rhythmbox /home/username/Musik/Sabine\ Alef/02\ Entspannung\ 
mit\ Yoga.mp3
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7ff6a1f0e424 :  mov
(%rax),%rax
   PC (0x7ff6a1f0e424) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_view_remove_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1737741] Re: rhythmbox-client --seek fails at more than 2148 seconds

2019-01-16 Thread Sebastien Bacher
Upstream is https://gitlab.gnome.org/GNOME/rhythmbox/issues/1618

** Changed in: rhythmbox (Ubuntu)
   Status: New => Triaged

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

Title:
  rhythmbox-client --seek fails at more than 2148 seconds

Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  System Information:
  Description:  Ubuntu 17.04
  Release:  17.04

  rhythmbox:
Installiert:   3.4.1-2ubuntu1
Installationskandidat: 3.4.1-2ubuntu1
Versionstabelle:
   *** 3.4.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  Behavior:

  via the commandline the rythembox client can skip to a specific second via 
the command
rhythmbox-client --seek

  This works for seeking up to second 2147.
  Any number beyond that skips to the next track, even if the track is longer 
instead of going to the correct position in the file itself (the track  has 
over 4000 seconds)

  my guess is that that the internal format is a signed 32-Bit Int that 
overflows.
  2148 seconds = 214800 milliseconds -> cast to Int32 is -2146967296 

  which would certainly produce an error (seeking to a negative number)

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

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


[Desktop-packages] [Bug 1665554] Re: Rhythmbox GUI is flickering and not usable

2019-01-16 Thread Sebastien Bacher
Thank you for your bug report, is that still an issue in newer Ubuntu
versions?

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

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

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

Title:
  Rhythmbox GUI is flickering and not usable

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  When starting up rhythmbox the gui is somewhat distorted and not
  usable. The buttons and lists are shown randomly, and flickering while
  the mouse is moving. Once rhythmbox is started, the whole session is
  going nuts, even for other windows.

  :~/$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  :~/$ apt-cache policy rhythmbox
  rhythmbox:
Installiert:   3.3-1ubuntu7
Installationskandidat: 3.3-1ubuntu7
Versionstabelle:
   *** 3.3-1ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rhythmbox 3.3-1ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 17 07:49:53 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (300 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error

2019-01-16 Thread Alexander McColl
Affected on Mint 19.1 running i3lock
locks and unlocks fine, but systemd reports:

"pam_ecryptfs: seteuid error"

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

Title:
  pam_ecryptfs: seteuid error

Status in eCryptfs:
  Confirmed
Status in GNOME Screensaver:
  New
Status in ecryptfs-utils package in Ubuntu:
  Triaged
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in kscreenlocker package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in gnome-screensaver package in Debian:
  New

Bug description:
  I get this error message in the syslog when I authenticate succesfully
  in the screensaver.

  ---
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2012-06-13 (172 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  Package: gnome-screensaver 3.6.0-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1812125] Re: Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result until manually installed, icons get disarranged every reboot in other PC configurations

2019-01-16 Thread David Gil
(NOTICE: This used a custom version of Xubuntu)

** Description changed:

  lsb_release -rd
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-bin 1.36.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jan 17 06:23:36 2019
  InstallationDate: Installed on 2019-01-16 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 3.8.0 "Gratitude" (20181126)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ (NOTE: This used a custom version of Xubuntu but the screenshot came
+ direct from the official Xubuntu version "xubuntu-18.04.1-desktop-
+ amd64.iso")

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

Title:
  Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result
  until manually installed, icons get disarranged every reboot in other
  PC configurations

Status in gvfs package in Ubuntu:
  New

Bug description:
  lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-bin 1.36.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jan 17 06:23:36 2019
  InstallationDate: Installed on 2019-01-16 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 3.8.0 "Gratitude" (20181126)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

  (NOTE: This used a custom version of Xubuntu but the screenshot came
  direct from the official Xubuntu version "xubuntu-18.04.1-desktop-
  amd64.iso")

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

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


[Desktop-packages] [Bug 1812125] [NEW] Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result until manually installed, icons get disarranged every reboot in other PC configurations

2019-01-16 Thread David Gil
Public bug reported:

lsb_release -rd

Description:Ubuntu 18.04.1 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs-bin 1.36.1-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 17 06:23:36 2019
InstallationDate: Installed on 2019-01-16 (0 days ago)
InstallationMedia: Moment Plus OS amd64 3.8.0 "Gratitude" (20181126)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

(NOTE: This used a custom version of Xubuntu but the screenshot came
direct from the official Xubuntu version "xubuntu-18.04.1-desktop-
amd64.iso")

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


** Tags: amd64 apport-bug bionic

** Attachment added: "xubuntu-18.04.1-livediskSrc-bug.png"
   
https://bugs.launchpad.net/bugs/1812125/+attachment/5229781/+files/xubuntu-18.04.1-livediskSrc-bug.png

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

Title:
  Xubuntu 18.04 LTS had no gvfs-bin installed by default, as a result
  until manually installed, icons get disarranged every reboot in other
  PC configurations

Status in gvfs package in Ubuntu:
  New

Bug description:
  lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-bin 1.36.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jan 17 06:23:36 2019
  InstallationDate: Installed on 2019-01-16 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 3.8.0 "Gratitude" (20181126)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

  (NOTE: This used a custom version of Xubuntu but the screenshot came
  direct from the official Xubuntu version "xubuntu-18.04.1-desktop-
  amd64.iso")

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

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


[Desktop-packages] [Bug 1804744] Re: Restoring from new location does not find backup files

2019-01-16 Thread Michael Terry
I'm able to confirm on bionic. Don't have my cosmic install handy
anymore.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Restoring from new location does not find backup files

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Bionic:
  Fix Committed
Status in deja-dup source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When a user tries to restore a backup on a fresh Ubuntu install, deja-
  dup will not be able to find their backup at first.

  A workaround is to set the current backup location on the fresh
  install to the old backup location. But that's not at all an obvious
  path. A user would not normally try that.

  [Test Case]

  1. Back up some files to a temporary dir.
  2. gsettings reset-recursively org.gnome.DejaDup
  3. Try to restore from that temporary dir.

  Notice that deja-dup will complain about waiting for Google Drive to
  be set up (even though your backup drive has nothing to do with
  Google).

  [Regression Potential]

  The proposed patch mostly affects the restore dialog. Any regressions
  would likely be in that flow.

  [Original Report]

  1. I back up my computer to my external hard drive
  2. I reinstall my new distro
  3. I install deja-dup and duplicity
  4. I open deja-dup, and select restore
  5. I select my external hard drive and the restore directory
  6. Deja-dup fails with "no backup found" message and creates a new backup 
directory on the hard drive

  This indicated to me that deja dup ignored the restore directory I
  entered, and instead used the default directory, which did not exist,
  hence restore fails because the backend is told to look in the wrong
  place for the backup! This seems like more a user interface issue than
  an issue with the backup.

  Here is the workflow I had to use to restore my backup:

  1. Set storage location to "local folder" and then manually navigate to the 
folder on my external hard drive. If I did not do this specifically, then 
backup would fail. Selecting the external hard drive directly as the device and 
entering the folder in the "folder" field also fails.
  2. Select restore and again use "local folder" and manually navigate to the 
folder on my external hard drive. If I instead try to use the hard drive device 
listed and enter the backup folder in the "folder" field, the restore also 
fails.

  This issue occurs on both Ubuntu 18.04.1 and ElementaryOS Juno.

  lsb_release -d
  Description:  elementary OS 5.0 Juno

  dpkg-query -W deja-dup duplicity
  deja-dup  37.1-2fakesync1
  duplicity 0.7.17-0ubuntu1

  gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
  cat /tmp/deja-dup.gsettings
  org.gnome.DejaDup last-restore '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup last-run '2018-11-23T01:39:44.556645Z'
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup prompt-check '2018-11-22T12:34:36.095106Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup exclude-list ['/home/ethan/.local/share/Trash']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'ethan-laptop'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'ethan-laptop'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.OpenStack container 'ethan-laptop'
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS folder 'ethan-laptop'
  org.gnome.DejaDup.Local folder '/media/ethan/porta_500gb/m1330'
  org.gnome.DejaDup.Remote uri ''
  org.gnome.DejaDup.Remote folder 'ethan-laptop'
  org.gnome.DejaDup.Drive uuid '1919a422-d154-4e19-b551-f74b56cf1f0e'
  org.gnome.DejaDup.Drive icon '. GThemedIcon drive-harddisk-usb drive-harddisk 
drive'
  org.gnome.DejaDup.Drive folder 'm1330'
  org.gnome.DejaDup.Drive name 'porta_500gb'
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA folder 'ethan-laptop'
  org.gnome.DejaDup.GOA type 'google'
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File relpath @ay []

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1804744/+subscriptions

-- 
Ma

[Desktop-packages] [Bug 1730229] Re: Desktop stops accepting input from mouse, keyboard, touchpad, or touchscreen, but topbar and dock still accept input

2019-01-16 Thread Mike Willems
*** This bug is a duplicate of bug 1181666 ***
https://bugs.launchpad.net/bugs/1181666

And, ftr, I agree that the duplicate status is wrong!

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

Title:
  Desktop stops accepting input from mouse, keyboard, touchpad, or
  touchscreen, but topbar and dock still accept input

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The desktop area stops accepting inputs from the mouse, keyboard,
  trackpad, and touchscreen.

  However, gnome session is not frozen, because I can still interact
  with the topbar and the Ubuntu Dock using the pointer or keyboard.

  I can move the pointer using the trackpad, or attached mouse, but
  clicking or typing in windows on the desktop area has no effect.

  What I can not do:
  - I can not close windows using the window buttons.
  - I can not move windows.
  - I can not bring windows to the foreground.
  - I can not click on any dialog buttons.
  - I can not type in any test areas (such as in gedit).

  What I can do:
  - I can start the activities view by clicking on Activities in the top left 
corner.
  - I can launch programs from the dock and from the applications button.
  - I can also interact with the notifications area or the indicator icons at 
the right of the topbar.
  - I can type and search for applications after entering the Activities 
overview.

  Logging-out and loggin-in does not resolve the problem.
  - Note that GDM accepts mouse and keyboard inputs.
  - After logging back into the desktop, I can not interact with the desktop 
area, as before.

  Restating is the only way to regain ability to interact with the
  windows and desktop area.

  I experience this issue on my laptop running Ubuntu 17.10, but I have
  not had this issue on my desktop running Ubuntu 17.10.

  Additional Information (Laptop):
    2017 HP Spectre x360 Convertible Laptop - 15t touch
    GeForce MX150
    Using xserver-xorg 1:7.7+19ubuntu3 amd64
    Using Nvidia binary driver version 384.90
    $ lsb_release -rd
    Description:Ubuntu 17.10
    Release:17.10
    $ gnome-shell --version
    GNOME Shell 3.26.1
    $ mutter --version
    mutter 3.26.1

  Note: My desktop (which does not have this issue) is also running
  Ubuntu 17.10, has an Nvidia card, and is using the proprietary driver
  with xorg.

  I'm not sure if mutter is responsible for handling mouse/keyboard
  inputs separately from GDM, extensions, and the topbar, so I opened
  this bug against gnome-shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 14:19:45 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.gedit.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1730229] Re: Desktop stops accepting input from mouse, keyboard, touchpad, or touchscreen, but topbar and dock still accept input

2019-01-16 Thread Mike Willems
*** This bug is a duplicate of bug 1181666 ***
https://bugs.launchpad.net/bugs/1181666

Hi Justin, did you ever find a resolution to this? I'm on 18.04
experiencing the exact same issue.

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

Title:
  Desktop stops accepting input from mouse, keyboard, touchpad, or
  touchscreen, but topbar and dock still accept input

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The desktop area stops accepting inputs from the mouse, keyboard,
  trackpad, and touchscreen.

  However, gnome session is not frozen, because I can still interact
  with the topbar and the Ubuntu Dock using the pointer or keyboard.

  I can move the pointer using the trackpad, or attached mouse, but
  clicking or typing in windows on the desktop area has no effect.

  What I can not do:
  - I can not close windows using the window buttons.
  - I can not move windows.
  - I can not bring windows to the foreground.
  - I can not click on any dialog buttons.
  - I can not type in any test areas (such as in gedit).

  What I can do:
  - I can start the activities view by clicking on Activities in the top left 
corner.
  - I can launch programs from the dock and from the applications button.
  - I can also interact with the notifications area or the indicator icons at 
the right of the topbar.
  - I can type and search for applications after entering the Activities 
overview.

  Logging-out and loggin-in does not resolve the problem.
  - Note that GDM accepts mouse and keyboard inputs.
  - After logging back into the desktop, I can not interact with the desktop 
area, as before.

  Restating is the only way to regain ability to interact with the
  windows and desktop area.

  I experience this issue on my laptop running Ubuntu 17.10, but I have
  not had this issue on my desktop running Ubuntu 17.10.

  Additional Information (Laptop):
    2017 HP Spectre x360 Convertible Laptop - 15t touch
    GeForce MX150
    Using xserver-xorg 1:7.7+19ubuntu3 amd64
    Using Nvidia binary driver version 384.90
    $ lsb_release -rd
    Description:Ubuntu 17.10
    Release:17.10
    $ gnome-shell --version
    GNOME Shell 3.26.1
    $ mutter --version
    mutter 3.26.1

  Note: My desktop (which does not have this issue) is also running
  Ubuntu 17.10, has an Nvidia card, and is using the proprietary driver
  with xorg.

  I'm not sure if mutter is responsible for handling mouse/keyboard
  inputs separately from GDM, extensions, and the topbar, so I opened
  this bug against gnome-shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 14:19:45 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.gedit.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-01-16 Thread Jefferson H. Xavier
Same issue in here on Ubuntu 18.04.1 LTS. I have a Dell G3 3579 with Nvidia 
Geforce 1050TI. I've tried to use a Samsung SmartTV as a secondary display 
connected to HDMI port but Gnome settings only shows laptop display. I've 
tested drivers 390, 396, 410, and 415 without success. This issue doesn't 
occurs using lightdm instead of gdm3.
I think developers have to solve this issue that has been reporting since 
2017-09-13 and people who wants do use a external HDMI TV/Monitor to play 
games, like me, will face this issue.

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

Title:
  gdm3, hybrid nvidia with modeset=1, no external monitors detected

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gdm3 package in Debian:
  New

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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


[Desktop-packages] [Bug 1812132] [NEW] Does not return results with files that have hyphens in the filename

2019-01-16 Thread Alex Cabal
Public bug reported:

On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome
Shell), tracker does not return any files if there is a hyphen (-) in
the search string.

To recreate:

- Create a file named `foo-bar`.

- Press  to open Overview.

- Type foo. Observe that the `foo-bar` file appears.

- Type foo-. Observe that the overview says "No results."

This is a regression as files with hyphens in the filename were included
in search results in 16.04.

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

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

Title:
  Does not return results with files that have hyphens in the filename

Status in tracker package in Ubuntu:
  New

Bug description:
  On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome
  Shell), tracker does not return any files if there is a hyphen (-) in
  the search string.

  To recreate:

  - Create a file named `foo-bar`.

  - Press  to open Overview.

  - Type foo. Observe that the `foo-bar` file appears.

  - Type foo-. Observe that the overview says "No results."

  This is a regression as files with hyphens in the filename were
  included in search results in 16.04.

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

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


[Desktop-packages] [Bug 1812132] Re: Does not return results with files that have hyphens in the filename

2019-01-16 Thread Alex Cabal
Note: This only occurs if the file is in a search location that was
manually added.

For example:

- Open the Settings app

- Select Search in the left hand sidebar

- Ensure Files is On

- Press the gear at the lower right of the dialog to open Search
Locations

- Select the Other tab

- Add a new search location, for example ~/projects/

This bug seems to only affect files in such locations. If, for example,
Home is On in the Places tab, files with dashes appear in search
results.

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

Title:
  Does not return results with files that have hyphens in the filename

Status in tracker package in Ubuntu:
  New

Bug description:
  On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome
  Shell), tracker does not return any files if there is a hyphen (-) in
  the search string.

  To recreate:

  - Create a file named `foo-bar`.

  - Press  to open Overview.

  - Type foo. Observe that the `foo-bar` file appears.

  - Type foo-. Observe that the overview says "No results."

  This is a regression as files with hyphens in the filename were
  included in search results in 16.04.

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

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


[Desktop-packages] [Bug 1371613] Re: Backup result message nonsense when some folders failed AND a verification test was done

2019-01-16 Thread Michael Terry
** Changed in: deja-dup
   Status: Fix Committed => Fix Released

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

Title:
  Backup result message nonsense when some folders failed AND a
  verification test was done

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  New

Bug description:
  There are two bugs here; I'm describing the second, layered on the
  first:

  The first is that even though I have explicitly listed ~/.cache in the
  folders to ignore, I get a complaint that it failed to back up
  something in .cache.

  the second bug is that when it does a password/restore verification
  test (which it does every two months), I end up with a completion
  message that makes no sense: it tells me that the test succeeded, but
  then lists a couple of files, suggesting maybe that they were the only
  ones which were backed up? Or the only ones for which the restore test
  was successful?

  See attached graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 19 09:45:48 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1371613/+subscriptions

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


[Desktop-packages] [Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

2019-01-16 Thread Michael Terry
** Changed in: deja-dup
   Status: Fix Committed => Fix Released

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

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Fix Released
Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions

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


[Desktop-packages] [Bug 1799714] Re: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from _meta_idle_monitor_watch_fire() from idle

2019-01-16 Thread Daniel van Vugt
** Tags added: disco

** Tags added: bionic

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

Title:
  gnome-shell crashed with SIGTRAP in gjs_callback_closure() from
  ffi_closure_unix64_inner() from ffi_closure_unix64() from
  _meta_idle_monitor_watch_fire() from idle_monitor_dispatch_timeout()
  while logging {"Function IdleMonitorWatchFunc terminated with
  uncatchable exception"}

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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


[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-01-16 Thread Daniel van Vugt
Interesting that I don't see any reports of this bug from 18.10 and
later. Is that correct?

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

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


[Desktop-packages] [Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep

2019-01-16 Thread Daniel van Vugt
** Description changed:

+ https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/8
+ 
+ ---
+ 
  Steps:
  
  1. Start Rhythmbox and play music
  2. Press Print Screen in keyboard
  3. Music stops and cannot be played again in Rhythmbox
  4. If the music does not stop from the first time try step 2 again and again 
until it stops
  
  I can navigate the UI of Rhythmbox, but I cannot play music. I have to
  kill the sleeping process in order to play music.
  
  I can reproduce this bug in Totem and Clementine too.
  
  Clementine and Totem present this error:
  
  pa_stream_writable_size() failed: Connection terminated
  
  This bug affects Bionic too.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  amr9438 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  amr9438 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 14:42:55 2018
  InstallationDate: Installed on 2017-06-21 (296 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09

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

Title:
  Pressing Print Screen in keyboard makes Rhythmbox go to sleep

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/8

  ---

  Steps:

  1. Start Rhythmbox and play music
  2. Press Print Screen in keyboard
  3. Music stops and cannot be played again in Rhythmbox
  4. If the music does not stop from the first time try step 2 again and again 
until it stops

  I can navigate the UI of Rhythmbox, but I cannot play music. I have to
  kill the sleeping process in order to play music.

  I can reproduce this bug in Totem and Clementine too.

  Clementine and Totem present this error:

  pa_stream_writable_size() failed: Connection terminated

  This bug affects Bionic too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr9438 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 14:42:55 2018
  InstallationDate: Installed on 2017-06-21 (296 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09

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

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

[Desktop-packages] [Bug 1730229] Re: Desktop stops accepting input from mouse, keyboard, touchpad, or touchscreen, but topbar and dock still accept input

2019-01-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1181666 ***
https://bugs.launchpad.net/bugs/1181666

Even if the original reporter agrees that the duplicate status is wrong,
then this bug would still be closed because 17.10 is past end-of-life.

So if you experience ongoing problems and think they are different to
bug 1181666 then please open a new bug by running:

  ubuntu-bug gnome-shell

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

Title:
  Desktop stops accepting input from mouse, keyboard, touchpad, or
  touchscreen, but topbar and dock still accept input

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The desktop area stops accepting inputs from the mouse, keyboard,
  trackpad, and touchscreen.

  However, gnome session is not frozen, because I can still interact
  with the topbar and the Ubuntu Dock using the pointer or keyboard.

  I can move the pointer using the trackpad, or attached mouse, but
  clicking or typing in windows on the desktop area has no effect.

  What I can not do:
  - I can not close windows using the window buttons.
  - I can not move windows.
  - I can not bring windows to the foreground.
  - I can not click on any dialog buttons.
  - I can not type in any test areas (such as in gedit).

  What I can do:
  - I can start the activities view by clicking on Activities in the top left 
corner.
  - I can launch programs from the dock and from the applications button.
  - I can also interact with the notifications area or the indicator icons at 
the right of the topbar.
  - I can type and search for applications after entering the Activities 
overview.

  Logging-out and loggin-in does not resolve the problem.
  - Note that GDM accepts mouse and keyboard inputs.
  - After logging back into the desktop, I can not interact with the desktop 
area, as before.

  Restating is the only way to regain ability to interact with the
  windows and desktop area.

  I experience this issue on my laptop running Ubuntu 17.10, but I have
  not had this issue on my desktop running Ubuntu 17.10.

  Additional Information (Laptop):
    2017 HP Spectre x360 Convertible Laptop - 15t touch
    GeForce MX150
    Using xserver-xorg 1:7.7+19ubuntu3 amd64
    Using Nvidia binary driver version 384.90
    $ lsb_release -rd
    Description:Ubuntu 17.10
    Release:17.10
    $ gnome-shell --version
    GNOME Shell 3.26.1
    $ mutter --version
    mutter 3.26.1

  Note: My desktop (which does not have this issue) is also running
  Ubuntu 17.10, has an Nvidia card, and is using the proprietary driver
  with xorg.

  I'm not sure if mutter is responsible for handling mouse/keyboard
  inputs separately from GDM, extensions, and the topbar, so I opened
  this bug against gnome-shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 14:19:45 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.gedit.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1803527] Re: ubuntu 18.10 fails to restore from suspend if no password

2019-01-16 Thread Daniel van Vugt
Please wait until bug 1769383 is declared fixed for 18.10 and then we
can see if the problem still occurs.

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

Title:
  ubuntu 18.10 fails to restore from suspend if no password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  my system:
  ubuntu 18.10
  4k monitor with 1 scale and 1.5 font scale
  nvidia 410 and 390 drivers are checked

  when happened:
  lock screen or suspend. return after that.
  if I have user password prompt enabled: everything ok
  if I haven't user password prompt enabled, system started with gnome crashed

  I expect:
  ubuntu to has the same behaviour either I have a password either not.

  What happened:
  in case of no password (I should just 'swipe up' or press 'space' and 
everything should be ready.. but) most of the times I can not return to desktop.
  - freezes on a screen with panels but no desktop
  - freezes on a purple screen that no command is working (as ctrl+alt+t)
  - freezes on a useless gnome panels (dash and topbar) mode

  solution chosen:
  I press ctrl+alt+F1 to change environment, I enter my password... BUT again 
the gnome is too slow, app icon is always on and everything is acting weird 
(some apps' icon that I have opened on the other session is liked pined on dash 
without have the option to unpin it - like I see it but it is not pinned)
  So, I just save what I can through the new session and just restart the pc 
(in new session is available - in the previous is only suspend available)

  frequency: about 80% of the times. If lock-screen showed up normally
  (and I have to press space to unlock) everything works like a charm
  afterwards. If not.. it will be the mess I described above

  hope it helps
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-08-28 (84 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (32 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://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   >