date:20190626

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

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

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

Title:
  Totem shows wrong frame when pausing

Status in Totem:
  Incomplete
Status in totem package in Ubuntu:
  Expired

Bug description:
  REOPENED BUG #964555

  Basically when I watch a video and use the seeker to move back and
  then pause, Totem will "jump" back to the location I moved it to,
  resuming the video will start from that wrong location again.

  Steps to reproduce:
  1. Select a video and play it.
  2. Pause the video.
  3. Move the seeker backwards to some random location.
  4. Resume the video.
  5. Pause the video again.

  Sometimes it will show you the location you have moved back to.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: totem 3.0.1-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Mar 25 15:50:04 2012
  ExecutablePath: /usr/bin/totem
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

2019-06-26 Thread Book 'em Dano

** Tags added: disco

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

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

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

[Desktop-packages] [Bug 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

2019-06-26 Thread Book 'em Dano

** Attachment added: "troubleshoot-logs.txt"
   
https://bugs.launchpad.net/hplip/+bug/1834400/+attachment/5273697/+files/troubleshoot-logs.txt

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

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

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

[Desktop-packages] [Bug 1834400] [NEW] pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

2019-06-26 Thread Book 'em Dano

Public bug reported:

I attempted to print a file on a network printer which was set up via
HPLIP. The PC reports that the print job has started and completed on
the network printer, but in fact the network printer has not printed
anything.

** Affects: hplip
 Importance: Undecided
 Status: New

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

** Attachment added: "troubleshoot.txt"
   
https://bugs.launchpad.net/bugs/1834400/+attachment/5273695/+files/troubleshoot.txt

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

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

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

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

Re: [Desktop-packages] [Bug 1834375] Re: Gaia.com videos unsupported

2019-06-26 Thread Robert James

Thanks for the prompt response, Daniel.  Gaia deserves it.  You're doing a good 
thing for Ubuntu users.
Bob

On Wednesday, June 26, 2019, 10:15:39 PM EDT, Daniel van Vugt 
 wrote:  
 
 ** Package changed: xorg (Ubuntu) => firefox (Ubuntu)

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1834375

Title:
  Gaia.com videos unsupported

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox could not play videos on Gaia.com.  The error message blamed
  the browser.  So I downloaded and installed the browser Opera, with
  the same results and message.  Both browsers would play Youtube
  videos.

  Please enable Gaia.com videos.

  Thanks.

  I downloaded the latest Ubuntu release today.  18.04...something

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun 26 17:57:24 2019
  DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
  Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
    Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
    Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
  InstallationDate: Installed on 2019-06-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago)
  dmi.bios.date: 06/23/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G2 v02.02
  dmi.board.name: 3048h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v02.02:bd06/23/2011:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Jun 26 10:11:57 2019
  xserver.configfile: default
  xserver.errors:
  
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

Title:
  Gaia.com videos unsupported

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox could not play videos on Gaia.com.  The error message blamed
  the browser.  So I downloaded and installed the browser Opera, with
  the same results and message.  Both browsers would play Youtube
  videos.

  Please enable Gaia.com videos.

  Thanks.

  I downloaded the latest Ubuntu release today.  18.04...something

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun 26 17:57:24 2019
  DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
  InstallationDate: Installed on 2019-06-25 (1 days ago)

[Desktop-packages] [Bug 1668309] Re: Scaling on xps13 means only a part of the screen is visible at any time.

2019-06-26 Thread No Mat

Can confirm comment #5. Fails as described on a Macbook Pro with Retina
display (2560x1600) in Ubuntu 18.04.

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

Title:
  Scaling on xps13 means only a part of the screen is visible at any
  time.

Status in vino package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. On a 4K system
  2. Do a default install of the current iso for Zesty
  3. Make sure scalling is set to 2
  4. Once in the user session activate desktop-sharing
  5. Connect from another machine

  EXPECTED:
  I expect to see the whole screen or for the screen to scroll to allow access 
to the whole screen

  ACTUAL:
  Top left hand quarter is the only thing visible and no changes to remina make 
it better.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2016-11-09 (109 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161109)
  Package: vino 3.8.1-0ubuntu12
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1834110] Re: Broken lock-screen wallpaper, stutter after resuming from hibernation

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

Thanks. It's the same bug in this case.

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

Title:
  Broken lock-screen wallpaper, stutter after resuming from hibernation

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Very similar to Bug #1809407
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407).

  I set up my swap partition and tested hibernation on 19.04 /w Nvidia
  drivers.

  Basically I observed 2 things:
  - Lock screen wallpaper gone (black screen with clock), same as with #1809407
  - Desktop wallpaper seems okay
  - Big frame rate drops (despite performance governor), everything seems quite 
laggy

  I'm new to Linux/Ubuntu, if you need any logs please tell me the
  commands and I will attach them.

  Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-06-20 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: mutter 3.32.1-2ubuntu1~19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-19.20-generic 5.0.8
  Tags:  disco
  Uname: Linux 5.0.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

** Summary changed:

- [nvidia] Corrupted wallpaper after resuming from suspend
+ [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  Confirmed
Status in mutter source package in Disco:
  Confirmed
Status in mutter source package in Eoan:
  In Progress

Bug description:
  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1834375] Re: Gaia.com videos unsupported

** Package changed: xorg (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/1834375

Title:
  Gaia.com videos unsupported

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox could not play videos on Gaia.com.  The error message blamed
  the browser.  So I downloaded and installed the browser Opera, with
  the same results and message.  Both browsers would play Youtube
  videos.

  Please enable Gaia.com videos.

  Thanks.

  I downloaded the latest Ubuntu release today.  18.04...something

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun 26 17:57:24 2019
  DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
  InstallationDate: Installed on 2019-06-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago)
  dmi.bios.date: 06/23/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G2 v02.02
  dmi.board.name: 3048h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v02.02:bd06/23/2011:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Jun 26 10:11:57 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1720730] Re: Feature Request: proper "Auto-hide" for Ubuntu Dock, not just "Intelli-hide".

Please open an issue for this feature request upstream:

  https://github.com/micheleg/dash-to-dock/issues

and then tell us the new issue ID.

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

Title:
  Feature Request: proper "Auto-hide" for Ubuntu Dock, not just
  "Intelli-hide".

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

Bug description:
  Wasn't sure if I was supposed to file this feature request under the
  Ubuntu Dock GNOME shell extension or here.

  BEHAVIOR
  Currently, Enabling "Auto-hide" in the Dock section of GNOME control center 
actually "intelli-hides" the dock, so that it always is present if no windows 
are near it.

  EXPECTED BEHAVIOR
  For their to be an option somewhere in the dock settings to be able to enable 
genuine Auto-hide for users who want the Ubuntu Dock hidden even if there are 
no windows near it.

  Feature requested while using:
  Ubuntu 17.10 beta 2
  GNOME Control Center 3.26.0

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

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

[Desktop-packages] [Bug 1720730] Re: Feature Request: proper "Auto-hide" for Ubuntu Dock, not just "Intelli-hide".

** Tags removed: artful
** Tags added: bionic disco eoan

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

Title:
  Feature Request: proper "Auto-hide" for Ubuntu Dock, not just
  "Intelli-hide".

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

Bug description:
  Wasn't sure if I was supposed to file this feature request under the
  Ubuntu Dock GNOME shell extension or here.

  BEHAVIOR
  Currently, Enabling "Auto-hide" in the Dock section of GNOME control center 
actually "intelli-hides" the dock, so that it always is present if no windows 
are near it.

  EXPECTED BEHAVIOR
  For their to be an option somewhere in the dock settings to be able to enable 
genuine Auto-hide for users who want the Ubuntu Dock hidden even if there are 
no windows near it.

  Feature requested while using:
  Ubuntu 17.10 beta 2
  GNOME Control Center 3.26.0

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

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

[Desktop-packages] [Bug 1834388] [NEW] package firefox-locale-zh-hans 66.0.3+build1-0ubuntu0.16.04.1 failed to install/upgrade: 正试图覆盖 /usr/lib/firefox，它同时被包含于软件包 firefox-locale-en 66.0.3+build1-0ubunt

2019-06-26 Thread tang shang

Public bug reported:

I often recieved this error warning after opening computer

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: firefox-locale-zh-hans 66.0.3+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  upc3093 F pulseaudio
 /dev/snd/controlC0:  upc3093 F pulseaudio
Channel: Unavailable
Date: Wed Jun 26 06:48:07 2019
Dependencies:
 
ErrorMessage: 正试图覆盖 /usr/lib/firefox，它同时被包含于软件包 firefox-locale-en 
66.0.3+build1-0ubuntu0.16.04.1
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-03-27 (456 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
IpRoute:
 default via 180.201.128.1 dev enp0s31f6  proto static  metric 100 
 169.254.0.0/16 dev enp0s31f6  scope link  metric 1000 
 180.201.128.0/18 dev enp0s31f6  proto kernel  scope link  src 180.201.140.117  
metric 100
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.29ubuntu0.1
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox-locale-zh-hans 66.0.3+build1-0ubuntu0.16.04.1 failed to 
install/upgrade: 正试图覆盖 /usr/lib/firefox，它同时被包含于软件包 firefox-locale-en 
66.0.3+build1-0ubuntu0.16.04.1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/23/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1009
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z270-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.:bvr1009:bd07/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package xenial

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

Title:
  package firefox-locale-zh-hans 66.0.3+build1-0ubuntu0.16.04.1 failed
  to install/upgrade: 正试图覆盖 /usr/lib/firefox，它同时被包含于软件包 firefox-locale-
  en 66.0.3+build1-0ubuntu0.16.04.1

Status in firefox package in Ubuntu:
  New

Bug description:
  I often recieved this error warning after opening computer

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: firefox-locale-zh-hans 66.0.3+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  upc3093 F pulseaudio
   /dev/snd/controlC0:  upc3093 F pulseaudio
  Channel: Unavailable
  Date: Wed Jun 26 06:48:07 2019
  Dependencies:
   
  ErrorMessage: 正试图覆盖 /usr/lib/firefox，它同时被包含于软件包 firefox-locale-en 
66.0.3+build1-0ubuntu0.16.04.1
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-27 (456 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IpRoute:
   default via 180.201.128.1 dev enp0s31f6  proto static  metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000 
   180.201.128.0/18 dev enp0s31f6  proto kernel  scope link  src 
180.201.140.117  metric 100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.29ubuntu0.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox-locale-zh-hans 66.0.3+build1-0ubuntu0.16.04.1 failed 
to install/upgrade: 正试图覆盖 /usr/lib/firefox，它同时被包含于软件包 firefox-locale-en 
66.0.3+build1-0ubuntu0.16.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1009
  dmi.board.asset.tag:

[Desktop-packages] [Bug 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)

2019-06-26 Thread roussel geoffrey

I also have an issue with the thumbnailer but it only occurs using Nemo
file browser and only when browsing SMB share folder:

https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1834386

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

Title:
  thumbnailer cannot create tempfiles (with apparmor denials)

Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Cosmic:
  Fix Released
Status in evince source package in Disco:
  Fix Released
Status in evince package in Debian:
  Fix Released

Bug description:
  * Impact

  Nautilus fails to generate previews for pdf files

  * Test case

  Download/copy a pdf, open the directory in nautilus, a preview image
  should be displayed

  * Regression potential

  Check that there are no other apparmor denials and the thumbnailer
  works

  
  -

  While trying to create thumbnails in a directory from within nautilus,
  I got:

  [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 14:59:00 2018
  InstallationDate: Installed on 2014-06-19 (1580 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago)

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

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

[Desktop-packages] [Bug 1834385] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1834385/+attachment/5273640/+files/StacktraceSource.txt

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

Title:
  gnome-software crashed with SIGSEGV

Status in gnome-software package in Ubuntu:
  New

Bug description:
  shown this bug after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 25 21:08:01 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-06-18 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f748a1f87c1:mov0x130(%r12),%r8d
   PC (0x7f748a1f87c1) ok
   source "0x130(%r12)" (0x0130) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-software crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
  separator:

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

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

[Desktop-packages] [Bug 1834385] StacktraceTop.txt

** Attachment added: "StacktraceTop.txt"
   
https://bugs.launchpad.net/bugs/1834385/+attachment/5273641/+files/StacktraceTop.txt

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

Title:
  gnome-software crashed with SIGSEGV

Status in gnome-software package in Ubuntu:
  New

Bug description:
  shown this bug after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 25 21:08:01 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-06-18 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f748a1f87c1:mov0x130(%r12),%r8d
   PC (0x7f748a1f87c1) ok
   source "0x130(%r12)" (0x0130) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-software crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
  separator:

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

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

[Desktop-packages] [Bug 1834385] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1834385/+attachment/5273642/+files/ThreadStacktrace.txt

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

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-software crashed with SIGSEGV

Status in gnome-software package in Ubuntu:
  New

Bug description:
  shown this bug after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 25 21:08:01 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-06-18 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f748a1f87c1:mov0x130(%r12),%r8d
   PC (0x7f748a1f87c1) ok
   source "0x130(%r12)" (0x0130) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-software crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
  separator:

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

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

[Desktop-packages] [Bug 1834385] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1834385/+attachment/5273639/+files/Stacktrace.txt

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

Title:
  gnome-software crashed with SIGSEGV

Status in gnome-software package in Ubuntu:
  New

Bug description:
  shown this bug after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 25 21:08:01 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-06-18 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f748a1f87c1:mov0x130(%r12),%r8d
   PC (0x7f748a1f87c1) ok
   source "0x130(%r12)" (0x0130) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-software crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
  separator:

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

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

[Desktop-packages] [Bug 1834385] [NEW] gnome-software crashed with SIGSEGV

2019-06-26 Thread Anas

Public bug reported:

shown this bug after a reboot

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu8
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 25 21:08:01 2019
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2019-06-18 (8 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.30.6-2ubuntu8
ProcCmdline: /usr/bin/gnome-software --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f748a1f87c1:  mov0x130(%r12),%r8d
 PC (0x7f748a1f87c1) ok
 source "0x130(%r12)" (0x0130) not located in a known VMA region (needed 
readable region)!
 destination "%r8d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
 ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
 ?? ()
 ?? ()
 ?? ()
Title: gnome-software crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
separator:

** Affects: gnome-software (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash eoan

** Information type changed from Private to Public

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

Title:
  gnome-software crashed with SIGSEGV

Status in gnome-software package in Ubuntu:
  New

Bug description:
  shown this bug after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 25 21:08:01 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-06-18 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f748a1f87c1:mov0x130(%r12),%r8d
   PC (0x7f748a1f87c1) ok
   source "0x130(%r12)" (0x0130) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? () from /lib/x86_64-linux-gnu/libostree-1.so.1
   ?? ()
   ?? ()
   ?? ()
  Title: gnome-software crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
  separator:

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

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

[Desktop-packages] [Bug 1834386] [NEW] Ebooks thumbnails fail in Nemo over SMB

2019-06-26 Thread roussel geoffrey

Public bug reported:

Nemo is unable to generate ebooks thumbnails over SMB share because of
evince-thumbnailer apparmor profile(note that Nautilus is able to do it
anyway), i removed apparmor to see and it fixed that issue.

Nemo output when generating thumbs:
-
(nemo:31811): CinnamonDesktop-WARNING **: 01:08:30.200: Error creating 
thumbnail for 
smb://akem-hp.local/comics_bds_mangas/Scrooge/Uncle%20Scrooge%20(001-100)%20GetComics.INFO/029%20Uncle%20Scrooge.cbr:
 Unrecognized image file format
Error loading remote document: An AppArmor policy prevents this sender from 
sending this message to this recipient; type="method_call", sender=":1.243" 
(uid=1000 pid=1488 comm="evince-thumbnailer -s 128 smb://akem-hp.local/comi" 
label="/usr/bin/evince-thumbnailer (enforce)") 
interface="org.gtk.vfs.MountTracker" member="LookupMount" error name="(unset)" 
requested_reply="0" destination=":1.10" (uid=1000 pid=1725 
comm="/usr/lib/gvfs/gvfsd " label="unconfined")
 
(nemo:31811): CinnamonDesktop-WARNING **: 01:08:30.365: Unable to create loader 
for mime type application/x-cbr: Unrecognized image file format
-
Note that it does the same with pdf or some other ebooks format.

The problem happens in loopback too, just share a folder with ebooks
using SMB, flush the thumbnails and open Nemo to that folder via
Network(connect to the SMB).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evince 3.28.4-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jun 27 02:11:28 2019
InstallationDate: Installed on 2019-05-31 (26 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Ebooks thumbnails fail in Nemo over SMB

Status in evince package in Ubuntu:
  New

Bug description:
  Nemo is unable to generate ebooks thumbnails over SMB share because of
  evince-thumbnailer apparmor profile(note that Nautilus is able to do
  it anyway), i removed apparmor to see and it fixed that issue.

  Nemo output when generating thumbs:
  -
  (nemo:31811): CinnamonDesktop-WARNING **: 01:08:30.200: Error creating 
thumbnail for 
smb://akem-hp.local/comics_bds_mangas/Scrooge/Uncle%20Scrooge%20(001-100)%20GetComics.INFO/029%20Uncle%20Scrooge.cbr:
 Unrecognized image file format
  Error loading remote document: An AppArmor policy prevents this sender from 
sending this message to this recipient; type="method_call", sender=":1.243" 
(uid=1000 pid=1488 comm="evince-thumbnailer -s 128 smb://akem-hp.local/comi" 
label="/usr/bin/evince-thumbnailer (enforce)") 
interface="org.gtk.vfs.MountTracker" member="LookupMount" error name="(unset)" 
requested_reply="0" destination=":1.10" (uid=1000 pid=1725 
comm="/usr/lib/gvfs/gvfsd " label="unconfined")
   
  (nemo:31811): CinnamonDesktop-WARNING **: 01:08:30.365: Unable to create 
loader for mime type application/x-cbr: Unrecognized image file format
  -
  Note that it does the same with pdf or some other ebooks format.

  The problem happens in loopback too, just share a folder with ebooks
  using SMB, flush the thumbnails and open Nemo to that folder via
  Network(connect to the SMB).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jun 27 02:11:28 2019
  InstallationDate: Installed on 2019-05-31 (26 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1724075] Re: gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()

** Tags added: eoan

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

Title:
  gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I was transferring a download to my android when then notice came up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 15:41:45 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2017-10-13 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 
/org/gtk/gvfs/exec_spaw/12
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7ff9a80718a7 <__strlen_avx2+55>: vpcmpeqb 
(%rdi),%ymm0,%ymm1
   PC (0x7ff9a80718a7) ok
   source "(%rdi)" (0x59dc5460) not located in a known VMA region (needed 
readable region)!
   destination "%ymm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:93
   ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Filemetadata () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Files_And_Folders () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
  Title: gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()
  UpgradeStatus: Upgraded to artful on 2017-10-15 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1834383] Re: gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()

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

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 #1724075, 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/1834383/+attachment/5273612/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724075
   gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()

Status in gvfs package in Ubuntu:
  New

Bug description:
  shown this bug after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gvfs-backends 1.40.1-1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 22 22:20:41 2019
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2019-06-18 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/9
  SegvAnalysis:
   Segfault happened at: 0x7f9d2ed570c7 <__strlen_avx2+55>: vpcmpeqb 
(%rdi),%ymm0,%ymm1
   PC (0x7f9d2ed570c7) ok
   source "(%rdi)" (0x5cf80ea0) not located in a known VMA region (needed 
readable region)!
   destination "%ymm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:96
   ?? () from /lib/x86_64-linux-gnu/libmtp.so.9
   ?? () from /lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Filemetadata () from /lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Files_And_Folders () from /lib/x86_64-linux-gnu/libmtp.so.9
  Title: gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
  separator:

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

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

[Desktop-packages] [Bug 1834383] [NEW] gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()

2019-06-26 Thread Anas

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

Public bug reported:

shown this bug after a reboot

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gvfs-backends 1.40.1-1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 22 22:20:41 2019
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2019-06-18 (8 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/9
SegvAnalysis:
 Segfault happened at: 0x7f9d2ed570c7 <__strlen_avx2+55>:   vpcmpeqb 
(%rdi),%ymm0,%ymm1
 PC (0x7f9d2ed570c7) ok
 source "(%rdi)" (0x5cf80ea0) not located in a known VMA region (needed 
readable region)!
 destination "%ymm0" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:96
 ?? () from /lib/x86_64-linux-gnu/libmtp.so.9
 ?? () from /lib/x86_64-linux-gnu/libmtp.so.9
 LIBMTP_Get_Filemetadata () from /lib/x86_64-linux-gnu/libmtp.so.9
 LIBMTP_Get_Files_And_Folders () from /lib/x86_64-linux-gnu/libmtp.so.9
Title: gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
separator:

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


** Tags: amd64 apport-crash eoan

** Information type changed from Private to Public

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

Title:
  gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()

Status in gvfs package in Ubuntu:
  New

Bug description:
  shown this bug after a reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gvfs-backends 1.40.1-1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 22 22:20:41 2019
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2019-06-18 (8 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/9
  SegvAnalysis:
   Segfault happened at: 0x7f9d2ed570c7 <__strlen_avx2+55>: vpcmpeqb 
(%rdi),%ymm0,%ymm1
   PC (0x7f9d2ed570c7) ok
   source "(%rdi)" (0x5cf80ea0) not located in a known VMA region (needed 
readable region)!
   destination "%ymm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:96
   ?? () from /lib/x86_64-linux-gnu/libmtp.so.9
   ?? () from /lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Filemetadata () from /lib/x86_64-linux-gnu/libmtp.so.9
   LIBMTP_Get_Files_And_Folders () from /lib/x86_64-linux-gnu/libmtp.so.9
  Title: gvfsd-mtp crashed with SIGSEGV in __strlen_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxsf 
vboxusers
  separator:

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

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

[Desktop-packages] [Bug 1834264] Re: PCI/internal sound card not detected

2019-06-26 Thread Hui Wang

According to the #17 and you said "it was workig fine until today", it
looks like this is a hardware issue. Probably the hardware of audio was
broken.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I don't have any sound.  I have followed some online instructions that
  have not worked.  Please help me.  My laptop was working just fine
  until today.  I opened it up and there was no sound.  If you need
  further information from me, please provide instructions on how to
  obtain it.  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 25 18:29:31 2019
  InstallationDate: Installed on 2019-02-18 (127 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8364
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc0xx
  dmi.product.sku: 1KU13UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034

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

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

[Desktop-packages] [Bug 1834367] Re: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible()

** Changed in: nautilus
   Status: Unknown => New

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

Title:
  nautilus crashed with SIGSEGV in
  gtk_places_sidebar_set_drop_targets_visible()

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

Bug description:
  I was moving movies from one directory to another directory with
  mouse.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  Uname: Linux 5.1.15-050115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 15:49:12 2019
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-12-02 (206 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1f91d44914 
:mov0xe8(%rdi),%eax
   PC (0x7f1f91d44914) ok
   source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_places_sidebar_set_drop_targets_visible () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
gtk_places_sidebar_set_drop_targets_visible()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1777285] Re: Batch libreoffice --convert-to offers no way to wait for document completion

** Changed in: df-libreoffice
   Status: Confirmed => New

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

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

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

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+subscriptions

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

[Desktop-packages] [Bug 1777285]

2019-06-26 Thread Richard Elkins

The command (OString cmd) is executed in background through a pipe no
matter what.  The difference is that in Mac and Windows, the foreground
process waits (blocked) while in Linux and Unix, the foreground process
continues to the exit.

Pardon my misuse of terminology.

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

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

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

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+subscriptions

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

[Desktop-packages] [Bug 1777285]

2019-06-26 Thread Xiscofauli

Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.

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

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

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

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+subscriptions

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

[Desktop-packages] [Bug 1777285]

2019-06-26 Thread Richard Elkins

Seriously, I am not trying to make work for anyone.  We are all busy and
I do not want to be a pest.

If the #ifdef LINUX for Linux and Unix in shellexec.cxx has a purpose,
I'd like to know.  I can live with my `sleep` logic.

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

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

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

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+subscriptions

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

[Desktop-packages] [Bug 1777285]

2019-06-26 Thread Richard Elkins

Yes, I have tried this with the latest download.  This is an off-the-
shelf Xubuntu 18.04.latest LTS desktop that I use primarily for
Libreoffice, browsing, and Python development.  I tend to stay with
Ubuntu's packages including Libreoffice.

Please see comment #9.

The current source code has special #ifdef LINUX logic to fork the
transaction into background and then immediately exit to the command
line.  It does not wait for the ODT file to be ready for use.  Hence,
any Linux/Unix bash command that references the ODT file will definitely
fail with file not found.  Workaround: sleep for 2/3 seconds before
trying to access the ODT file.

For Mac and Windows, the transaction takes place in foreground so that
when soffice.bin exits to the O/S, the ODT file is guaranteed to be
available for use.  This is the desirable effect for all O/Ses.

Why is there more concern with "blocking" in the Unix/Linux environments
as opposed to Mac (Unix bash environment) and Windows?

IMO, this is a bug for the Linux environment.  There is no reason for
special #ifdef LINUX logic.

Has anyone else tried the above script yourself using a Linux desktop
with the current or recent Libreoffice?

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

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

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

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+subscriptions

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

[Desktop-packages] [Bug 1118446] Re: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted

2019-06-26 Thread peitian

I want to know which versifon fixed the bug. I installed network-manager
0.9.8.8-0ubuntu7.3 but still occurs this issue.

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

Title:
  NetworkManager[14155]:  nl_recvmsgs() error: (-33) Dump
  inconsistency detected, interrupted

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I see the following messages in /var/log/syslog:
NetworkManager[14155]:  nl_recvmsgs() error: (-33) Dump inconsistency 
detected, interrupted

  When it goes down, I have to bounce network-manager to resolve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Thu Feb  7 08:59:00 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-01-26 (12 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 10.0.1.1 dev wlan0  proto static 
   10.0.1.0/24 dev wlan0  proto kernel  scope link  src 10.0.1.11  metric 9 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to raring on 2013-01-26 (11 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Ubuntuac3b296c-3250-4464-8ee0-ebd6e5d8e9ca   
802-11-wireless   1360249035   Thu 07 Feb 2013 08:57:15 AM CSTyes   
no /org/freedesktop/NetworkManager/Settings/2
   Palms 2e5ef890-c77c-466e-92ee-d9dcb777cf12   
802-11-wireless   1359750784   Fri 01 Feb 2013 02:33:04 PM CSTyes   
no /org/freedesktop/NetworkManager/Settings/1
   MIA-WiFi  ea25a58d-9cb8-48a8-843a-2dc3231a1e17   
802-11-wireless   1359754973   Fri 01 Feb 2013 03:42:53 PM CSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.7.995  connected   enabled   enabled 
enabledenabled enabled

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

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

[Desktop-packages] [Bug 1834378] [NEW] two-finger scrolling "jumps" unpredictably

2019-06-26 Thread Daniel McCloy

Public bug reported:

When attempting 2-finger scrolling, it often happens that the document /
webpage will scroll down by more than a full screen height at the
instant I first lay fingers on the touchpad. This happens across
multiple apps (text editors, web browsers).

Note: the system (Dell Inspiron 7380) came pre-installed with Windows; I
erased the HD and installed Xubuntu 18.04 in its place.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CurrentDesktop: XFCE
Date: Wed Jun 26 14:23:35 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
InstallationDate: Installed on 2018-12-23 (185 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
Lsusb:
 Bus 002 Device 002: ID 706b:6b31  
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:6715 Microdia 
 Bus 001 Device 004: ID 8087:0025 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 7380
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-52-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.name: 0GW3KR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd08/23/2018:svnDellInc.:pnInspiron7380:pvr:rvnDellInc.:rn0GW3KR:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7380
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
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: xserver-xorg-input-synaptics (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 xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1834378

Title:
  two-finger scrolling "jumps" unpredictably

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  When attempting 2-finger scrolling, it often happens that the document
  / webpage will scroll down by more than a full screen height at the
  instant I first lay fingers on the touchpad. This happens across
  multiple apps (text editors, web browsers).

  Note: the system (Dell Inspiron 7380) came pre-installed with Windows;
  I erased the HD and installed Xubuntu 18.04 in its place.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: XFCE
  Date: Wed Jun 26 14:23:35 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-12-23 (185 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  Lsusb:
   Bus 002 Device 002: ID 706b:6b31  
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6715 Microdia 
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7380
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-52-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0GW3KR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd08/23/2018:svnDellInc.:pnInspiron7380:pvr:rvnDellInc.:rn0GW3KR:rvrA00:cvnDellInc.:ct10:cvr:

[Desktop-packages] [Bug 1834375] [NEW] Gaia.com videos unsupported

2019-06-26 Thread Robert James

Public bug reported:

Firefox could not play videos on Gaia.com.  The error message blamed the
browser.  So I downloaded and installed the browser Opera, with the same
results and message.  Both browsers would play Youtube videos.

Please enable Gaia.com videos.

Thanks.

I downloaded the latest Ubuntu release today.  18.04...something

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jun 26 17:57:24 2019
DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
   Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
InstallationDate: Installed on 2019-06-25 (1 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago)
dmi.bios.date: 06/23/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G2 v02.02
dmi.board.name: 3048h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v02.02:bd06/23/2011:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Jun 26 10:11:57 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Gaia.com videos unsupported

Status in xorg package in Ubuntu:
  New

Bug description:
  Firefox could not play videos on Gaia.com.  The error message blamed
  the browser.  So I downloaded and installed the browser Opera, with
  the same results and message.  Both browsers would play Youtube
  videos.

  Please enable Gaia.com videos.

  Thanks.

  I downloaded the latest Ubuntu release today.  18.04...something

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun 26 17:57:24 2019
  DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
  InstallationDate: Installed on 2019-06-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago)
  dmi.bios.date: 06/23/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G2 v02.02
  dmi.board.name: 3048h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias:

[Desktop-packages] [Bug 1834367] Re: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible()

2019-06-26 Thread Sebastien Bacher

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

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

Title:
  nautilus crashed with SIGSEGV in
  gtk_places_sidebar_set_drop_targets_visible()

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

Bug description:
  I was moving movies from one directory to another directory with
  mouse.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  Uname: Linux 5.1.15-050115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 15:49:12 2019
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-12-02 (206 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1f91d44914 
:mov0xe8(%rdi),%eax
   PC (0x7f1f91d44914) ok
   source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_places_sidebar_set_drop_targets_visible () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
gtk_places_sidebar_set_drop_targets_visible()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1834367] Re: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible()

2019-06-26 Thread El jinete sin cabeza

** Description changed:

- https://gitlab.gnome.org/GNOME/nautilus/issues/1082
- 
- ---
- 
- I was moving movies from one directory to another directory.
+ I was moving movies from one directory to another directory with mouse.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  Uname: Linux 5.1.15-050115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 15:49:12 2019
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-12-02 (206 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1f91d44914 
:mov0xe8(%rdi),%eax
   PC (0x7f1f91d44914) ok
   source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_places_sidebar_set_drop_targets_visible () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
gtk_places_sidebar_set_drop_targets_visible()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:
  
  usr_lib_nautilus:

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

Title:
  nautilus crashed with SIGSEGV in
  gtk_places_sidebar_set_drop_targets_visible()

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

Bug description:
  I was moving movies from one directory to another directory with
  mouse.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  Uname: Linux 5.1.15-050115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 15:49:12 2019
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-12-02 (206 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1f91d44914 
:mov0xe8(%rdi),%eax
   PC (0x7f1f91d44914) ok
   source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_places_sidebar_set_drop_targets_visible () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
gtk_places_sidebar_set_drop_targets_visible()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1834367] Re: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible()

2019-06-26 Thread El jinete sin cabeza

** Information type changed from Private to Public

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1082
   https://gitlab.gnome.org/GNOME/nautilus/issues/1082

** Also affects: nautilus via
   https://gitlab.gnome.org/GNOME/nautilus/issues/1082
   Importance: Unknown
   Status: Unknown

** Description changed:

+ https://gitlab.gnome.org/GNOME/nautilus/issues/1082
+ 
+ ---
+ 
  I was moving movies from one directory to another directory.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  Uname: Linux 5.1.15-050115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 15:49:12 2019
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-12-02 (206 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
-  PATH=(custom, no user)
-  LANGUAGE=es_CL:es
-  LANG=es_CL.UTF-8
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+  LANGUAGE=es_CL:es
+  LANG=es_CL.UTF-8
  SegvAnalysis:
-  Segfault happened at: 0x7f1f91d44914 
:mov0xe8(%rdi),%eax
-  PC (0x7f1f91d44914) ok
-  source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed 
readable region)!
-  destination "%eax" ok
+  Segfault happened at: 0x7f1f91d44914 
:mov0xe8(%rdi),%eax
+  PC (0x7f1f91d44914) ok
+  source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed 
readable region)!
+  destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
-  gtk_places_sidebar_set_drop_targets_visible () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  ()
-  g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  gtk_places_sidebar_set_drop_targets_visible () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  ()
+  g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
gtk_places_sidebar_set_drop_targets_visible()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:
-  
+ 
  usr_lib_nautilus:

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

Title:
  nautilus crashed with SIGSEGV in
  gtk_places_sidebar_set_drop_targets_visible()

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

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/1082

  ---

  I was moving movies from one directory to another directory.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  Uname: Linux 5.1.15-050115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 26 15:49:12 2019
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-12-02 (206 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f1f91d44914 
:mov0xe8(%rdi),%eax
   PC (0x7f1f91d44914) ok
   source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_places_sidebar_set_drop_targets_visible () at 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
gtk_places_sidebar_set_drop_targets_visible()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1141034] Re: RTL Spreadsheet Insert Cells

Launchpad has imported 1 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=125868.

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-06-11T20:48:38+00:00 Elicoten wrote:

Description:
Dialog option text needs to be changed for right to left spreadsheets, 
currently it could cause confusion as what it does (correctly) is actually 
opposite to what it says (but the option is mislabelled, the behaviour seems 
correct).

Steps to Reproduce:
1.Open/create a right to left spreadsheet (with some data in it)
2. Right click on a cell
3. Select "Insert..." 

Actual Results:
The second option on the dialog box says "Shift cells right".

Expected Results:
For right to left spreadsheets, this should actually say "Shift cells left"


Reproducible: Always


User Profile Reset: No


Additional Info:
The functionality works correctly, shifting cells to the left - only the dialog 
text needs to be changed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1141034/comments/3


** Changed in: df-libreoffice
   Status: Unknown => New

** Changed in: df-libreoffice
   Importance: Unknown => Low

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

Title:
  RTL Spreadsheet Insert Cells

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

Bug description:
  When using a right-to-left spreadsheet, right clicking and selected
  "insert cells" shows the normal LTR option to shift cells right,
  although when used it actually shifts cells left.

  I believe that shifting cells left is the correct behaviour in this
  case, but the text of the option should be changed to read "shift
  cells left". This was first noticed when using the Hebrew language
  user interface, but the problem is present when using English UI too.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-calc 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CheckboxSubmission: ad9a15703e19217cb3448f881e125f6a
  CheckboxSystem: abc83e3988b72e7c3a9b3aa684cb92fd
  Date: Sun Mar  3 00:47:21 2013
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-01 (305 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1141034/+subscriptions

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

[Desktop-packages] [Bug 1834366] [NEW] xdg-desktop-portal-gtk package makes the computer crawl to the knees

2019-06-26 Thread Valentin Quequet

Public bug reported:

Hi the Team!

I run Ubuntu 18.04.2 LTS (Bionic Beaver) 64-bit on Intel-based platform.

I have noticed for ages that sometimes a dozen of programs where
consuming much too CPU cycles. Amongst them were xdg-desktop-portal-gtk.
And if I "kill -STOP" the PID of xdg-desktop-portal-gtk then all calm
down and become responsive again.

If fact the most affected applications were gedit, geany, firefox,
google-chrome, and, last but not leas, the Xorg server itself!,
hindering the usability of the whole system.

Also, this bug maybe also affects default Ubuntu session/desktop/window
manager or compositor, and non default ones, possibly.

In hope this helps,
Sincerely, Valentin.

** Affects: xdg-desktop-portal-gtk (Ubuntu)
Importance: Undecided
Status: New

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

Title:
xdg-desktop-portal-gtk package makes the computer crawl to the knees

Status in xdg-desktop-portal-gtk package in Ubuntu:
New

Bug description:
Hi the Team!

I run Ubuntu 18.04.2 LTS (Bionic Beaver) 64-bit on Intel-based
platform.

I have noticed for ages that sometimes a dozen of programs where
consuming much too CPU cycles. Amongst them were xdg-desktop-portal-
gtk. And if I "kill -STOP" the PID of xdg-desktop-portal-gtk then all
calm down and become responsive again.

If fact the most affected applications were gedit, geany, firefox,
google-chrome, and, last but not leas, the Xorg server itself!,
hindering the usability of the whole system.

Also, this bug maybe also affects default Ubuntu
session/desktop/window manager or compositor, and non default ones,
possibly.

In hope this helps,
Sincerely, Valentin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1834366/+subscriptions

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

[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04

2019-06-26 Thread RussianNeuroMancer

Workaround does not help me too anymore. So there is possibility that
after system upgrade there was one issue, and now it's another.

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

Title:
  Nautilus does not open after updating to 19.04

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 19.04 dev branch, nautilus does not open at
  all. Moreover, trying to open nautilus from the terminal does not give
  any error, nor any output at all, and no window opens.

  I don't really know how to report this bug without any terminal
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 13:58:12 2019
  InstallationDate: Installed on 2018-02-23 (398 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04

2019-06-26 Thread RussianNeuroMancer

> https://wiki.ubuntu.com/Backtrace#Already_running_programs describes
how to get a stacktrace of a program hanging

Attached.

** Attachment added: "stacktrace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+attachment/5273536/+files/stacktrace.txt

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

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

Title:
  Nautilus does not open after updating to 19.04

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 19.04 dev branch, nautilus does not open at
  all. Moreover, trying to open nautilus from the terminal does not give
  any error, nor any output at all, and no window opens.

  I don't really know how to report this bug without any terminal
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 13:58:12 2019
  InstallationDate: Installed on 2018-02-23 (398 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1834264] Re: PCI/internal sound card not detected

2019-06-26 Thread pgfan92

Bluetooth does not work.  And after updating the kernel, virtualbox no
longer works.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I don't have any sound.  I have followed some online instructions that
  have not worked.  Please help me.  My laptop was working just fine
  until today.  I opened it up and there was no sound.  If you need
  further information from me, please provide instructions on how to
  obtain it.  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 25 18:29:31 2019
  InstallationDate: Installed on 2019-02-18 (127 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8364
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc0xx
  dmi.product.sku: 1KU13UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034

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

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

[Desktop-packages] [Bug 1827879] Re: Killer Wireless 1525 firmware crashes on suspend

2019-06-26 Thread Sander Los

Yes, nothing changed as far as i know, so the issue remains

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Problem: 
  Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's 
stay on and FAN keeps running. Strangely this does not happen in Fedora 29 
(Kernel 4.18 & same board firmware)

  System:
  Ubuntu 19.04 
  Kernel 5.0.0-13-generic
  Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1)
  Wireless info:
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 20
 serial: 40:b8:9a:ca:2b:99
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 
ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:32 memory:f680-f69f

  
  My attempts:
  1. Tried other kernels:
  5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114

  2. Tried several distro's based on ubuntu -> all have the same issue

  3. Checked firmware from Fedora 29 (md5sum was equal) and updated
  firmware (not available, using latest)

  4. Created systemd scripts for disabling & enabling the driver, this causes 
the same crashes in /var/log/syslog
  See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11

  5. Physically replaced Killer 1525 with Intel 8260 --> problem is
  gone, standby works perfectly

  Of course i want to be able to use the 1525, so please help me solve the 
issue.
  Happy to perform additional debugging if required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sander 1527 F pulseaudio
   /dev/snd/controlC0:  sander 1527 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 
600
  MachineType: Alienware Alienware 17 R2
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.16.0-0ubuntu2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  Tags:  disco
  Uname: Linux 5.0.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/31/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: A08
  dmi.board.name: Alienware 17 R2
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08:
  dmi.product.family: Alienware 17 R2
  dmi.product.name: Alienware 17 R2
  dmi.product.sku: Alienware 15
  dmi.product.version: A08
  dmi.sys.vendor: Alienware
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid

** Changed in: mutter
   Status: Unknown => New

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

Title:
  scaling changes when closing/re-opening the lid

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  scaling changes when closing/re-opening the lid. Seen in bionic.

  Mz scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

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

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

[Desktop-packages] [Bug 1834358] [NEW] network-manager-openvpn works only in command line

2019-06-26 Thread Yossi Haddad

Public bug reported:

Using Kubuntu 18.04 with KDE Plasma 5.12.8 network-manager-openvpn not
connecting but if I use openvpn --config CONFIG_FILE.opvn in command
line I get connected with a problem...

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager-openvpn 1.8.2-1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Jun 26 20:52:41 2019
InstallationDate: Installed on 2018-08-14 (316 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  network-manager-openvpn works only in command line

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  Using Kubuntu 18.04 with KDE Plasma 5.12.8 network-manager-openvpn not
  connecting but if I use openvpn --config CONFIG_FILE.opvn in command
  line I get connected with a problem...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-openvpn 1.8.2-1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jun 26 20:52:41 2019
  InstallationDate: Installed on 2018-08-14 (316 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2019-06-26 Thread Gunnar Hjalmarsson

** Tags added: regression-release

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Starting with Ubuntu 17.10, Ubuntu changed the directory where sane
  dll looks for third party drivers. This configuration effectively
  broke backward compatibility for all existing third-party drivers.

   * A large swath of these third party drivers (most of them) are no
  longer supported by the OEM, so maintaining compatibility is
  important.

   * No open source replacement drivers are currently available, nor
  does the community have the resources to easily replace them.

   * This bug represents a substantial portion of the scanners in use.

  Scanners known to be affected include, but are not limited to:

   - Brother Scanners (all Brother scanners before brscan4)
- DCP-145C
- DCP-163C
- DCP-165C
- DCP-167C
- DCP-185C
- DCP-195C
- DCP-197C
- DCP-365CN
- DCP-373CW
- DCP-375CW
- DCP-377CW
- DCP-383C
- DCP-385C
- DCP-387C
- DCP-395CN
- DCP-585CW
- DCP-6690CW
- DCP-7030
- DCP-7040
- DCP-7045N
- DCP-8070D
- DCP-8080DN
- DCP-8085DN
- DCP-9010CN
- DCP-9040CN
- DCP-9042CDN
- DCP-9045CDN
- DCP-J125
- DCP-J315W
- DCP-J515W
- DCP-J715W
- MFC-250C
- MFC-255CW
- MFC-257CW
- MFC-290C
- MFC-295CN
- MFC-297C
- MFC-490CW
- MFC-495CW
- MFC-5490CN
- MFC-5890CN
- MFC-5895CW
- MFC-6490CW
- MFC-6890CDW
- MFC-7320
- MFC-7340
- MFC-7345N
- MFC-7440N
- MFC-7450
- MFC-7840N
- MFC-7840W
- MFC-790CW
- MFC-795CW
- MFC-8370DN
- MFC-8380DN
- MFC-8480DN
    - MFC-8510DN
- MFC-8680DN
- MFC-8880DN
- MFC-8890DW
- MFC-9010CN
- MFC-9120CN
- MFC-9320CW
- MFC-9440CN
- MFC-9450CDN
- MFC-9840CDW
- MFC-990CW
- MFC-J220
- MFC-J265W
- MFC-J270W
- MFC-J410
- MFC-J410W
- MFC-J415W
- MFC-J615W
- MFC-J630W 

   - Dell MFP Laser Printer 1135n

   - Epson Scanners
- All scanners supported by the libsane-epk driver
- All scanners supported by the iscan driver
    - Epson Perfection V10
    - Epson Perfection V1000
    - Epson WorkForce GT-1500
    - Epson Perfection V33

   - Samsung M2070

   - Xerox Workcentre 3225

   * This was working in the 17.04 release.  18.10 is an LTS release, so
  backporting is warranted for the 18.10 release.

  [Test Case]

   * Following the standard installation procedures for any of the
  affected scanner drivers results in the driver files being installed
  to /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux-
  gnu/sane.  When xsane is run, the scanner is not found.

  [Regression Potential]

   * Regression to previous working sane package often results in the
  automatic removal of core system components (documented in the
  comments to this bug report), making regression an unusable option for
  addressing this bug.

   * The available patch is functional and stable in the 19.10 branch.

  [Other Info]
   * Third party sane drivers in previous version of sane were located under 
/usr/lib/sane/, however, the current version of sane on Ubuntu only looks for 
64 bit drivers under the /usr/lib/x86_64-linux-gnu/sane directory. /usr/lib64 
and /usr/lib64/sane are other directories old drivers are known to install 
files to.

  * The addition of symlinks alone does not appear to fix this issue,
  though it may make the scanner detectable. Changes to udev rules are
  also needed to allow proper communications to the scanners. A
  selection of workarounds, including working (though not ideal) udev
  rules for a number of scanners has been posted to the sane
  troubleshooting guide:
  help.ubuntu.com/community/sane_Troubleshooting#The_symlink_and_udev_tricks

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2019-06-26 Thread Gunnar Hjalmarsson

I have uploaded a proposed fix of sane-backends to this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

If you are on 18.04 and affected by this bug, it would be great if you
could install from the PPA, test to find out if it makes a difference,
and report your observations in a comment here.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Starting with Ubuntu 17.10, Ubuntu changed the directory where sane
  dll looks for third party drivers. This configuration effectively
  broke backward compatibility for all existing third-party drivers.

   * A large swath of these third party drivers (most of them) are no
  longer supported by the OEM, so maintaining compatibility is
  important.

   * No open source replacement drivers are currently available, nor
  does the community have the resources to easily replace them.

   * This bug represents a substantial portion of the scanners in use.

  Scanners known to be affected include, but are not limited to:

   - Brother Scanners (all Brother scanners before brscan4)
- DCP-145C
- DCP-163C
- DCP-165C
- DCP-167C
- DCP-185C
- DCP-195C
- DCP-197C
- DCP-365CN
- DCP-373CW
- DCP-375CW
- DCP-377CW
- DCP-383C
- DCP-385C
- DCP-387C
- DCP-395CN
- DCP-585CW
- DCP-6690CW
- DCP-7030
- DCP-7040
- DCP-7045N
- DCP-8070D
- DCP-8080DN
- DCP-8085DN
- DCP-9010CN
- DCP-9040CN
- DCP-9042CDN
- DCP-9045CDN
- DCP-J125
- DCP-J315W
- DCP-J515W
- DCP-J715W
- MFC-250C
- MFC-255CW
- MFC-257CW
- MFC-290C
- MFC-295CN
- MFC-297C
- MFC-490CW
- MFC-495CW
- MFC-5490CN
- MFC-5890CN
- MFC-5895CW
- MFC-6490CW
- MFC-6890CDW
- MFC-7320
- MFC-7340
- MFC-7345N
- MFC-7440N
- MFC-7450
- MFC-7840N
- MFC-7840W
- MFC-790CW
- MFC-795CW
- MFC-8370DN
- MFC-8380DN
- MFC-8480DN
    - MFC-8510DN
- MFC-8680DN
- MFC-8880DN
- MFC-8890DW
- MFC-9010CN
- MFC-9120CN
- MFC-9320CW
- MFC-9440CN
- MFC-9450CDN
- MFC-9840CDW
- MFC-990CW
- MFC-J220
- MFC-J265W
- MFC-J270W
- MFC-J410
- MFC-J410W
- MFC-J415W
- MFC-J615W
- MFC-J630W 

   - Dell MFP Laser Printer 1135n

   - Epson Scanners
- All scanners supported by the libsane-epk driver
- All scanners supported by the iscan driver
    - Epson Perfection V10
    - Epson Perfection V1000
    - Epson WorkForce GT-1500
    - Epson Perfection V33

   - Samsung M2070

   - Xerox Workcentre 3225

   * This was working in the 17.04 release.  18.10 is an LTS release, so
  backporting is warranted for the 18.10 release.

  [Test Case]

   * Following the standard installation procedures for any of the
  affected scanner drivers results in the driver files being installed
  to /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux-
  gnu/sane.  When xsane is run, the scanner is not found.

  [Regression Potential]

   * Regression to previous working sane package often results in the
  automatic removal of core system components (documented in the
  comments to this bug report), making regression an unusable option for
  addressing this bug.

   * The available patch is functional and stable in the 19.10 branch.

  [Other Info]
   * Third party sane drivers in previous version of sane were located under 
/usr/lib/sane/, however, the current version of sane on Ubuntu only looks for 
64 bit drivers under the /usr/lib/x86_64-linux-gnu/sane directory. /usr/lib64 
and /usr/lib64/sane are other directories old drivers are known to install 
files to.

  * The addition of symlinks alone does not appear to fix this issue,
  though it may make the scanner detectable. Changes to udev rules are
  also needed to allow proper communications to the scanners. A
  selection of workarounds, including working (though not ideal) udev
  rules for a number of scanners has been posted to the sane
  troubleshooting guide:
  help.ubuntu.com/community/sane_Troubleshooting#The_symlink_and_udev_tricks

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

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

[Desktop-packages] [Bug 1559739] Re: Systemd service script for daemon doesn't use /etc/default/transmission-daemon

2019-06-26 Thread Justin Alcorn

The fact that the systemd unit file has command line parameters set and
no way to override them should be fixed.  The simplest way to fix this
is to add to /lib/systemd/system/transmission-daemon

EnvironmentFile=/etc/default/transmission-daemon


Change the ExecStart to

ExecStart=/usr/bin/transmission-daemon -f --error-log $OPTIONS

And add

TRANSMISSION_HOME=$CONFIG_DIR

to /etc/default/transmission-daemon

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

Title:
  Systemd service script for daemon doesn't use /etc/default
  /transmission-daemon

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 15.10
  Release:  15.10

  transmission-daemon:
Installed: 2.84-1ubuntu1
Candidate: 2.84-1ubuntu1
Version table:
   *** 2.84-1ubuntu1 0
  500 http://fi.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected:
  Changing CONFIG_DIR in /etc/default/transmission-daemon, causes the daemon to 
use that directory for its configuration and runtime folders.

  What happened instead:
  Whatever value CONFIG_DIR had, transmission-daemon acted as if it was the 
default ('/var/lib/transmission-daemon/info').

  I was finally able to fix this by adding 
'EnvironmentFile=/etc/default/transmission' into the service file and changing 
the name of CONFIG_DIR to TRANSMISSION_HOME in /etc/default/transmission. I 
tried adding $OPTIONS to the command line in the service file instead (as the 
older startup scripts do) but apparently systemd doesn't support substitution 
in the environment file. 
  This enables specifying the configuration directory, and shouldn't break the 
older scripts.

  Btw, having three init scripts is kind of confusing.

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

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

[Desktop-packages] [Bug 1825447] Re: Indicators Scroll events are not emitted in 19.04

2019-06-26 Thread Lonnie Lee Best

Thank you for fixing this. The app-level volume control is working great
now by scrolling on top of the RadioTray icon.

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

Title:
  Indicators Scroll events are not emitted in 19.04

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Disco:
  Fix Released

Bug description:
  [ Impact ]

  Scroll events aren't delivered to app-indicators

  [ Test case ]
   - Run an indicator that supports scroll events (i.e. radiotray-ng or run
 
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js
 with gjs
   - Scroll events should be delivered

  [ Regression potential ]

  Scroll events over other shell actors aren't working (i.e. changing volume 
with scroll)
   

  ---

  It appears the code used in the 19.04 packaging of the appindicator is
  from master and not the tagged ubuntu-19.04 commit from the ubuntu
  branch. The master branch is not delivering scroll events, which stops
  my application (radiotray-ng) from being able to adjust its volume
  levels.

  I've swapped out the code under /usr/share/gnome-shell/extensions
  /ubuntu-appindicat...@ubuntu.com/ with the ubuntu branch and scrolling
  on an indicator icon works again.

  I've filed an issue on github as well.

  https://github.com/ubuntu/gnome-shell-extension-
  appindicator/issues/169

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

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

[Desktop-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5

2019-06-26 Thread Amr Ibrahim

** Also affects: gstreamer-editing-services1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-python1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] Bugfix release 1.14.5

Status in gst-libav1.0 package in Ubuntu:
  New
Status in gst-omx package in Ubuntu:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gst-plugins-good1.0 package in Ubuntu:
  New
Status in gst-plugins-ugly1.0 package in Ubuntu:
  New
Status in gst-python1.0 package in Ubuntu:
  New
Status in gst-rtsp-server1.0 package in Ubuntu:
  New
Status in gstreamer-editing-services1.0 package in Ubuntu:
  New
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.
  ---

  Highlighted bugfixes in 1.14.5

  GStreamer core

  -   aggregator: take the pad lock around queue gap event removal
  -   aggregator: don’t leak gap buffer when out of segment
  -   buffer: fix possible memory corruption in gst_buffer_foreach_meta() when 
removing metas
  -   bus: Make removing of signal/bus watches thread-safe
  -   bus: Don’t allow removing signal watches with gst_bus_remove_watch()
  -   controlbinding: Check if the weak pointer was cleared before explicitly 
removing it
  -   ptp clock: Wait for ANNOUNCE before selecting a master; increase 
tolerance for late follow-up and delay-resp
  -   segment: Allow stop == -1 in gst_segment_to_running_time() and negative 
rate
  -   g-i: annotations fixes

  gst-plugins-base

  -   audioconvert: fix endianness conversion for unpacked formats (e.g. 
S24_32BE)
  -   audioringbuffer: Fix wrong memcpy address when reordering channels
  -   decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup
  -   glviewconvert: fix output when a transformation matrix is used
  -   glupload: prevent segfault when updating caps
  -   gl/egl: Determine correct format on dmabuf import
  -   glupload: dmabuf: be explicit about gl formats used
  -   id3tag: validate the year from v1 tags before passing to GstDateTime
  -   rtpbasepayload: fix sequence numbers when using buffer lists
  -   rtspconnection: fix security issue, potential heap overflow 
(CVE-2019-9928)
  -   rtspconnection: fix GError set over the top of a previous GError
  -   rtspconnection: do not duplicate authentication headers
  -   subparse: don’t assert when failing to parse subrip timestamp
  -   video: various convert sample frame fixes
  -   video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, 
A420_10LE/BE to BGRA/RGBA which created corrupted output
  -   video-format: Fix GBRA_10/12 alpha channel pixel strides

  gst-plugins-good

  -   flv: Use 8kHz sample rate for alaw/mulaw audio
  -   flvdemux: Do not error out if the first added and chained pad is not 
linked
  -   flvmux: try harder to make sure timestamps are always increasing
  -   gdkpixbufdec: output a TIME segment which is what’s expected for raw video
  -   matroskademux: fix handling of MS ACM audio
  -   matroska: fix handling of FlagInterlaced
  -   pulsesink: Deal with not being able to convert a format to caps
  -   rtph265depay, rtph264depay; aggregation packet marker handling fixes
  -   rtpmp4gdepay: detect broken senders who send AAC with ADTS frames
  -   rtprawdepay: keep buffer pool around when flushing/seeking
  -   rtpssrcdemux: Forward serialized events to all pads
  -   qmlglsink: Handle OPENGL header guard changes
  -   qtdemux: fix track language code parsing; ignore corrupted CTTS box
  -   qtmux: Correctly set tkhd width/height to the display size
  -   splitmuxsink: various timecode meta handling fixes
  -   splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc
  -   v4l2sink: fix pool-less allocation query handling
  -   v4l2dec/enc: fix use after free when handling events
  -   vpx: Fix build against libvpx 1.8
  -   webmmux: allow resolutions above 4096

  gst-plugins-ugly

  -   sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN
  -   x264: Only enable dynamic loading code for x264 before v253

  gst-plugins-bad

  -   assrender: fix disappearing subtitles when seeking back in time
  -

[Desktop-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5

2019-06-26 Thread Amr Ibrahim

** Also affects: gst-plugins-good1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-plugins-base1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-plugins-ugly1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-libav1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-rtsp-server1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gstreamer-vaapi (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-omx (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] Bugfix release 1.14.5

Status in gst-libav1.0 package in Ubuntu:
  New
Status in gst-omx package in Ubuntu:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gst-plugins-good1.0 package in Ubuntu:
  New
Status in gst-plugins-ugly1.0 package in Ubuntu:
  New
Status in gst-python1.0 package in Ubuntu:
  New
Status in gst-rtsp-server1.0 package in Ubuntu:
  New
Status in gstreamer-editing-services1.0 package in Ubuntu:
  New
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.
  ---

  Highlighted bugfixes in 1.14.5

  GStreamer core

  -   aggregator: take the pad lock around queue gap event removal
  -   aggregator: don’t leak gap buffer when out of segment
  -   buffer: fix possible memory corruption in gst_buffer_foreach_meta() when 
removing metas
  -   bus: Make removing of signal/bus watches thread-safe
  -   bus: Don’t allow removing signal watches with gst_bus_remove_watch()
  -   controlbinding: Check if the weak pointer was cleared before explicitly 
removing it
  -   ptp clock: Wait for ANNOUNCE before selecting a master; increase 
tolerance for late follow-up and delay-resp
  -   segment: Allow stop == -1 in gst_segment_to_running_time() and negative 
rate
  -   g-i: annotations fixes

  gst-plugins-base

  -   audioconvert: fix endianness conversion for unpacked formats (e.g. 
S24_32BE)
  -   audioringbuffer: Fix wrong memcpy address when reordering channels
  -   decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup
  -   glviewconvert: fix output when a transformation matrix is used
  -   glupload: prevent segfault when updating caps
  -   gl/egl: Determine correct format on dmabuf import
  -   glupload: dmabuf: be explicit about gl formats used
  -   id3tag: validate the year from v1 tags before passing to GstDateTime
  -   rtpbasepayload: fix sequence numbers when using buffer lists
  -   rtspconnection: fix security issue, potential heap overflow 
(CVE-2019-9928)
  -   rtspconnection: fix GError set over the top of a previous GError
  -   rtspconnection: do not duplicate authentication headers
  -   subparse: don’t assert when failing to parse subrip timestamp
  -   video: various convert sample frame fixes
  -   video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, 
A420_10LE/BE to BGRA/RGBA which created corrupted output
  -   video-format: Fix GBRA_10/12 alpha channel pixel strides

  gst-plugins-good

  -   flv: Use 8kHz sample rate for alaw/mulaw audio
  -   flvdemux: Do not error out if the first added and chained pad is not 
linked
  -   flvmux: try harder to make sure timestamps are always increasing
  -   gdkpixbufdec: output a TIME segment which is what’s expected for raw video
  -   matroskademux: fix handling of MS ACM audio
  -   matroska: fix handling of FlagInterlaced
  -   pulsesink: Deal with not being able to convert a format to caps
  -   rtph265depay, rtph264depay; aggregation packet marker handling fixes
  -   rtpmp4gdepay: detect broken senders who send AAC with ADTS frames
  -   rtprawdepay: keep buffer pool around when flushing/seeking
  -   rtpssrcdemux: Forward serialized events to all pads
  -   qmlglsink: Handle OPENGL header guard changes
  -   qtdemux: fix track language code parsing; ignore corrupted CTTS box
  -   qtmux: Correctly set tkhd width/height to the display size
  -   splitmuxsink: various timecode meta handling fixes
  -   splitmuxsink: make

[Desktop-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5

2019-06-26 Thread Sebastien Bacher

There is currently 1.14.4 that in bionic-proposed that needs to be
verified first

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

Title:
  [SRU] Bugfix release 1.14.5

Status in gst-libav1.0 package in Ubuntu:
  New
Status in gst-omx package in Ubuntu:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gst-plugins-good1.0 package in Ubuntu:
  New
Status in gst-plugins-ugly1.0 package in Ubuntu:
  New
Status in gst-python1.0 package in Ubuntu:
  New
Status in gst-rtsp-server1.0 package in Ubuntu:
  New
Status in gstreamer-editing-services1.0 package in Ubuntu:
  New
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.
  ---

  Highlighted bugfixes in 1.14.5

  GStreamer core

  -   aggregator: take the pad lock around queue gap event removal
  -   aggregator: don’t leak gap buffer when out of segment
  -   buffer: fix possible memory corruption in gst_buffer_foreach_meta() when 
removing metas
  -   bus: Make removing of signal/bus watches thread-safe
  -   bus: Don’t allow removing signal watches with gst_bus_remove_watch()
  -   controlbinding: Check if the weak pointer was cleared before explicitly 
removing it
  -   ptp clock: Wait for ANNOUNCE before selecting a master; increase 
tolerance for late follow-up and delay-resp
  -   segment: Allow stop == -1 in gst_segment_to_running_time() and negative 
rate
  -   g-i: annotations fixes

  gst-plugins-base

  -   audioconvert: fix endianness conversion for unpacked formats (e.g. 
S24_32BE)
  -   audioringbuffer: Fix wrong memcpy address when reordering channels
  -   decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup
  -   glviewconvert: fix output when a transformation matrix is used
  -   glupload: prevent segfault when updating caps
  -   gl/egl: Determine correct format on dmabuf import
  -   glupload: dmabuf: be explicit about gl formats used
  -   id3tag: validate the year from v1 tags before passing to GstDateTime
  -   rtpbasepayload: fix sequence numbers when using buffer lists
  -   rtspconnection: fix security issue, potential heap overflow 
(CVE-2019-9928)
  -   rtspconnection: fix GError set over the top of a previous GError
  -   rtspconnection: do not duplicate authentication headers
  -   subparse: don’t assert when failing to parse subrip timestamp
  -   video: various convert sample frame fixes
  -   video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, 
A420_10LE/BE to BGRA/RGBA which created corrupted output
  -   video-format: Fix GBRA_10/12 alpha channel pixel strides

  gst-plugins-good

  -   flv: Use 8kHz sample rate for alaw/mulaw audio
  -   flvdemux: Do not error out if the first added and chained pad is not 
linked
  -   flvmux: try harder to make sure timestamps are always increasing
  -   gdkpixbufdec: output a TIME segment which is what’s expected for raw video
  -   matroskademux: fix handling of MS ACM audio
  -   matroska: fix handling of FlagInterlaced
  -   pulsesink: Deal with not being able to convert a format to caps
  -   rtph265depay, rtph264depay; aggregation packet marker handling fixes
  -   rtpmp4gdepay: detect broken senders who send AAC with ADTS frames
  -   rtprawdepay: keep buffer pool around when flushing/seeking
  -   rtpssrcdemux: Forward serialized events to all pads
  -   qmlglsink: Handle OPENGL header guard changes
  -   qtdemux: fix track language code parsing; ignore corrupted CTTS box
  -   qtmux: Correctly set tkhd width/height to the display size
  -   splitmuxsink: various timecode meta handling fixes
  -   splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc
  -   v4l2sink: fix pool-less allocation query handling
  -   v4l2dec/enc: fix use after free when handling events
  -   vpx: Fix build against libvpx 1.8
  -   webmmux: allow resolutions above 4096

  gst-plugins-ugly

  -   sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN
  -   x264: Only enable dynamic loading code for x264 before v253

  gst-plugins-bad

  -   assrender: fix disappearing subtitles when seeking back in time
  -   decklinkvideosink: fix segfault when audiosink is closed before videosink
  -   decklinkvideosrc: respect pixel

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-26 Thread Eric Desrochers

Todd, The fix will land in the next kernel cycle.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  As per commit description:

  "
  This should be transparent to to user space, as long as it doesn't
  compare the time against the result of gettimeofday().
  "

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log

[Desktop-packages] [Bug 1832875] Re: On-screen keyboard lacks several French layouts

** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/369345

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

Title:
  On-screen keyboard lacks several French layouts

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  The on-screen keyboard in Gnome Shell is not localized (at least for
  some locales), and always displays a QWERTY keyboard, independently of
  the selected layout.

  See upstream issue https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/997

  [ Test case ]

  - Setting locale to a French one should change the layout accordinly

  [ Regression potential ]

  French layouts are not working as expected

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

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

[Desktop-packages] [Bug 1832875] Re: On-screen keyboard lacks several French layouts

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: Triaged => In Progress

** Description changed:

+ [ Description ]
+ 
  The on-screen keyboard in Gnome Shell is not localized (at least for
  some locales), and always displays a QWERTY keyboard, independently of
  the selected layout.
  
  See upstream issue https://gitlab.gnome.org/GNOME/gnome-shell/issues/997
+ 
+ [ Test case ]
+ 
+ - Setting locale to a French one should change the layout accordinly
+ 
+ [ Regression potential ]
+ 
+ French layouts are not working as expected

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

Title:
  On-screen keyboard lacks several French layouts

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  The on-screen keyboard in Gnome Shell is not localized (at least for
  some locales), and always displays a QWERTY keyboard, independently of
  the selected layout.

  See upstream issue https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/997

  [ Test case ]

  - Setting locale to a French one should change the layout accordinly

  [ Regression potential ]

  French layouts are not working as expected

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

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

[Desktop-packages] [Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv("Function allocate terminated with uncatchab

** This bug is no longer a duplicate of bug 1831555
   gnome-shell crashed with SIGTRAP in gjs_callback_closure() from 
ffi_closure_unix64_inner() from ffi_closure_unix64() from 
clutter_actor_allocate_internal() from clutter_actor_allocate()

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler() from
  g_logv("Function allocate terminated with uncatchable exception") from
  g_log()

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.26.2-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 
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/1736664/+subscriptions

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

[Desktop-packages] [Bug 1733733] Re: portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estad

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

** This bug has been marked a duplicate of bug 1509043
   package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  portable apps crash while installing package gconf2-common
  3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-
  installation instalado retornou estado de saída de erro 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I installed orbital apps then it crashed, i changed to unity environment then 
tried to install again. I'm in need for portable apps for ubuntu.
  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: gconf2-common 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Tue Nov 21 21:44:08 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 128
  InstallationDate: Installed on 2017-09-05 (77 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 128
  UpgradeStatus: Upgraded to artful on 2017-11-18 (4 days ago)

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-26 Thread Todd Short

I am running into the same situation:

Running Ubuntu 18.04 in VMWare Fusion 10.1.6 on macOS 10.14.5

After I updated I received the 4.15.0-52-geeneric kernel, and the login
screen no longer shows. I was able to successfully use the workaround
"WaylandEnable=false" to get it to show.

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  As per commit description:

  "
  This should be transparent to to user space, as long as it doesn't
  compare the time against the result of gettimeofday().
  "

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8

[Desktop-packages] [Bug 1645384] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida d

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

** This bug has been marked a duplicate of bug 1509043
   package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 128

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  el problema se genero cuando intentaba descargar unos programas, no se
  completo la descarga  y la tuve que reiniciar y posterior al reinicio
  aparecio el  mensaje de error.

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 09:10:05 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 128
  InstallationDate: Installed on 2016-11-26 (1 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1698612] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett

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

** This bug has been marked a duplicate of bug 1509043
   package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: telepítve post-installation parancsfájl alfolyamat
  128 hibakóddal kilépett

Status in gconf package in Ubuntu:
  New

Bug description:
  this problem comes up after aech booting

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 18:21:04 2017
  ErrorMessage: telepítve post-installation parancsfájl alfolyamat 128 
hibakóddal kilépett
  InstallationDate: Installed on 2017-05-22 (26 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 
hibakóddal kilépett
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1711472] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sorti

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

** This bug has been marked a duplicate of bug 1509043
   package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: le sous-processus script post-installation installé a
  retourné une erreur de sortie d'état 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Hello,
  i want you say what this problem isn't today.
  I had this problem with ubuntu16.10
  And today i have this problem with this new system based on ubuntu.
  I wish what you resolved this problem.
  Jo

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug 17 23:53:18 2017
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 128
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4

2019-06-26 Thread Iain Lane

I've verified these as best as I can. I installed 1.14.4 and played a
load of different filetypes:

  - mp3
  - ogg
  - flac
  - opus
  - mp4 (H.264)

with different codecs, e.g. mpg123, libav, ...

and different players - epiphany, totem, rhythmbox.

I didn't find any regressions.

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

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Bionic:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Committed
Status in gst-plugins-base1.0 source package in Bionic:
  In Progress
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Committed
Status in gst-python1.0 source package in Bionic:
  Fix Committed
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Committed
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Committed
Status in gstreamer-vaapi source package in Bionic:
  Fix Committed
Status in gstreamer1.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions

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

[Desktop-packages] [Bug 1831555] Re: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from clutter_actor_allocate_internal() from cl

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

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

** Changed in: gnome-shell (Ubuntu Bionic)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGTRAP in gjs_callback_closure() from
  ffi_closure_unix64_inner() from ffi_closure_unix64() from
  clutter_actor_allocate_internal() from clutter_actor_allocate()

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  In Progress

Bug description:
  This is a regression for GNOME Shell / mutter 3.32.1.

  Tracking upstream at https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1295

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/7a0ffc1caa388737d61043fd4a0ee45677b63d71 
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/.

  Similar stacktrace at
  https://errors.ubuntu.com/problem/66c2476d86f4d697ff373f99f20c6134c6b5fab3

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

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

[Desktop-packages] [Bug 1834318] Re: Warning from Google about Ubuntu

2019-06-26 Thread Mateo Salta

I believe it is a bug, because ubuntu would need to comply with updating
the plugin in order for it to continue to function.

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

Title:
  Warning from Google about Ubuntu

Status in gnome-online-accounts package in Ubuntu:
  Invalid

Bug description:
  I'm not sure if it is a correct place to report this problem.

  I use Ubuntu 18.04. 
  Yesterday I've got an email from Google warning that "Ubuntu" will lose 
access to my Google account if it will not comply with new Google policy 
requirement.

  Screenshot attached and here's the full text of the email:

  Hi,

  Although you don’t need to do anything, we wanted to let you know that the 
following apps may no longer be able to access some data in your Google 
account, including your Gmail content. If these apps are unable to meet the 
deadline to comply with our updated data policy requirements, they'll lose 
access to your account from 15 July 2019.
  Ubuntu

  We are making this change as part of ongoing efforts to make sure that
  your data is protected and private.

  You can always view, manage and remove apps to which you’ve given
  access to your account by visiting your Google account.

  Thanks,
  The Google Accounts team

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

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

[Desktop-packages] [Bug 1821765] Re: [snap] Missing icon in indicator

2019-06-26 Thread Ken VanDine

Is there an env variable we can set to change the location of tmp?  I
think in generally it shouldn't be attempting to use /tmp for anything.

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

Title:
  [snap] Missing icon in indicator

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Chromium is adding an appindicator, which has a missing icon when
  running from the snap.  I've confirmed with the deb that it shows the
  chromium icon there.  I'm not sure what setting makes it display the
  appindicator, I've had it there for years so must be some setting I
  have that is being synced.

  The only extensions I have installer are:

* The Great Suspender
* Google Drive
* Google Calendar

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

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

[Desktop-packages] [Bug 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_

2019-06-26 Thread El jinete sin cabeza

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

Title:
  gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay()
  from detach_pixmap() from meta_surface_actor_x11_dispose() from
  g_object_unref() from g_object_unref()

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
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.32.0+git20190410-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/1a5d1f99fd9215f7a79b718d2e915c675ebcd69f 
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/gnome-shell/+bug/1826918/+subscriptions

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

[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/407
   Importance: Unknown
   Status: Unknown

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

Title:
  scaling changes when closing/re-opening the lid

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  scaling changes when closing/re-opening the lid. Seen in bionic.

  Mz scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

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

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

[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid

2019-06-26 Thread Iain Lane

** No longer affects: mutter (Ubuntu Bionic)

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

Title:
  scaling changes when closing/re-opening the lid

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  scaling changes when closing/re-opening the lid. Seen in bionic.

  Mz scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

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

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

[Desktop-packages] [Bug 1834333] Re: Scaling problem with Qt apps

2019-06-26 Thread Sebastien Bacher

Thank you for your bug report, that should be sent upstream on
https://gitlab.gnome.org/GNOME/gnome-control-center/issues

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Scaling problem with Qt apps

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Hi
  I have problem with scaling for Qt apps.
  when i open Kolourpaint scaling is too small 
  i have Ubuntu 18.04 and install from snap and apt
  i first report to bugs.kde.org and they tell me to report here 
  https://bugs.kde.org/show_bug.cgi?id=407668

  Kolourpaint its not only app with problem , anydesk , filezilla ,
  pylon viewer ,  dukto , stacer , vmware horizon

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

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

[Desktop-packages] [Bug 1834110] Re: Broken lock-screen wallpaper, stutter after resuming from hibernation

2019-06-26 Thread Aleksandar Palic

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

@vanvugt

I just want to clarify that I'm indeed talking about hibernation, not 
suspend-mode.
Thanks.

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

Title:
  Broken lock-screen wallpaper, stutter after resuming from hibernation

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Very similar to Bug #1809407
  (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407).

  I set up my swap partition and tested hibernation on 19.04 /w Nvidia
  drivers.

  Basically I observed 2 things:
  - Lock screen wallpaper gone (black screen with clock), same as with #1809407
  - Desktop wallpaper seems okay
  - Big frame rate drops (despite performance governor), everything seems quite 
laggy

  I'm new to Linux/Ubuntu, if you need any logs please tell me the
  commands and I will attach them.

  Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-06-20 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: mutter 3.32.1-2ubuntu1~19.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-19.20-generic 5.0.8
  Tags:  disco
  Uname: Linux 5.0.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1834333] [NEW] Scaling problem with Qt apps

2019-06-26 Thread Ali Fakhamati

Public bug reported:

Hi
I have problem with scaling for Qt apps.
when i open Kolourpaint scaling is too small 
i have Ubuntu 18.04 and install from snap and apt
i first report to bugs.kde.org and they tell me to report here 
https://bugs.kde.org/show_bug.cgi?id=407668

Kolourpaint its not only app with problem , anydesk , filezilla , pylon
viewer ,  dukto , stacer , vmware horizon

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


** Tags: hidpi qt scaling

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

Title:
  Scaling problem with Qt apps

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hi
  I have problem with scaling for Qt apps.
  when i open Kolourpaint scaling is too small 
  i have Ubuntu 18.04 and install from snap and apt
  i first report to bugs.kde.org and they tell me to report here 
  https://bugs.kde.org/show_bug.cgi?id=407668

  Kolourpaint its not only app with problem , anydesk , filezilla ,
  pylon viewer ,  dukto , stacer , vmware horizon

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

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

[Desktop-packages] [Bug 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect

2019-06-26 Thread Olivier Tilloy

I updated the title to reflect the fact that only Yaru (or communitheme
on older releases) seems to be affected. All the other themes that I
tested behave correctly.

** Summary changed:

- [snap] with CSD, minimize and maximize buttons are invisible until hovered
+ [snap] with CSD and Yaru, background color of the header bar is incorrect

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

Title:
  [snap] with CSD and Yaru, background color of the header bar is
  incorrect

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Channel:Stable
  Version:70.0.3538.67
  Updated:10/19/2018
  License:Free
  Developer:  Canonical
  Source: Snap Store
  Installed Size: 148.2 MB

  Settings -> Appearance: "Use system title bar and borders" was turned
  off. Close, minimize, maximize buttons became oval (more of stretched
  down) instead of circle. Turned back it on, buttons went back to
  normal shape (circle). It's a repeatable action.

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

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

[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid

2019-06-26 Thread Matthias Klose

** Tags added: rls-bb-incoming

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

Title:
  scaling changes when closing/re-opening the lid

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

Bug description:
  scaling changes when closing/re-opening the lid. Seen in bionic.

  Mz scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

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

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

[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid

2019-06-26 Thread Matthias Klose

** Also affects: mutter (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  scaling changes when closing/re-opening the lid

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

Bug description:
  scaling changes when closing/re-opening the lid. Seen in bionic.

  Mz scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

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

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

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

2019-06-26 Thread Jani Uusitalo

Happy to report that the proposed packages did fix the issue for me
also. Thanks everyone!

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

Title:
  LIbreoffice crashes on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice-l10n source package in Bionic:
  Fix Committed
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*'
  packages installed.

   * The fix is currently in LibreOffice 6.2.0+ on disco and eoan.

  [Test Case]

   1. apt install cpdb-backend-gcp
   2. run LibreOffice

  [Regression Potential]

   * We're backporting a patch that has already been applied to 6.2.0+
  with no regression, so potential for regression here is low.

   * A combination of autopkgtests and manual testing should provide
  reasonable confidence that no regressions sneaked in.

  [Original Description]

  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:

  $ libreoffice --norestore
  Application Error

  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]

  I have tried entirely removing my profile, ~/.config/libreoffice , but
  the same problem still exhibits.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu

[Desktop-packages] [Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv("Function allocate terminated with uncatchab

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

** This bug has been marked a duplicate of bug 1831555
   gnome-shell crashed with SIGTRAP in gjs_callback_closure() from 
ffi_closure_unix64_inner() from ffi_closure_unix64() from 
clutter_actor_allocate_internal() from clutter_actor_allocate()

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler() from
  g_logv("Function allocate terminated with uncatchable exception") from
  g_log()

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.26.2-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 
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/1736664/+subscriptions

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

[Desktop-packages] [Bug 1833500] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv("Function allocate terminated with uncatchab

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

** This bug is no longer a duplicate of bug 1736664
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler() from g_logv("Function 
allocate terminated with uncatchable exception") from g_log()
** This bug has been marked a duplicate of bug 1831555
   gnome-shell crashed with SIGTRAP in gjs_callback_closure() from 
ffi_closure_unix64_inner() from ffi_closure_unix64() from 
clutter_actor_allocate_internal() from clutter_actor_allocate()

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler() from
  g_logv("Function allocate terminated with uncatchable exception")

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  No idea what caused this, just woke my laptop up to a re-launched
  gnome-shell and an apport dialog.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-lowlatency 5.0.8
  Uname: Linux 5.0.0-16-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 00:29:18 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2015-07-13 (1438 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   ffi_closure_unix64_inner () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_closure_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   clutter_actor_allocate () at 
/usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0
   clutter_actor_allocate_preferred_size () at 
/usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  separator:

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

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

[Desktop-packages] [Bug 1832693] Re: System auto suspend again during resuming

2019-06-26 Thread Rex Tsai

There are several versions of gsd in bionic archive, it would be more
clear for developer if you report the package version by "apport-cli -u
1832693 -p gnome-settings-daemon"

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

Title:
  System auto suspend again during resuming

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  ## Issue
  In certain case, system wake-up from suspend will suspend again automatically.

  The issue comes from a target machine turning auto-suspend on and
  suspends after the idle time-out. Manually suspend, e.g., click
  suspend icon or execute "systemctl suspend" won't reproduce the issue.

  When waking up from this situation, the monitor keeps blank, although
  the monitor has exited low power mode, then suspend again immediately.
  Can successfully waking up the system after that, but once the system
  reaches the idle time again, the issue appears repeatedly. From the
  system log, a sleep request is following the wake request.

  Hardware configuration also counts. It is hard to reproduce the issue
  with the system installed on SSD or with a lower resolution monitor;
  graphics card may also affect. It's likely to be a timing issue.

  ## Environment
  Machine: Dell Precision 7920 Tower.
  Monitor: Philips 288P6L
  DistroRelease: Ubuntu 18.04.2
  Graphics card: Nvidia Quadro P2200
  Nvidia driver version: 418.74
  CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz

  ## Steps to reproduce:
  Turn on automatic suspend in Settings->Power
  Wait for the system to suspend
  Wake up the system via pressing power button or keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1832693/+subscriptions

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

[Desktop-packages] [Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

** Description changed:

+ [ Description ]
+ 
+ GNOME shell crashes on restart when some window actors are opened
+ 
+ [ Test case ]
+ 
+ - Run gnome-shell in Xorg, start some windows
+ - Hit Alt+F2
+ - Write 'r' and press Enter
+ 
+ - The shell should restart without crashing in
+ meta_workspace_list_windows
+ 
+ [ Regression potential ]
+ 
+ Javascript errors might be emitted when trying to access to invalidated
+ data, but nothing really harmful.
+ 
+ [ Note ]
+ 
+ This crash doesn't affect versions after 3.28 for various reasons: 
+  - The JS code triggering it isn't there anymore
+  - MetaScreen doesn't exist anymore.
+ 
+ Similar crashes might happen in newer versions, but as per different
+ code paths, and so to be reported as different bugs.
+ 
+ ---
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.4-0ubuntu18.04.1, the problem page at 
https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 
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/.
  
  https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58
  https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64
  https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c
  https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76
  https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680

** Also affects: mutter (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Also affects: mutter (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

** Changed in: mutter (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: mutter (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: mutter (Ubuntu Bionic)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

** Changed in: mutter (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

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

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Won't Fix
Status in gnome-shell source package in Bionic:
  New
Status in gnome-shell-extension-dashtodock source package in Bionic:
  New
Status in mutter source package in Bionic:
  In Progress
Status in gnome-shell source package in Disco:
  New
Status in gnome-shell-extension-dashtodock source package in Disco:
  New
Status in mutter source package in Disco:
  Won't Fix

Bug description:
  [ Description ]

  GNOME shell crashes on restart when some window actors are opened

  [ Test case ]

  - Run gnome-shell in Xorg, start some windows
  - Hit Alt+F2
  - Write 'r' and press Enter

  - The shell should restart without crashing in
  meta_workspace_list_windows

  [ Regression potential ]

  Javascript errors might be emitted when trying to access to
  invalidated data, but nothing really harmful.

  [ Note ]

  This crash doesn't affect versions after 3.28 for various reasons: 
   - The JS code triggering it isn't there anymore
   - MetaScreen doesn't exist anymore.

  Similar crashes might happen in newer versions, but as per different
  code paths, and so to be reported as different bugs.

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.4-0ubuntu18.04.1, the problem page at 
https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 
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/.

  https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58

[Desktop-packages] [Bug 1832693] Re: System auto suspend again during resuming

2019-06-26 Thread Rex Tsai

** Changed in: oem-priority
 Assignee: (unassigned) => cktenn (cktenn)

** Tags added: originate-from-1830332

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

Title:
  System auto suspend again during resuming

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  ## Issue
  In certain case, system wake-up from suspend will suspend again automatically.

  The issue comes from a target machine turning auto-suspend on and
  suspends after the idle time-out. Manually suspend, e.g., click
  suspend icon or execute "systemctl suspend" won't reproduce the issue.

  When waking up from this situation, the monitor keeps blank, although
  the monitor has exited low power mode, then suspend again immediately.
  Can successfully waking up the system after that, but once the system
  reaches the idle time again, the issue appears repeatedly. From the
  system log, a sleep request is following the wake request.

  Hardware configuration also counts. It is hard to reproduce the issue
  with the system installed on SSD or with a lower resolution monitor;
  graphics card may also affect. It's likely to be a timing issue.

  ## Environment
  Machine: Dell Precision 7920 Tower.
  Monitor: Philips 288P6L
  DistroRelease: Ubuntu 18.04.2
  Graphics card: Nvidia Quadro P2200
  Nvidia driver version: 418.74
  CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz

  ## Steps to reproduce:
  Turn on automatic suspend in Settings->Power
  Wait for the system to suspend
  Wake up the system via pressing power button or keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1832693/+subscriptions

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

[Desktop-packages] [Bug 1742594] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_unmanage

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

** This bug is no longer a duplicate of bug 1422253
   gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: 
(window->display->focus_window != window)") from g_assertion_message_expr() 
from meta_window_unmanage() from handle_other_xevent()
** This bug has been marked a duplicate of bug 1791574
   gnome-shell crashed with SIGABRT: assertion failed 
"window->display->focus_window != window" in meta_window_unmanage

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

Title:
  /usr/bin/gnome-
  
shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_unmanage

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5 
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/1742594/+subscriptions

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

[Desktop-packages] [Bug 1791574] Re: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage

** Description changed:

+ [ Description ]
+ 
+ GNOME Shell crashes when interacting with some "take-input" windows such
+ as the jetbrains products (you can snap install the 2008 versions which
+ are affected), see https://gitlab.gnome.org/GNOME/mutter/issues/308
+ 
+ [ Test case ]
+  Run this script:
+  $ wget -O - https://gitlab.gnome.org/3v1n0/mutter/snippets/453/raw | python3
+ 
+  - The shell should not crash when the windows are closed.
+ 
+ [ Regression potential ]
+ 
+ The patch introduces changes to the window focus handling, so a window
+ might not be properly focused in some cases.
+ 
+ [ Notes to the SRU team ]
+ 
+ This fix is still in process of being released to eoan / disco too.
+ 
+ 
+ 
+ 
  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/308
  
  Originally reported as bug 1422253 and fixed in 18.04, but that crash
  (fixed) was due to a different condition.
  
  Test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/453
  
  ---
  
  gnome-shell crashed and restarted while I was using it.
  
  ProblemType: CrashDistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-1ubuntu1
  Uname: Linux 4.19.0-041900rc3-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 12:39:16 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1536081658
  InstallationDate: Installed on 2017-08-16 (389 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
  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
   meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-08-15 (25 days ago)
  UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo

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

Title:
  gnome-shell crashed with SIGABRT: assertion failed
  "window->display->focus_window != window" in meta_window_unmanage

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Confirmed
Status in mutter source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  GNOME Shell crashes when interacting with some "take-input" windows
  such as the jetbrains products (you can snap install the 2008 versions
  which are affected), see
  https://gitlab.gnome.org/GNOME/mutter/issues/308

  [ Test case ]
   Run this script:
   $ wget -O - https://gitlab.gnome.org/3v1n0/mutter/snippets/453/raw | python3

   - The shell should not crash when the windows are closed.

  [ Regression potential ]

  The patch introduces changes to the window focus handling, so a window
  might not be properly focused in some cases.

  [ Notes to the SRU team ]

  This fix is still in process of being released to eoan / disco too.


  

  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/308

  Originally reported as bug 1422253 and fixed in 18.04, but that crash
  (fixed) was due to a different condition.

  Test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/453

  ---

  gnome-shell crashed and restarted while I was using it.

  ProblemType: CrashDistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-1ubuntu1
  Uname: Linux 4.19.0-041900rc3-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 12:39:16 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1536081658
  InstallationDate: Installed on 2017-08-16 (389 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
  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
   meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at

[Desktop-packages] [Bug 1791574] Re: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage

** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/369334

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

Title:
  gnome-shell crashed with SIGABRT: assertion failed
  "window->display->focus_window != window" in meta_window_unmanage

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Confirmed
Status in mutter source package in Bionic:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/308

  Originally reported as bug 1422253 and fixed in 18.04, but that crash
  (fixed) was due to a different condition.

  Test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/453

  ---

  gnome-shell crashed and restarted while I was using it.

  ProblemType: CrashDistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-1ubuntu1
  Uname: Linux 4.19.0-041900rc3-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 10 12:39:16 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1536081658
  InstallationDate: Installed on 2017-08-16 (389 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
  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
   meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-08-15 (25 days ago)
  UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/369334

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

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Invalid
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.28.4-0ubuntu18.04.1, the problem page at 
https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 
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/.

  https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58
  https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64
  https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c
  https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76
  https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680

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

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

[Desktop-packages] [Bug 1832693] Re: System auto suspend again during resuming

2019-06-26 Thread Rex Tsai

** Tags added: oem-priority

** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: linux-oem (Ubuntu) => oem-priority

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

Title:
  System auto suspend again during resuming

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  ## Issue
  In certain case, system wake-up from suspend will suspend again automatically.

  The issue comes from a target machine turning auto-suspend on and
  suspends after the idle time-out. Manually suspend, e.g., click
  suspend icon or execute "systemctl suspend" won't reproduce the issue.

  When waking up from this situation, the monitor keeps blank, although
  the monitor has exited low power mode, then suspend again immediately.
  Can successfully waking up the system after that, but once the system
  reaches the idle time again, the issue appears repeatedly. From the
  system log, a sleep request is following the wake request.

  Hardware configuration also counts. It is hard to reproduce the issue
  with the system installed on SSD or with a lower resolution monitor;
  graphics card may also affect. It's likely to be a timing issue.

  ## Environment
  Machine: Dell Precision 7920 Tower.
  Monitor: Philips 288P6L
  DistroRelease: Ubuntu 18.04.2
  Graphics card: Nvidia Quadro P2200
  Nvidia driver version: 418.74
  CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz

  ## Steps to reproduce:
  Turn on automatic suspend in Settings->Power
  Wait for the system to suspend
  Wake up the system via pressing power button or keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1832693/+subscriptions

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

[Desktop-packages] [Bug 1834318] Re: Warning from Google about Ubuntu

2019-06-26 Thread Michal Predotka

So to report this as a bug, I need to wait until Ubuntu stops working
with Google account?

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

Title:
  Warning from Google about Ubuntu

Status in gnome-online-accounts package in Ubuntu:
  Invalid

Bug description:
  I'm not sure if it is a correct place to report this problem.

  I use Ubuntu 18.04. 
  Yesterday I've got an email from Google warning that "Ubuntu" will lose 
access to my Google account if it will not comply with new Google policy 
requirement.

  Screenshot attached and here's the full text of the email:

  Hi,

  Although you don’t need to do anything, we wanted to let you know that the 
following apps may no longer be able to access some data in your Google 
account, including your Gmail content. If these apps are unable to meet the 
deadline to comply with our updated data policy requirements, they'll lose 
access to your account from 15 July 2019.
  Ubuntu

  We are making this change as part of ongoing efforts to make sure that
  your data is protected and private.

  You can always view, manage and remove apps to which you’ve given
  access to your account by visiting your Google account.

  Thanks,
  The Google Accounts team

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

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

[Desktop-packages] [Bug 1834318] Re: Warning from Google about Ubuntu

2019-06-26 Thread lotuspsychje

This is not an ubuntu bug, but a warning from google updating data
policy

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Invalid

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

Title:
  Warning from Google about Ubuntu

Status in gnome-online-accounts package in Ubuntu:
  Invalid

Bug description:
  I'm not sure if it is a correct place to report this problem.

  I use Ubuntu 18.04. 
  Yesterday I've got an email from Google warning that "Ubuntu" will lose 
access to my Google account if it will not comply with new Google policy 
requirement.

  Screenshot attached and here's the full text of the email:

  Hi,

  Although you don’t need to do anything, we wanted to let you know that the 
following apps may no longer be able to access some data in your Google 
account, including your Gmail content. If these apps are unable to meet the 
deadline to comply with our updated data policy requirements, they'll lose 
access to your account from 15 July 2019.
  Ubuntu

  We are making this change as part of ongoing efforts to make sure that
  your data is protected and private.

  You can always view, manage and remove apps to which you’ve given
  access to your account by visiting your Google account.

  Thanks,
  The Google Accounts team

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

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

[Desktop-packages] [Bug 1834318] [NEW] Warning from Google about Ubuntu

2019-06-26 Thread Michal Predotka

Public bug reported:

I'm not sure if it is a correct place to report this problem.

I use Ubuntu 18.04. 
Yesterday I've got an email from Google warning that "Ubuntu" will lose access 
to my Google account if it will not comply with new Google policy requirement.

Screenshot attached and here's the full text of the email:

Hi,

Although you don’t need to do anything, we wanted to let you know that the 
following apps may no longer be able to access some data in your Google 
account, including your Gmail content. If these apps are unable to meet the 
deadline to comply with our updated data policy requirements, they'll lose 
access to your account from 15 July 2019.
Ubuntu

We are making this change as part of ongoing efforts to make sure that
your data is protected and private.

You can always view, manage and remove apps to which you’ve given access
to your account by visiting your Google account.

Thanks,
The Google Accounts team

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Attachment added: "google-ubuntu.png"
   
https://bugs.launchpad.net/bugs/1834318/+attachment/5273452/+files/google-ubuntu.png

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

Title:
  Warning from Google about Ubuntu

Status in gnome-online-accounts package in Ubuntu:
  Invalid

Bug description:
  I'm not sure if it is a correct place to report this problem.

  I use Ubuntu 18.04. 
  Yesterday I've got an email from Google warning that "Ubuntu" will lose 
access to my Google account if it will not comply with new Google policy 
requirement.

  Screenshot attached and here's the full text of the email:

  Hi,

  Although you don’t need to do anything, we wanted to let you know that the 
following apps may no longer be able to access some data in your Google 
account, including your Gmail content. If these apps are unable to meet the 
deadline to comply with our updated data policy requirements, they'll lose 
access to your account from 15 July 2019.
  Ubuntu

  We are making this change as part of ongoing efforts to make sure that
  your data is protected and private.

  You can always view, manage and remove apps to which you’ve given
  access to your account by visiting your Google account.

  Thanks,
  The Google Accounts team

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

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

[Desktop-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_

** Description changed:

+ [Impact]
+ 
  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17
+ 
+ This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
+ 
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=month
+ 
+ [Test Case]
+ 
+ No manual test case known. We just wait and watch errors.ubuntu.com to
+ see where the most crashes are.
+ 
+ [Regression Potential]
+ 
+ Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
+ 18.10 and later for a year so far.
  
  ---
  
  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

** Description changed:

  [Impact]
  
  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17
  
  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=month
  
  [Test Case]
  
  No manual test case known. We just wait and watch errors.ubuntu.com to
  see where the most crashes are.
  
  [Regression Potential]
  
  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.
  
- ---
+ [Original Report]
  
  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx

[Desktop-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

** Description changed:

+ [Impact]
+ 
  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
  https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
  https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669
+ 
+ This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
+ 
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=month
+ 
+ [Test Case]
+ 
+ No manual test case known. We just wait and watch errors.ubuntu.com to
+ see where the most crashes are.
+ 
+ [Regression Potential]
+ 
+ Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
+ 18.10 and later for a year so far.
  
  ---
  
  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.
  
  Got an other crash, and that time 'sound' is fully lost (pulseaudio not
  reloaded). Wonder if lp:1662860 can be concerned.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

** Description changed:

  [Impact]
  
  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
  https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
  https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669
  
  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=month
  
  [Test Case]
  
  No manual test case known. We just wait and watch errors.ubuntu.com to
  see where the most crashes are.
  
  [Regression Potential]
  
  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.
  
- ---
+ [Original Report]
  
  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.
  
  Got an other crash, and that time 'sound' is fully lost (pulseaudio not
  reloaded). Wonder if lp:1662860 can be concerned.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID

Re: [Desktop-packages] [Bug 1825621] Re: Textbearbeitung -gedit- läßt sich nicht sauber aufrufen. Keine weiße Fläche, Eingaben sind nicht möglich

2019-06-26 Thread Bors Johannes

Sehr geehrte Damen und Herren,
mein Problem ist gelöst. Ich habe Ubuntu 18.04 neu auf mein
Laptop installiert und die "Textbearbeitung" funktioniert jetzt
reibungslos.
Ich bitte zu entschuldigen, dass ich mich nicht mehr gemeldet habe.

Wo der Fehler gelegen hat ist jetzt natürlich nicht mehr zu klären. 
Mit freundlichem Gruß
Johannes Bors



> Launchpad Bug Tracker <1825...@bugs.launchpad.net> hat am 23. Juni 2019 um 
> 06:18 geschrieben:
> 
> 
> [Expired for gedit (Ubuntu) because there has been no activity for 60
> days.]
> 
> ** Changed in: gedit (Ubuntu)
>Status: Incomplete => Expired
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1825621
> 
> Title:
>   Textbearbeitung -gedit- läßt sich nicht sauber aufrufen. Keine weiße
>   Fläche, Eingaben sind nicht möglich
> 
> Status in gedit package in Ubuntu:
>   Expired
> 
> Bug description:
>   /home/nomennescio/Schreibtisch/gedit nach Aufruf.png
>   Dies erschein nach Aufruf; damit zu arbeiten ist nicht möglich
>   Vielen Dank für Ihre Hilfe.
>   Johannes Bors
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gedit 3.28.1-1ubuntu1.1
>   ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
>   Uname: Linux 4.15.0-47-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 20 10:23:33 2019
>   InstallationDate: Installed on 2019-04-07 (12 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
> (20180426)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=de_DE.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gedit
>   UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825621/+subscriptions

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

Title:
  Textbearbeitung -gedit- läßt sich nicht sauber aufrufen. Keine weiße
  Fläche, Eingaben sind nicht möglich

Status in gedit package in Ubuntu:
  Expired

Bug description:
  /home/nomennescio/Schreibtisch/gedit nach Aufruf.png
  Dies erschein nach Aufruf; damit zu arbeiten ist nicht möglich
  Vielen Dank für Ihre Hilfe.
  Johannes Bors

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 10:23:33 2019
  InstallationDate: Installed on 2019-04-07 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

Upgraded libreoffice-l10n from 1:6.0.7-0ubuntu0.18.04.6 to
1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date
bionic amd64 VM, and verified that the test case passes.

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Committed
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

  [Impact]

   * This effects all libreoffice-gtk3 users wishing to embed videos
  into an Impress slide.

   * The fix is currently in LibreOffice 6.2.2+ on disco and eoan.

  [Test Case]

   1. Insert a video into an Impress slide
   2. Play the video
   3. The video should play within the slide (not fullscreen like this: 
https://youtu.be/77E6IzVJ5jA)

  [Regression Potential]

   * The fix is one line in the control file so potential for regression
  is low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1820062/+subscriptions

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

[Desktop-packages] [Bug 1827451] Re: Japanese new era "Reiwa(令和)" support

Upgraded libreoffice-l10n from 1:6.0.7-0ubuntu0.18.04.6 to
1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date
bionic amd64 VM, and verified that the test case passes.

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

Title:
  Japanese new era "Reiwa(令和)" support

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Committed
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This effects all users who use the Japanese era date format in
  LibreOffice.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Start Calc
   2. Put "01/05/2019" into a cell
   3. Right-click on the cell and select "Format Cells"
   4. Set “Language" to "Japanese"
   5. Set “Format" to "H11.12.31"
   6. Cell should show "R1.05.01" (not "N1.05.01”)
   7. Set “Format" to "平成11年12月31日"
   8. Cell should show "令和1年5月1日" (not "平成31年5月1日")

  [Regression Potential]

   * The fix is minor so potential for regression is low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

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

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

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

Upgraded libreoffice-l10n from 1:6.0.7-0ubuntu0.18.04.6 to
1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date
bionic amd64 VM, and verified that the test case passes.

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Committed
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in openjdk-lts source package in Disco:
  New
Status in libreoffice package in Debian:
  Won't Fix

Bug description:
  [Impact]

   * A recent OpenJDK update changes the value of the "java.vendor"
  property from "Oracle Corporation" to "Private Build". This breaks the
  code in LibreOffice that detects an installed JVM.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Launch the LibreOffice Start Center
   2. Open Tools > Options
   3. Navigate to LibreOffice > Advanced
   4. A JRE should be listed with Location: /usr/lib/jvm/...

  [Regression Potential]

   * This fix is small and concentrated so potential for regression
  should be relatively low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+subscriptions

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

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.6 to
1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date
bionic amd64 VM, and verified that the crash is now resolved.

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

Title:
  LIbreoffice crashes on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice-l10n source package in Bionic:
  Fix Committed
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*'
  packages installed.

   * The fix is currently in LibreOffice 6.2.0+ on disco and eoan.

  [Test Case]

   1. apt install cpdb-backend-gcp
   2. run LibreOffice

  [Regression Potential]

   * We're backporting a patch that has already been applied to 6.2.0+
  with no regression, so potential for regression here is low.

   * A combination of autopkgtests and manual testing should provide
  reasonable confidence that no regressions sneaked in.

  [Original Description]

  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:

  $ libreoffice --norestore
  Application Error

  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]

  I have tried entirely removing my profile, ~/.config/libreoffice , but

[Desktop-packages] [Bug 1834293] Re: screen