date:20190722

It sounds like your PrtScn button might be stuck down. This can happen
without it looking stuck down. Please try tapping PrtScn several times
to try and unstick it.


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  screen

Status in Ubuntu:
  Incomplete

Bug description:
  ubuntu does not stop taking screen shots without stopping, making
  annoying noise system crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 22 22:34:39 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
 Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
  MachineType: Semp Toshiba IS 1414
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: MTVNCRB01.86C..X.00
  dmi.board.name: IS 1414
  dmi.board.vendor: Semp Toshiba
  dmi.board.version: CRB
  dmi.chassis.type: 10
  dmi.chassis.vendor: Semp Toshiba
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga&ICH9MChipset:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr:
  dmi.product.name: IS 1414
  dmi.product.version: 20ga & ICH9M Chipset
  dmi.sys.vendor: Semp Toshiba
  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.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1837453] Re: 18.04 overheating at lock screen or closed lid

Please:

  sudo apt install openssh-server

so that you can log into the machine before/while the lid is closed.

Then while the lid is closed and the machine overheating, please run:

  top

and tell us what process is using the most CPU? Or just take a
screenshot.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  18.04 overheating at lock screen or closed lid

Status in Ubuntu:
  Incomplete

Bug description:
  On KDE or Normal Gnome session when the system goes to lock screen no
  matter how (If I press mod+l or log out, or shut lid) The system gets
  extremely hot. I am unable to touch the bottom of the laptop it's that
  hot.

  It continues to get hotter and hotter. It continues to do this until
  the system crashes and reboots, or runs out of battery.

  If I am not away for to0 long sometimes the system is still back up. It is 
very hot but when I log in, 
  The temperature cools down and feels like a normal heat. 

  I do and have installed i3WM. From what I noticed I have it has ever
  happened with i3WM.

  But I defiantly get it with KDE or the Stock Gnome session.

  I have tried to change the power and lock screen settings to ensure it
  is not going into suspend but this hasn't made a difference from what
  I can tell.

  I have told the system to go to lock screen when I close the lid.

  I have never seen this issue on my home PC only my work laptop. No
  other colleague has experienced this issue either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  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: KDE
  Date: Mon Jul 22 19:50:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-52-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-54-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5063]
  InstallationDate: Installed on 2018-06-11 (406 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20J1004DUK
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0JET27W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J1004DUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0JET27W(1.12):bd08/14/2017:svnLENOVO:pn20J1004DUK:pvrThinkPad132ndGen:rvnLENOVO:rn20J1004DUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad 13 2nd Gen
  dmi.product.name: 20J1004DUK
  dmi.product.version: ThinkPad 13 2nd Gen
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1800749] Re: Ubuntu doesn't like fullscreen mode for sauerbraten(game)

** Summary changed:

- Ubuntu 18.10 doesn't like fullscreen mode for sauerbraten(game)
+ Ubuntu doesn't like fullscreen mode for sauerbraten(game)

** Tags removed: cosmic
** Tags added: disco

** Changed in: gnome-shell (Ubuntu)
   Status: Won't Fix => Confirmed

** Changed in: mutter (Ubuntu)
   Status: Won't Fix => Confirmed

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

Title:
  Ubuntu doesn't like fullscreen mode for sauerbraten(game)

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

Bug description:
  When I run sauerbraten in fullscreen mode in Ubuntu 18.10, there are
  "skips" in the animation of the rotating cubes.  Upon further
  "evaluation", I noticed the system mouse pointer "popping up" briefly
  at the moment of the glitch(near the crosshair) about once a second.
  When not in fullscreen, the animation is smooth(no visible
  skips/glitches) and I don't see the system mouse pointer "popping up"
  every second.  It works fine in fullscreen mode in Ubuntu 18.04.

  To recreate/observe the problem:
  0. Boot into Ubuntu 18.10
  1. Install sauerbraten
  2. Start sauerbraten
  3. Set sauerbraten to fullscreen 
mode(sauerbraten->options..->display->fullscreen)
  4. Start a game(I like sauerbraten->bot match->start match->ctf->europium)
  5. Move forward with the 'w' key(steer with the mouse) to some rotating 
cubes.  Here you should notice the glitch in rotation and the _system_ mouse 
pointer flickering in and out near the crosshair at a rate of about once a 
second.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.399
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 30 21:46:28 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2102]
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper 
iso-scan/filename=/Downloads/username-18.10-desktop-amd64.iso ipv6.disable=1 
net.ifnames=0 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.407
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.407:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  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/ubuntu/+source/gnome-shell/+bug/1800749/+subscriptions

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

[Desktop-packages] [Bug 1837489] [NEW] screen

2019-07-22 Thread Muryllo Sirqueira Lopes dos Santos

Public bug reported:

ubuntu does not stop taking screen shots without stopping, making
annoying noise system crashes

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 22 22:34:39 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
   Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
MachineType: Semp Toshiba IS 1414
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: MTVNCRB01.86C..X.00
dmi.board.name: IS 1414
dmi.board.vendor: Semp Toshiba
dmi.board.version: CRB
dmi.chassis.type: 10
dmi.chassis.vendor: Semp Toshiba
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga&ICH9MChipset:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr:
dmi.product.name: IS 1414
dmi.product.version: 20ga & ICH9M Chipset
dmi.sys.vendor: Semp Toshiba
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.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1837489

Title:
  screen

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu does not stop taking screen shots without stopping, making
  annoying noise system crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 22 22:34:39 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
 Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
  MachineType: Semp Toshiba IS 1414
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: MTVNCRB01.86C..X.00
  dmi.board.name: IS 1414
  dmi.board.vendor: Semp Toshiba
  dmi.board.version: CRB
  dmi.chassis.type: 10
  dmi.chassis.vendor: Semp Toshiba
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga&ICH9MChipset:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr:
  dmi.product.name: IS 1414
  dmi.product.version: 20ga & ICH9M Chipset
  dmi.sys.vendor: Semp Toshiba
  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.3
  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-i

[Desktop-packages] [Bug 1800749] Re: Ubuntu 18.10 doesn't like fullscreen mode for sauerbraten(game)

2019-07-22 Thread Paul

The bug started Ubuntu 18.10 and continues in 19.04 with all updates
applied as of the date of this comment.  Again, it seems like the Ubuntu
Desktop, as of 18.10, is continuously(once a second) hijacking the mouse
and keyboard from Sauerbraten when running in full-screen mode.  Thanks.

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

Title:
  Ubuntu 18.10 doesn't like fullscreen mode for sauerbraten(game)

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When I run sauerbraten in fullscreen mode in Ubuntu 18.10, there are
  "skips" in the animation of the rotating cubes.  Upon further
  "evaluation", I noticed the system mouse pointer "popping up" briefly
  at the moment of the glitch(near the crosshair) about once a second.
  When not in fullscreen, the animation is smooth(no visible
  skips/glitches) and I don't see the system mouse pointer "popping up"
  every second.  It works fine in fullscreen mode in Ubuntu 18.04.

  To recreate/observe the problem:
  0. Boot into Ubuntu 18.10
  1. Install sauerbraten
  2. Start sauerbraten
  3. Set sauerbraten to fullscreen 
mode(sauerbraten->options..->display->fullscreen)
  4. Start a game(I like sauerbraten->bot match->start match->ctf->europium)
  5. Move forward with the 'w' key(steer with the mouse) to some rotating 
cubes.  Here you should notice the glitch in rotation and the _system_ mouse 
pointer flickering in and out near the crosshair at a rate of about once a 
second.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.399
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 30 21:46:28 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2102]
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper 
iso-scan/filename=/Downloads/username-18.10-desktop-amd64.iso ipv6.disable=1 
net.ifnames=0 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.407
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.407:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  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/ubuntu/+source/gnome-shell/+bug/1800749/+subscriptions

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

[Desktop-packages] [Bug 1837448] Re: gnome-keyring-daemon constantly hangs on fresh ubuntu 19.04 install

2019-07-22 Thread Tessa

looks like it's not just ssh. when the screen is locked, unlocking the
screen hangs too unless I pop over to another tty and kill gnome-
keyring-daemon. as well, other services which use the keyring, like aws-
vault also hang. (https://github.com/99designs/aws-vault)

does the keyring daemon output logs anywhere?

** Summary changed:

- ssh key actions hang with gnome-keyring-daemon
+ gnome-keyring-daemon constantly hangs on fresh ubuntu 19.04 install

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

Title:
  gnome-keyring-daemon constantly hangs on fresh ubuntu 19.04 install

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  fresh install of ubuntu 19.04, and using all my ssh keys I had before the 
reinstall, anything with ssh just hangs when gnome-keyring-daemon is providing 
the keys:
  ```
  ssh -v my-test-host
  [...]
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey after 134217728 blocks
  [ hangs here forever ]
  ```

  it appears to be setting at least some of the environment vars incorrectly, 
with the agent pid pointing to nothing:
  ```
  $ export | grep SSH
  declare -x SSH_AGENT_PID="3300"
  declare -x SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"
  $ ps auxf | grep 3300
  tessa 5950  0.0  0.0   8856   760 pts/0S+   11:50   0:00  
|   |   \_ grep --color=auto 3300
  $ ps axf | grep keyring
   2642 pts/0S+ 0:00  |   |   \_ grep --color=auto keyring
  27662 ?S  0:00 /usr/bin/ssh-agent -D -a 
/run/user/1000/keyring/.ssh
   6177 ?Sl44:10 /usr/bin/gnome-keyring-daemon --daemonize --login
  $ ls -lah /run/user/1000/keyring/
  total 0
  drwx--  2 tessa tessa 120 Jul 22 10:54 .
  drwx-- 11 tessa tessa 260 Jul 22 10:47 ..
  srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 control
  srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 pkcs11
  srw---  1 tessa tessa   0 Jul 22 10:47 .ssh
  srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 ssh

  ```

  if I set the SSH_AUTH_SOCK to the path being set by ssh-agent instead
  of gnome-keyring-daemon, things work correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 22 11:02:52 2019
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1728012] Update Released

2019-07-22 Thread Manuel

Worked for me...
~$ uname -a
Linux hades 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
~$ lsb_release -a
LSB Version: core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

Manuel SCHULTE
*Managing Director, Olympus Consulting sprl*
*gsm :* +32(0)498 881 718
*mail :* manuel.schu...@olympusconsulting.eu
*web :* http://www.olympusconsulting.eu/


Le dim. 21 juil. 2019 à 23:35, Phil  a écrit :

> Hi Lukasz,
>
> I am an Ubuntu user but *not* a technician so please bear with me.  Your
> e-mail says "The verification of the Stable Release Update for
> sane-backends has
> completed successfully and the package has now been released to -updates."
>  Do you know what release will contain the fix and when the release will
> occur?
> (I updated my system a couple of minutes ago and the scanner is still not
> working.)  Should I have checkmarked Pre-released updates Bionic-proposed
> in the Developer Options tab of the update settings - see picture?  (The
> release I'm using is 18.04.02)  Thanks!
>
>
> [image: image.png]
>
>
>
> On Thu, Jul 18, 2019 at 3:26 AM Łukasz Zemczak <1728...@bugs.launchpad.net
> >
> wrote:
>
> > The verification of the Stable Release Update for sane-backends has
> > completed successfully and the package has now been released to
> > -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
> > unsubscribed and will not receive messages about this bug report.  In
> > the event that you encounter a regression using the package from
> > -updates please report a new bug using ubuntu-bug and tag the bug report
> > regression-update so we can easily find any regressions.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1822360).
> > 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:
> >   Fix Released
> > Status in sane-backends package in Debian:
> >   Fix Released
> >
> > Bug description:
> >   To the sponsor: Please upload to bionic using the attached sane-
> >   backends_lp1728012_bionic.debdiff.
> >
> >   [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 Workcent

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

2019-07-22 Thread Manuel

Hi,

I received the update yesterday. Success!!!
Could scan without issues and my scanner got recognized with all features
working fine!
Thanks a lot, kudos

Manuel SCHULTE
*Managing Director, Olympus Consulting sprl*
*gsm :* +32(0)498 881 718
*mail :* manuel.schu...@olympusconsulting.eu
*web :* http://www.olympusconsulting.eu/


Le lun. 22 juil. 2019 à 01:55, Gunnar Hjalmarsson <
1728...@bugs.launchpad.net> a écrit :

> Hi Phil,
>
> Łukasz will probably not see your question. But this fix is about Ubuntu
> 18.04, and no, the "Pre-released updates" option does not need to be
> checked - the "Recommended updates" option in the "Updates" tab is
> sufficient (and that one is checked by default).
>
> To confirm that you got the fix you can open a terminal window and run
> this command:
>
> dpkg-query -W libsane1 libsane-common sane-utils
>
> The version you should have is 1.0.27-1~experimental3ubuntu2.1
>
> Also, please note that there are multiple possible reasons why your
> scanner refuses to scan. This fix addresses one particular issue which
> was a regression compared to Ubuntu 16.04.
>
> To get help with your particular problem, please use e.g. Ask Ubuntu or
> some other support resource as mentioned here:
>
> https://ubuntu.com/support/community-support
>
> This is a bug report intended to report, investigate and keep track of
> bugs. It's not a support channel.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728012
>
> Title:
>   Many 3rd party scanner drivers are broken by a sane change
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions
>


** Attachment added: "20190722_ubuntu18.04_sane-update-ok.png"
   
https://bugs.launchpad.net/bugs/1728012/+attachment/5278552/+files/20190722_ubuntu18.04_sane-update-ok.png

-- 
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:
  Fix Released
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  To the sponsor: Please upload to bionic using the attached sane-
  backends_lp1728012_bionic.debdiff.

  [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.04 is an LTS release, so
  backporting is warranted for the 18.04 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

[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

2019-07-22 Thread Thomas SIMON

So it seems that it does away with the following kernel option:
i915.enable_psr=0

It seems from some Dell user forum that some have had the same issues on
Windows and disabling the panel self refresh worked for them so I was
searching along these lines.

I'm certain it's not a "clean" fix however to deactivate a measure
that's suppose to save battery.

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1837452] [NEW] segfault at 0 {...} error 4 in libgio-2.0.so.0.5600.4

2019-07-22 Thread Ken Sharp

Public bug reported:

Shotwell segfaults every time I close it.

shotwell[11186]: segfault at 0 ip 7f33b2e3b7e0 sp 7aeabaa8
error 4 in libgio-2.0.so.0.5600.4[7f33b2d9+195000]

I have no idea why.

libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(0x7fc9005ed000)

Apport has automatically reported the crash.

ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: called for pid 11186, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: executable: 
/usr/bin/shotwell (command line "shotwell /tmp/P7200010.JPG")
ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: debug: session gdbus call: 
(true,)

ERROR: apport (pid 11201) Sat Jul 20 11:59:05 2019: wrote report
/var/crash/_usr_bin_shotwell.1000.crash

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: shotwell 0.28.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Jul 22 19:54:12 2019
InstallationDate: Installed on 2019-06-09 (42 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  segfault at 0 {...} error 4 in libgio-2.0.so.0.5600.4

Status in shotwell package in Ubuntu:
  New

Bug description:
  Shotwell segfaults every time I close it.

  shotwell[11186]: segfault at 0 ip 7f33b2e3b7e0 sp 7aeabaa8
  error 4 in libgio-2.0.so.0.5600.4[7f33b2d9+195000]

  I have no idea why.

  libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  (0x7fc9005ed000)

  Apport has automatically reported the crash.

  ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: called for pid 11186, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: executable: 
/usr/bin/shotwell (command line "shotwell /tmp/P7200010.JPG")
  ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: debug: session gdbus 
call: (true,)

  ERROR: apport (pid 11201) Sat Jul 20 11:59:05 2019: wrote report
  /var/crash/_usr_bin_shotwell.1000.crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: shotwell 0.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Jul 22 19:54:12 2019
  InstallationDate: Installed on 2019-06-09 (42 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1837453] [NEW] 18.04 overheating at lock screen or closed lid

2019-07-22 Thread Alan Auckland

Public bug reported:

On KDE or Normal Gnome session when the system goes to lock screen no
matter how (If I press mod+l or log out, or shut lid) The system gets
extremely hot. I am unable to touch the bottom of the laptop it's that
hot.

It continues to get hotter and hotter. It continues to do this until the
system crashes and reboots, or runs out of battery.

If I am not away for to0 long sometimes the system is still back up. It is very 
hot but when I log in, 
The temperature cools down and feels like a normal heat. 

I do and have installed i3WM. From what I noticed I have it has ever
happened with i3WM.

But I defiantly get it with KDE or the Stock Gnome session.

I have tried to change the power and lock screen settings to ensure it
is not going into suspend but this hasn't made a difference from what I
can tell.

I have told the system to go to lock screen when I close the lid.

I have never seen this issue on my home PC only my work laptop. No other
colleague has experienced this issue either.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
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: KDE
Date: Mon Jul 22 19:50:50 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-52-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-54-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:5063]
InstallationDate: Installed on 2018-06-11 (406 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20J1004DUK
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0JET27W (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20J1004DUK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0JET27W(1.12):bd08/14/2017:svnLENOVO:pn20J1004DUK:pvrThinkPad132ndGen:rvnLENOVO:rn20J1004DUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad 13 2nd Gen
dmi.product.name: 20J1004DUK
dmi.product.version: ThinkPad 13 2nd Gen
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~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 N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic kubuntu 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/1837453

Title:
  18.04 overheating at lock screen or closed lid

Status in xorg package in Ubuntu:
  New

Bug description:
  On KDE or Normal Gnome session when the system goes to lock screen no
  matter how (If I press mod+l or log out, or shut lid) The system gets
  extremely hot. I am unable to touch the bottom of the laptop it's that
  hot.

  It continues to get hotter and hotter. It continues to do this until
  the system crashes and reboots, or runs out of battery.

  If I am not away for to0 long sometimes the system is still back up. It is 
very hot but when I log in, 
  The temperature cools down and feels like a normal heat. 

  I do and have installed i3WM. From what I noticed I have it has ever
  happened with i3WM.

  But I defiantly get it with KDE or the Stock Gnome session.

  I have tried to change the power and lock screen settings to ensure it
  is not going into suspend but this hasn't made a difference from what
  I can tell.

  I have told the system to go to lock screen when I close the lid.

  I have never seen this issue on my home PC only my work laptop. No
  other colleague has

[Desktop-packages] [Bug 1837448] [NEW] ssh key actions hang with gnome-keyring-daemon

2019-07-22 Thread Tessa

Public bug reported:

fresh install of ubuntu 19.04, and using all my ssh keys I had before the 
reinstall, anything with ssh just hangs when gnome-keyring-daemon is providing 
the keys:
```
ssh -v my-test-host
[...]
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
[ hangs here forever ]
```

it appears to be setting at least some of the environment vars incorrectly, 
with the agent pid pointing to nothing:
```
$ export | grep SSH
declare -x SSH_AGENT_PID="3300"
declare -x SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"
$ ps auxf | grep 3300
tessa 5950  0.0  0.0   8856   760 pts/0S+   11:50   0:00  | 
  |   \_ grep --color=auto 3300
$ ps axf | grep keyring
 2642 pts/0S+ 0:00  |   |   \_ grep --color=auto keyring
27662 ?S  0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh
 6177 ?Sl44:10 /usr/bin/gnome-keyring-daemon --daemonize --login
$ ls -lah /run/user/1000/keyring/
total 0
drwx--  2 tessa tessa 120 Jul 22 10:54 .
drwx-- 11 tessa tessa 260 Jul 22 10:47 ..
srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 control
srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 pkcs11
srw---  1 tessa tessa   0 Jul 22 10:47 .ssh
srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 ssh

```

if I set the SSH_AUTH_SOCK to the path being set by ssh-agent instead of
gnome-keyring-daemon, things work correctly.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-keyring 3.31.91-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 22 11:02:52 2019
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  ssh key actions hang with gnome-keyring-daemon

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  fresh install of ubuntu 19.04, and using all my ssh keys I had before the 
reinstall, anything with ssh just hangs when gnome-keyring-daemon is providing 
the keys:
  ```
  ssh -v my-test-host
  [...]
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey after 134217728 blocks
  [ hangs here forever ]
  ```

  it appears to be setting at least some of the environment vars incorrectly, 
with the agent pid pointing to nothing:
  ```
  $ export | grep SSH
  declare -x SSH_AGENT_PID="3300"
  declare -x SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"
  $ ps auxf | grep 3300
  tessa 5950  0.0  0.0   8856   760 pts/0S+   11:50   0:00  
|   |   \_ grep --color=auto 3300
  $ ps axf | grep keyring
   2642 pts/0S+ 0:00  |   |   \_ grep --color=auto keyring
  27662 ?S  0:00 /usr/bin/ssh-agent -D -a 
/run/user/1000/keyring/.ssh
   6177 ?Sl44:10 /usr/bin/gnome-keyring-daemon --daemonize --login
  $ ls -lah /run/user/1000/keyring/
  total 0
  drwx--  2 tessa tessa 120 Jul 22 10:54 .
  drwx-- 11 tessa tessa 260 Jul 22 10:47 ..
  srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 control
  srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 pkcs11
  srw---  1 tessa tessa   0 Jul 22 10:47 .ssh
  srwxrwxr-x  1 tessa tessa   0 Jul 22 10:54 ssh

  ```

  if I set the SSH_AUTH_SOCK to the path being set by ssh-agent instead
  of gnome-keyring-daemon, things work correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 22 11:02:52 2019
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration

2019-07-22 Thread C. Jeffery Small

I am VERY interested in continuing work on this.  I'm now running 19.04
and the problem persists.  I cannot change the status so please update
it.

There has been a long running discussion on the Xfce buglist which you
can review here:

https://bugzilla.xfce.org/show_bug.cgi?id=15116

The problem seems to be that the move to gtk3 is the source of the
condition as it has dropped support for multiple monitors.  Olivier
Fourdan is maintaining xfwm4 and he has apparently done something
internally that allows X11-aware applications to be launched on a
separate display (:0.1) in addition to the native display (:0.0), but
none of the other Xfce components such as the panel, desktop, etc have
the ability to run more than one instance on the main display.

In this forum discussion:

https://forum.xfce.org/viewtopic.php?pid=50336#p50336

member gert pointed to this patch in the gtk3 repository that seems to
indicate that multi-screen support has been added back into the toolkit.

https://github.com/xfce-
mirror/xfwm4/commit/b52c2f5b740434803342c471d4dcb5dd62eb99a1

However, this patched version of gtk has not yet made it into a Ubuntu
distribution.

Losing multi-headed independent desktop support has been a terrible step
backwards for Ubuntu.  Please look into this more closely and make sure
that the 19.10 release gets the tools required to get this capability
restored.

I'll provide additional info if necessary.  However, as an end0user in
this arena, I don't have more insights into the interactions of the
display components making up the various desktop environments.


On a couple of other forums, I asked whether there was another flavor of Ubuntu 
that was properly supporting multiple screens.  I received zero replies.  
Multiple independent desktops is critical (as opposed to Xinerama mode) so that 
material can be displayed statically on one display while changing workspaces 
on the other screen.

** Bug watch added: Xfce Bugzilla #15116
   https://bugzilla.xfce.org/show_bug.cgi?id=15116

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

Title:
  Ubuntu 18.10 broke dual-screen dual-desktop configuration

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  I'm running Xubuntu.  I finally reported this problem to the Xfce
  group and received this response:

  "As arandr/xrandr does not detect correctly your 2nd screen, this
  seems that it is not related directly to Xfce, but a bug in Xubuntu
  stack.  Can you please open a bug on Xubuntu project if the issue is
  still present for you?"

  Thus this bug report.

  
  I've been running Xubuntu for years with two monitors, each running an 
independent xfce4 desktop -- i.e., configured without Xinerama. This has worked 
fine for every upgrade through 18.04.  When upgrading to 18.10, something 
significant changed and the the second monitor (display :0.1) was disabled.  
After much reading and work, I have only been able to restore some extremely 
hobbled functionality.  I am unable to get a second xfce4-desktop, panel or 
window manager running on the second screen.  I have assembled detailed 
screenshots and command output at the following link:

  http://smallthoughts.com/xfce/xfce.html

  I'm using an NVIDIA Quadro K-4000 graphics card and no hardware
  changes were made between 18.04 and 18.10.

  The nvidia-settings tool reports both monitors active (as configured
  in /etc/X11/xorg.conf) but the xfce4-display-settings and aarandr
  tools each show only one display (although xrandr can be forced to
  report on the second display.  See full documentation at the above
  link.)

  What changed in the latest release, and what needs to be done to get
  the second monitor running a second desktop once again?  I have been
  struggling with this for many months now and it has severely impacted
  the use of my system.  As a new release of Ubuntu in coming, I would
  appreciate it if this could be prioritized and addressed as quickly as
  possible.

  I will provide additional information upon request.

  P.S.:  There is really no documentation available on running multiple
  desktops on separate screens when Xinerama is not used to tie the
  screens together into a single desktop.  This is a common
  configuration and I would like to request that as part of the solution
  to this problem, the setup steps be documented and this multi-desktop
  configuration be made a standard part of the development and testing
  process for each Ubuntu release.

  13-> lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

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

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

[Desktop-packages] [Bug 1837437] Re: disk content permanently lost when changing LUKS password

2019-07-22 Thread Iain Lane

thanks for filing

I'm guessing we should reproduce the problem, see if it happens on
bionic & then backport libblockdev 2.20-7+deb10u1

** Package changed: gnome-disk-utility (Ubuntu) => libblockdev (Ubuntu)

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

Title:
  disk content permanently lost when changing LUKS password

Status in libblockdev package in Ubuntu:
  New
Status in gnome-disk-utility package in Debian:
  Unknown

Bug description:
  This is fixed upstream.  Logging this bug to track the fix in to
  Ubuntu.

  
  From the upstream bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893

  Dear Maintainer,

 * What led up to the situation?

  Install system using normal full disk encryption LUKS+Ext4.
  After install open gnome-disk-utility and change
  encryption password. It gives some error dialog and
  now you are royally screwed. It deleted the only
  LUKS keyslot. Cannot add new keyslots because of that.
  All data will be lost after reboot.

  Here is output of luksdump:

  udo cryptsetup luksDump /dev/sda5
  LUKS header information
  Version:2
  Epoch:  4
  Metadata area:  16384 [bytes]
  Keyslots area:  1678 [bytes]
  UUID:   3c16ad4c-294c-4547-bf3e-bb8864ba5ea3
  Label:  (no label)
  Subsystem:  (no subsystem)
  Flags:  (no flags)

  Data segments:
0: crypt
  offset: 16777216 [bytes]
  length: (whole device)
  cipher: aes-xts-plain64
  sector: 512 [bytes]

  Keyslots:
  Tokens:
  Digests:
0: pbkdf2
  Hash:   sha256
  Iterations: 59904
  Salt:   XX XX XX XX XX 
  Digest: XX XX XX XX XX ...

  

  I changed salt and digest. No Keyslots are present!!!

  I tried this 2 times in a row with new install,
  exactly same result.


  -- System Information:
  Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.0.8-xanmod5 (SMP w/2 CPU cores; PREEMPT)
  Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages gnome-disk-utility depends on:
  ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
  ii  libatk1.0-0  2.30.0-2
  ii  libc62.28-10
  ii  libcairo21.16.0-4
  ii  libcanberra-gtk3-0   0.30-7
  ii  libdvdread4  6.0.1-1
  ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
  ii  libglib2.0-0 2.58.3-1
  ii  libgtk-3-0   3.24.5-1
  ii  liblzma5 5.2.4-1
  ii  libnotify4   0.7.7-4
  ii  libpango-1.0-0   1.42.4-6
  ii  libpangocairo-1.0-0  1.42.4-6
  ii  libpwquality11.4.0-3
  ii  libsecret-1-00.18.7-1
  ii  libsystemd0  241-3
  ii  libudisks2-0 2.8.1-4
  ii  udisks2  2.8.1-4

  gnome-disk-utility recommends no packages.

  gnome-disk-utility suggests no packages.

  -- no debconf information

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

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

[Desktop-packages] [Bug 1837437] Re: disk content permanently lost when changing LUKS password

2019-07-22 Thread Tom Reynolds

Possible Workaround (untested):
This only applies if you have not rebooted / closed the LUKS volume. Follow 
steps 7 to 9 of https://www.thegeekstuff.com/2016/03/cryptsetup-lukskey/

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

Title:
  disk content permanently lost when changing LUKS password

Status in gnome-disk-utility package in Ubuntu:
  New
Status in gnome-disk-utility package in Debian:
  Unknown

Bug description:
  This is fixed upstream.  Logging this bug to track the fix in to
  Ubuntu.

  
  From the upstream bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893

  Dear Maintainer,

 * What led up to the situation?

  Install system using normal full disk encryption LUKS+Ext4.
  After install open gnome-disk-utility and change
  encryption password. It gives some error dialog and
  now you are royally screwed. It deleted the only
  LUKS keyslot. Cannot add new keyslots because of that.
  All data will be lost after reboot.

  Here is output of luksdump:

  udo cryptsetup luksDump /dev/sda5
  LUKS header information
  Version:2
  Epoch:  4
  Metadata area:  16384 [bytes]
  Keyslots area:  1678 [bytes]
  UUID:   3c16ad4c-294c-4547-bf3e-bb8864ba5ea3
  Label:  (no label)
  Subsystem:  (no subsystem)
  Flags:  (no flags)

  Data segments:
0: crypt
  offset: 16777216 [bytes]
  length: (whole device)
  cipher: aes-xts-plain64
  sector: 512 [bytes]

  Keyslots:
  Tokens:
  Digests:
0: pbkdf2
  Hash:   sha256
  Iterations: 59904
  Salt:   XX XX XX XX XX 
  Digest: XX XX XX XX XX ...

  

  I changed salt and digest. No Keyslots are present!!!

  I tried this 2 times in a row with new install,
  exactly same result.


  -- System Information:
  Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 5.0.8-xanmod5 (SMP w/2 CPU cores; PREEMPT)
  Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages gnome-disk-utility depends on:
  ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
  ii  libatk1.0-0  2.30.0-2
  ii  libc62.28-10
  ii  libcairo21.16.0-4
  ii  libcanberra-gtk3-0   0.30-7
  ii  libdvdread4  6.0.1-1
  ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
  ii  libglib2.0-0 2.58.3-1
  ii  libgtk-3-0   3.24.5-1
  ii  liblzma5 5.2.4-1
  ii  libnotify4   0.7.7-4
  ii  libpango-1.0-0   1.42.4-6
  ii  libpangocairo-1.0-0  1.42.4-6
  ii  libpwquality11.4.0-3
  ii  libsecret-1-00.18.7-1
  ii  libsystemd0  241-3
  ii  libudisks2-0 2.8.1-4
  ii  udisks2  2.8.1-4

  gnome-disk-utility recommends no packages.

  gnome-disk-utility suggests no packages.

  -- no debconf information

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

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

[Desktop-packages] [Bug 1837437] [NEW] disk content permanently lost when changing LUKS password

2019-07-22 Thread Will Cooke

Public bug reported:

This is fixed upstream.  Logging this bug to track the fix in to Ubuntu.


>From the upstream bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893

Dear Maintainer,

   * What led up to the situation?

Install system using normal full disk encryption LUKS+Ext4.
After install open gnome-disk-utility and change
encryption password. It gives some error dialog and
now you are royally screwed. It deleted the only
LUKS keyslot. Cannot add new keyslots because of that.
All data will be lost after reboot.

Here is output of luksdump:

udo cryptsetup luksDump /dev/sda5
LUKS header information
Version:2
Epoch:  4
Metadata area:  16384 [bytes]
Keyslots area:  1678 [bytes]
UUID:   3c16ad4c-294c-4547-bf3e-bb8864ba5ea3
Label:  (no label)
Subsystem:  (no subsystem)
Flags:  (no flags)

Data segments:
  0: crypt
offset: 16777216 [bytes]
length: (whole device)
cipher: aes-xts-plain64
sector: 512 [bytes]

Keyslots:
Tokens:
Digests:
  0: pbkdf2
Hash:   sha256
Iterations: 59904
Salt:   XX XX XX XX XX 
Digest: XX XX XX XX XX ...



I changed salt and digest. No Keyslots are present!!!

I tried this 2 times in a row with new install,
exactly same result.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.0.8-xanmod5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-disk-utility depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcanberra-gtk3-0   0.30-7
ii  libdvdread4  6.0.1-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  liblzma5 5.2.4-1
ii  libnotify4   0.7.7-4
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpwquality11.4.0-3
ii  libsecret-1-00.18.7-1
ii  libsystemd0  241-3
ii  libudisks2-0 2.8.1-4
ii  udisks2  2.8.1-4

gnome-disk-utility recommends no packages.

gnome-disk-utility suggests no packages.

-- no debconf information

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

** Affects: gnome-disk-utility (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: rls-dd-incoming

** Bug watch added: Debian Bug tracker #928893
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893

** Also affects: gnome-disk-utility (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893
   Importance: Unknown
   Status: Unknown

** Tags added: rls-dd-incoming

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

Title:
  disk content permanently lost when changing LUKS password

Status in gnome-disk-utility package in Ubuntu:
  New
Status in gnome-disk-utility package in Debian:
  Unknown

Bug description:
  This is fixed upstream.  Logging this bug to track the fix in to
  Ubuntu.

  
  From the upstream bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893

  Dear Maintainer,

 * What led up to the situation?

  Install system using normal full disk encryption LUKS+Ext4.
  After install open gnome-disk-utility and change
  encryption password. It gives some error dialog and
  now you are royally screwed. It deleted the only
  LUKS keyslot. Cannot add new keyslots because of that.
  All data will be lost after reboot.

  Here is output of luksdump:

  udo cryptsetup luksDump /dev/sda5
  LUKS header information
  Version:2
  Epoch:  4
  Metadata area:  16384 [bytes]
  Keyslots area:  1678 [bytes]
  UUID:   3c16ad4c-294c-4547-bf3e-bb8864ba5ea3
  Label:  (no label)
  Subsystem:  (no subsystem)
  Flags:  (no flags)

  Data segments:
0: crypt
  offset: 16777216 [bytes]
  length: (whole device)
  cipher: aes-xts-plain64
  sector: 512 [bytes]

  Keyslots:
  Tokens:
  Digests:
0: pbkdf2
  Hash:   sha256
  Iterat

[Desktop-packages] [Bug 1837428] [NEW] /usr/bin/nautilus-desktop:11:gdk_x11_device_manager_xi2_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event:_gdk_x11_display_que

2019-07-22 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: artful bionic cosmic disco kylin-18.04

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

Title:
  /usr/bin/nautilus-
  
desktop:11:gdk_x11_device_manager_xi2_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event:_gdk_x11_display_queue_events:gdk_display_get_event

Status in nautilus package in Ubuntu:
  New

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

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

-- 
Mailing list: https://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 1672459] Re: incorrectly asks for password on .pdf file

2019-07-22 Thread Jon Elson

On 07/22/2019 07:10 AM, Paul White wrote:
> I cannot reproduce the problem using either evince 3.28 in Xubuntu
> 18.04, or evince 3.32 in Ubuntu 19.10 (dev). I've also viewed the same
> file downloaded from other sources. There have been several reports of
> this problem in the past but they seem to have been fixed before this
> bug report was raised.
>
OK, that is fine.  Eventually, this system will get creaky 
enough that I will have to update.
Just a case of inertia!

Thanks for looking into it, and glad that newer versions do 
not have the problem.

Jon

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

Title:
  incorrectly asks for password on .pdf file

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 12.04.3 LTS, evince 3.4.0, just updated it with apt-get and still 
shows the problem.
  Here's a file that asks for password :
  https://www.fairchildsemi.com/datasheets/FO/FODM121.pdf

  But, it seems a bunch of Fairchild semi files have the same problem.
  Reads fine with acroread, asks for a password in evince.

  apt-cache shows :
  evince:
Installed: 3.4.0-0ubuntu1.8
Candidate: 3.4.0-0ubuntu1.8
Version table:
   *** 3.4.0-0ubuntu1.8 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.4.0-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  Thanks,

  Jon

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

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

[Desktop-packages] [Bug 1837422] [NEW] podcast with filename greater than 255 cannot be downloaded

2019-07-22 Thread marc belmont

Public bug reported:

Subscribe to "hidden brain". 
Try to download podcast from first week of July.

File will not download and will be marked as failed.

Look at properties. Filename is greater than 255. 
Such long filenames are not supported on Linux.

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

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

Title:
  podcast with filename greater than 255 cannot be downloaded

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Subscribe to "hidden brain". 
  Try to download podcast from first week of July.

  File will not download and will be marked as failed.

  Look at properties. Filename is greater than 255. 
  Such long filenames are not supported on Linux.

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

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

[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

2019-07-22 Thread kenji yuki

** Changed in: duplicity
   Status: In Progress => Confirmed

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

Title:
  Backing up fails with 'IOError CRC check failed'.

Status in Duplicity:
  Confirmed
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  For 4 days déjà dup hasn't been able to perform a backup. It fails
  with the error

  Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
  0x3d503338L',), )

  There is another similar bug #676767 where deleting ~/.cache/deja-dup
  helps. In this case it doesn't.

  I'm quite certain that my backup drive isn't corrupted. (It's a
  raid5.) I'd be happy to provide any additional information needed.

  --

  System information:
  Ubuntu 11.10
  deja-dup 20.0-0ubuntu3
  duplicity 0.6.15-0ubuntu2

  Logs:
  deja-dup.log: http://pastie.org/2705320
  deja-dup.gsettings: http://pastie.org/2705322

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

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

[Desktop-packages] [Bug 1827169] Re: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Changed in: desktop-file-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

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

Bug description:
  Attempting to install lyx from command-line with sudo apt install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: desktop-file-utils 0.22-1ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  Uname: Linux 4.4.0-146-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed May  1 13:14:35 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2019-03-19 (43 days ago)
  InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190226)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1827169/+subscriptions

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

[Desktop-packages] [Bug 1837399] [NEW] file selection does not work properly in 'search-results' mode

2019-07-22 Thread Friedrich Feichtinger

Public bug reported:

When nautilus is in 'search-results' mode, the first found file is
displayed as selected (the file symbol and text have an orange
background color) but apparently in fact it is not. (Copying the file
does not work, or a file that was selected previously is copied
instead.)


How to reproduce:
* open two tabs at different paths
* use CTRL+F to enter 'find' mode
* type some letters until a file is found
* use CTRL+C to copy the first found file
* switch to the second tab
* use CTRL+V to paste the file

What I expected to happen:
* the file should be copied to the second tab

What happened instead:
* the file was not copied or a different file is copied instead


Also when using CTRL+left click to select addition files, these are also
displayed as selected, but nothing is copied.

When using SHIFT instead, the behaviour is a little bit different, as
you have to click two times for the files to be selected, but then all
files are copied correctly.


Workaround:
* unselect the first found file after searching by clicking into the white
* select the file(s) again
* copy works as expected


Nautilus version: 3.26.4
Ubuntu version: 18.04.2 LTS

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: 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/1837399

Title:
  file selection does not work properly in 'search-results' mode

Status in nautilus package in Ubuntu:
  New

Bug description:
  When nautilus is in 'search-results' mode, the first found file is
  displayed as selected (the file symbol and text have an orange
  background color) but apparently in fact it is not. (Copying the file
  does not work, or a file that was selected previously is copied
  instead.)

  
  How to reproduce:
  * open two tabs at different paths
  * use CTRL+F to enter 'find' mode
  * type some letters until a file is found
  * use CTRL+C to copy the first found file
  * switch to the second tab
  * use CTRL+V to paste the file

  What I expected to happen:
  * the file should be copied to the second tab

  What happened instead:
  * the file was not copied or a different file is copied instead


  Also when using CTRL+left click to select addition files, these are
  also displayed as selected, but nothing is copied.

  When using SHIFT instead, the behaviour is a little bit different, as
  you have to click two times for the files to be selected, but then all
  files are copied correctly.

  
  Workaround:
  * unselect the first found file after searching by clicking into the white
  * select the file(s) again
  * copy works as expected


  Nautilus version: 3.26.4
  Ubuntu version: 18.04.2 LTS

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

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

[Desktop-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz

2019-07-22 Thread Muhammed Ali Geldi

I can also confirm that this bug is still present. I'm on Ubuntu 19.04
with the latest drivers & updates installed.

Also, I want to add something here: It's not that it specifically
limits the framerate to 60 Hz. Rather, it limits it to the monitor with
the lowest refresh rate. Try setting one monitor's refresh rate to 30
Hz, and you should instantly notice how laggy the whole desktop
environment becomes.

I understand that this issue might be looked at as "not that important",
but I believe a lot of people that would love to switch from Windows to
something like Ubuntu really wouldn't appreciate the fact that their 144
Hz monitor doesn't work as intended. If you own one yourself, you
probably would never want to set it to 60 Hz out of free will.

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

Title:
[xorg] multiple monitors: limits the framerate of faster 120/144hz
monitors to 60hz

Status in nvidia-graphics-drivers-418 package in Ubuntu:
Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
Confirmed

Bug description:
multiple monitors on xorg
=

Was recently discussed over on
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892

Another user + myself have the following issue:

The slowest connected display limits the FPS. The test case we used is
over at the top of the other bug report ^^

This we found today happens with either amd vega graphics, or nvidia
pascal graphics, the vendor doesn't seem to matter. We have both seen
the same issue (xorg).

This is on 18.10, and booting into the 'Gnome (xorg)' login option.
With the FPS being logged by journalctl -f. With only single monitor
attached. Then it initially goes as high as the primary monitor can
show. (And glmark2 running in background, to maintain a continued
load). Which is 120fps for my case. Then as soon as secondary monitor
is plugged in, which is a 60hz TV. This is being plugged into the HDMI
port of the same graphics card in real time. Then the FPS logged by
'journalctl -f' drops, and becomes capped to 60hz, in the output being
printed by journalctl -f.

My setup:
kernel 5.0.0-05-lowlatency #201903032031
NVIDIA Driver for UNIX platforms 415.27 (the closed source one)
ubuntu 18.10

mutter version:

mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all
[installed]

To confirm where the '.4' at the very end of the ~ubuntu18.10.4
version number, it seems to be that we have updated now on our client
machines the be most recent bugfix updates, kindly provided by Daniel.
Which closed the other bug
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
referred to, as being solved for people's single monitor scenarios.

Thanks again for the other recent bug fixes in this area, it is a nice
progress. Very helpful! We hope you can also look into this latest
problem / issue for the multiple monitor scenario.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions

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

[Desktop-packages] [Bug 1074351] Re: Vertical scrollbar has no minimal height

Thanks for your feedback, closing.

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

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

Title:
  Vertical scrollbar has no minimal height

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Since the upgrade to Xubuntu 12.10 (packet evince 3.6.0-0ubuntu2), the
  vertical scrollbar has a height that is strictly proportional to the
  visible fraction of the document. This means that becomes vanishingly
  small when the document is very long. I did not have this behavior
  with Xubuntu 12.04.

  $ uname -a
  Linux asuslinux 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:27:31 UTC 2012 
i686 i686 i686 GNU/Linux

  Window managers: tried with Compiz and with Metacity.

  See attached picture

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

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

[Desktop-packages] [Bug 1074351] Re: Vertical scrollbar has no minimal height

2019-07-22 Thread Miguel

No, I don't have this problem anymore. It was a long time ago!

I now have evince 3.28.4, with Xfce 4.12.2 (gtk2), on Xubuntu 18.04 LTS
32 bit.

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

uname -a
Linux  4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar 15 15:26:32 UTC 
2019 i686 i686 i686 GNU/Linux

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

Title:
  Vertical scrollbar has no minimal height

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Xubuntu 12.10 (packet evince 3.6.0-0ubuntu2), the
  vertical scrollbar has a height that is strictly proportional to the
  visible fraction of the document. This means that becomes vanishingly
  small when the document is very long. I did not have this behavior
  with Xubuntu 12.04.

  $ uname -a
  Linux asuslinux 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:27:31 UTC 2012 
i686 i686 i686 GNU/Linux

  Window managers: tried with Compiz and with Metacity.

  See attached picture

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

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

[Desktop-packages] [Bug 1836756] Re: Xorg freeze

2019-07-22 Thread Balaji Duraisamy

Any improvements ?
Can you solve the problem(Ubuntu froze)

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  New

Bug description:
  i have to hard reboot the system for ubuntu froze,so please fix the
  bug .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 16 19:42:53 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
  InstallationDate: Installed on 2019-04-01 (105 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2213
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 096C11405F00050660180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1460153] Re: Evince fails to snap left/right in Gnome Shell with >9 pages

Issue now being tracked at:
https://gitlab.gnome.org/GNOME/evince/issues/515


** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #515
   https://gitlab.gnome.org/GNOME/evince/issues/515

** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #515
   https://gitlab.gnome.org/GNOME/evince/issues/515

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

** Changed in: evince
   Status: Expired => Unknown

** Changed in: evince
 Remote watch: GNOME Bug Tracker #737239 => 
gitlab.gnome.org/GNOME/evince/issues #515

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

Title:
  Evince fails to snap left/right in Gnome Shell with >9 pages

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Triaged

Bug description:
  Evince fails to snap to left or right edges in Gnome Shell if the pdf opened 
has 10 or more pages.
  To reproduce:

  1) Open a pdf in evince
  2) Try to snap to left and right screen edges by dragging or using Super+L / 
Super+R
  3) Observe that this doesn't work correctly

  A sample pdf has been attached for testing purposes

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri May 29 17:50:05 2015
  InstallationDate: Installed on 2015-05-10 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  KernLog:
   [12516.809554] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
   [12516.822305] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
   [22153.473615] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
   [22153.487176] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1252099] Re: mouse wheel does not scroll

No comments here for over 5 years
Tested ok with evince 3.32.0 in Ubuntu 19.10 (dev)
Further to comment #7 by reporter closing as fixed.

** Changed in: evince (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  mouse wheel does not scroll

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Since updating to Ubuntu 13.10 (saucy), my mouse wheel does not scroll
  PDFs in evince (3.10.0-0ubuntu2) anymore. The wheel works perfectly in
  other programs, such as Adobe Reader (acroread), Firefox or gnome-
  terminal.

  A few additional details I noticed:

   - The builtin touchpad in my Dell Latitude E6400 *does* work for
  scrolling in evince (when using the scrolling area at the right margin
  of the pad).

   - The USB mouse's wheel creates the following events when recorded
  with xev (same as the touchpad's):

  ButtonPress event, serial 37, synthetic NO, window 0x5a1,
  root 0x255, subw 0x0, time 1888376, (122,66), root:(753,436),
  state 0x0, button 5, same_screen YES

  ButtonRelease event, serial 37, synthetic NO, window 0x5a1,
  root 0x255, subw 0x0, time 1888376, (122,66), root:(753,436),
  state 0x1000, button 5, same_screen YES

  ButtonPress event, serial 37, synthetic NO, window 0x5a1,
  root 0x255, subw 0x0, time 1889640, (122,66), root:(753,436),
  state 0x0, button 4, same_screen YES

  ButtonRelease event, serial 37, synthetic NO, window 0x5a1,
  root 0x255, subw 0x0, time 1889640, (122,66), root:(753,436),
  state 0x800, button 4, same_screen YES

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evince 3.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 23:32:05 2013
  InstallationDate: Installed on 2012-07-06 (499 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

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

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

[Desktop-packages] [Bug 1158223] Re: evince prints crop marks

** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #217
   https://gitlab.gnome.org/GNOME/evince/issues/217

** Changed in: evince
   Importance: Undecided => Unknown

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

** Changed in: evince
 Remote watch: None => gitlab.gnome.org/GNOME/evince/issues #217

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

Title:
  evince prints crop marks

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Triaged

Bug description:
  When printing the attached PDF file crop marks from Adobe Reader on
  Windows, it prints nice A4 pages without crop marks.

  On Ubuntu 12.04 LTS, evince prints the attached PDF file with crop
  marks - and also select A3 paper instead of A4.

  The intent of the author was clearly to print without crop marks by
  default.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: evince 3.4.0-0ubuntu1.6
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Thu Mar 21 11:26:22 2013
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=fr_FR:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1087206] Re: Evince often hangs on close

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

Does anyone still see a problem related to the one that was reported
when using a currently supported version of Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Tags added: precise trusty utopic

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

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

Title:
  Evince often hangs on close

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  When closing an  Evince 3.4.0-0ubuntu1.4 window, it often happens that
  the window remains open but stops responding to events. This is not
  document-dependent, as this behaviour is seen for different documents,
  for at least both PDF and EPS documents, and the same document
  sometimes shows this behaviour, and sometimes doesn't.

  When attaching using strace, it is hanging on
  futex(0x7f57e20bb5c4, FUTEX_WAIT_PRIVATE, 1, NULL

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

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

[Desktop-packages] [Bug 514930] Re: URLs not clickable

** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #268
   https://gitlab.gnome.org/GNOME/evince/issues/268

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

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

Title:
  URLs not clickable

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Triaged

Bug description:
  Upstream URL:
  https://gitlab.gnome.org/GNOME/evince/issues/268

  Binary package hint: evince

  The URL contained in the pdf are not clickable

  Ubuntu Lucid 10.04 (Netbook Edition)

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

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

[Desktop-packages] [Bug 531516] Re: Evince produces multiple icons on clickable buttons

** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #539
   https://gitlab.gnome.org/GNOME/evince/issues/539

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

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

Title:
  Evince produces multiple icons on clickable buttons

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Triaged

Bug description:
  Upstream URL:
  https://gitlab.gnome.org/GNOME/evince/issues/539

  Binary package hint: evince

  1) lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  2) apt-cache policy evince
  evince:
    Installed: 3.14.1-0ubuntu1
    Candidate: 3.14.1-0ubuntu1
    Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one opens
  
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/531516/+attachment/1207516/+files/test.pdf
  one may click one of the four buttons, and then clicks another, the
  first one disappears, and reappears in the secondly clicked button,
  just like Adobe Reader.

  What happens instead is clicking the second radio button does input a
  mark in the second button, but the first button clicked still has its
  mark. This was originally reported to be a regression.

  WORKAROUND: Use Google Chrome's built-in PDF viewer.

  apt-cache policy google-chrome-stable:i386
  google-chrome-stable:i386:
    Installed: 39.0.2171.95-1
    Candidate: 39.0.2171.95-1
    Version table:
   *** 39.0.2171.95-1 0
  500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Mar  3 10:23:44 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Package: evince 2.28.1-0ubuntu1.2
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: evince
  Uname: Linux 2.6.31-19-generic x86_64

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

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

[Desktop-packages] [Bug 1837392] [NEW] "unable to find firefox.desktop" when clicking "Show Details" on the Firefox menu (top)

2019-07-22 Thread EoflaOE

Public bug reported:

When a user tries to open the menu that is on the top, next to
Activities button, and clicks "Show Details", it opens GNOME Software,
but stays on the loading bar for a while then it says "Unable to find
firefox.desktop".

However, if I opened GNOME Software to search for Firefox, there are two
entries for Firefox, one from Ubuntu repo, one from Snap. I know that
Firefox existed on GNOME Software, but it seems weird that it won't be
able to search for "firefox.desktop."

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu8
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 22 14:59:54 2019
InstallationDate: Installed on 2019-07-21 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.30.6-2ubuntu8
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 eoan firefox gnome-software

** Attachment added: "Picture showing the problem"
   
https://bugs.launchpad.net/bugs/1837392/+attachment/5278436/+files/Screenshot%20from%202019-07-22%2015-24-45.png

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

Title:
  "unable to find firefox.desktop" when clicking "Show Details" on the
  Firefox menu (top)

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When a user tries to open the menu that is on the top, next to
  Activities button, and clicks "Show Details", it opens GNOME Software,
  but stays on the loading bar for a while then it says "Unable to find
  firefox.desktop".

  However, if I opened GNOME Software to search for Firefox, there are
  two entries for Firefox, one from Ubuntu repo, one from Snap. I know
  that Firefox existed on GNOME Software, but it seems weird that it
  won't be able to search for "firefox.desktop."

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 22 14:59:54 2019
  InstallationDate: Installed on 2019-07-21 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1548566] Re: gnome document previewer does not allow printer selection

Thanks Humphrey.

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

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

Title:
  gnome document previewer does not allow printer selection

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  gnome document previewer prints to the default printer.

  it should allow the selection of a different printer

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.16.0-62.82~14.04.1-generic 3.16.7-ckt23
  Uname: Linux 3.16.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 23 11:21:27 2016
  ExecutablePath: /usr/bin/evince-previewer
  InstallationDate: Installed on 2015-09-08 (167 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  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/1548566/+subscriptions

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

[Desktop-packages] [Bug 1672459] Re: incorrectly asks for password on .pdf file

Thanks for the reply.

Obviously evince 3.4.0 is never going to be updated now and any fixes
would be applied to later releases of evince.

I cannot reproduce the problem using either evince 3.28 in Xubuntu
18.04, or evince 3.32 in Ubuntu 19.10 (dev). I've also viewed the same
file downloaded from other sources. There have been several reports of
this problem in the past but they seem to have been fixed before this
bug report was raised.

The problem that you are experiencing may not be an evince bug but a bug
in one of the dependencies.

I'm closing this report for now by marking it "Fix Released" as the
issue seems to have been fixed in later releases of evince. If when you
upgrade to a supported Ubuntu release and you find that you still
experience the bug as the originator of the report you can re-open it by
changing the status back to "New".

Preferably you should use the command 'ubuntu-bug evince' in a terminal
so that the appropriate logs are attached to a new report.


** Tags added: precise

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

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

Title:
  incorrectly asks for password on .pdf file

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 12.04.3 LTS, evince 3.4.0, just updated it with apt-get and still 
shows the problem.
  Here's a file that asks for password :
  https://www.fairchildsemi.com/datasheets/FO/FODM121.pdf

  But, it seems a bunch of Fairchild semi files have the same problem.
  Reads fine with acroread, asks for a password in evince.

  apt-cache shows :
  evince:
Installed: 3.4.0-0ubuntu1.8
Candidate: 3.4.0-0ubuntu1.8
Version table:
   *** 3.4.0-0ubuntu1.8 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.4.0-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  Thanks,

  Jon

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

-- 
Mailing list: https://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 1548566] Re: gnome document previewer does not allow printer selection

2019-07-22 Thread Humphrey van Polanen Petel

works fine now

On 21/7/19 10:19 pm, Paul White wrote:
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
>
> Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
>
> Do you still see a problem related to the one that you reported when
> using a currently supported version of Ubuntu? Please let us know if you
> do otherwise this report can be left to expire in approximately 60 days
> time.
>
> Thank you for helping make Ubuntu better.
>
> Paul White
> [Ubuntu Bug Squad]
>
>
> ** Changed in: evince (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  gnome document previewer does not allow printer selection

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  gnome document previewer prints to the default printer.

  it should allow the selection of a different printer

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.16.0-62.82~14.04.1-generic 3.16.7-ckt23
  Uname: Linux 3.16.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 23 11:21:27 2016
  ExecutablePath: /usr/bin/evince-previewer
  InstallationDate: Installed on 2015-09-08 (167 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  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/1548566/+subscriptions

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

[Desktop-packages] [Bug 1438011] Re: document viewer

All understood Wilbur.
Sorry to hear of your circumstances.
Reverting status to new.


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

** Tags added: trusty

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

Title:
  document viewer

Status in evince package in Ubuntu:
  New

Bug description:
  Evince has some usability issues with "locked" files:

  1.  When a "locked" PDF is saved, it cannot be saved to iself, as
  LibreOffice does for ordinary files.  This is an issue with IRS and
  State of Texas filing documents.  They can be edited after having been
  saved, but must be manually saved to a different file and the original
  file manually deleted -- a great opportunity for screwups.  I suppose
  that's "reasonable", but being a mere mortal, I find that I often must
  edit these things, sometimes several times, before finally printing
  them for submission.  Keeping up with the saved versions is a real
  hassle.

  2.  Besides being a hassle, it's a big time-waster saving an edited
  locked government form.  A semi-automagical renaming mechanism would
  be a great help.

  3.  Edited PDF's are saved with the same timestamp as the source file.
  This makes it more difficult to distinguish between saved versions.
  It's also misleading, with potential legal repercussions for the user.
  There's no way to distinguish as to when the file was actually created
  in its new persona.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

This bug was fixed in the package linux - 4.15.0-55.60

---
linux (4.15.0-55.60) bionic; urgency=medium

  * linux: 4.15.0-55.60 -proposed tracker (LP: #1834954)

  * Request backport of ceph commits into bionic (LP: #1834235)
- ceph: use atomic_t for ceph_inode_info::i_shared_gen
- ceph: define argument structure for handle_cap_grant
- ceph: flush pending works before shutdown super
- ceph: send cap releases more aggressively
- ceph: single workqueue for inode related works
- ceph: avoid dereferencing invalid pointer during cached readdir
- ceph: quota: add initial infrastructure to support cephfs quotas
- ceph: quota: support for ceph.quota.max_files
- ceph: quota: don't allow cross-quota renames
- ceph: fix root quota realm check
- ceph: quota: support for ceph.quota.max_bytes
- ceph: quota: update MDS when max_bytes is approaching
- ceph: quota: add counter for snaprealms with quota
- ceph: avoid iput_final() while holding mutex or in dispatch thread

  * QCA9377 isn't being recognized sometimes (LP: #1757218)
- SAUCE: USB: Disable USB2 LPM at shutdown

  * hns: fix ICMP6 neighbor solicitation messages discard problem (LP: #1833140)
- net: hns: fix ICMP6 neighbor solicitation messages discard problem
- net: hns: fix unsigned comparison to less than zero

  * Fix occasional boot time crash in hns driver (LP: #1833138)
- net: hns: Fix probabilistic memory overwrite when HNS driver initialized

  *  use-after-free in hns_nic_net_xmit_hw (LP: #1833136)
- net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw()

  * hns: attempt to restart autoneg when disabled should report error
(LP: #1833147)
- net: hns: Restart autoneg need return failed when autoneg off

  * systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
(LP: #1821625)
- powerpc: sys_pkey_alloc() and sys_pkey_free() system calls
- powerpc: sys_pkey_mprotect() system call

  * [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different
(LP: #1832625)
- pkey: Indicate old mkvp only if old and current mkvp are different

  * [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
(LP: #1832623)
- s390/crypto: fix gcm-aes-s390 selftest failures

  * System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
(LP: #1833716)
- powerpc/numa: improve control of topology updates
- powerpc/numa: document topology_updates_enabled, disable by default

  * Kernel modules generated incorrectly when system is localized to a non-
English language (LP: #1828084)
- scripts: override locale from environment when running recordmcount.pl

  * [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs
(LP: #1832624)
- s390/zcrypt: Fix wrong dispatching for control domain CPRBs

  * CVE-2019-11815
- net: rds: force to destroy connection if t_sock is NULL in
  rds_tcp_kill_sock().

  * Sound device not detected after resume from hibernate (LP: #1826868)
- drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled
- drm/i915: Save the old CDCLK atomic state
- drm/i915: Remove redundant store of logical CDCLK state
- drm/i915: Skip modeset for cdclk changes if possible

  * Handle overflow in proc_get_long of sysctl (LP: #1833935)
- sysctl: handle overflow in proc_get_long

  * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe
drains lots of power under s2idle (LP: #1808957)
- Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering 
D3
  and being disabled"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUNTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3"
- Revert "SAUCE: nvme: add quirk to not call disable function when 
suspending"
- Revert "SAUCE: pci: prevent sk hynix nvme from entering D3"
- PCI: PM: Avoid possible suspend-to-idle issue
- PCI: PM: Skip devices in D0 for suspend-to-idle
- nvme-pci: Sync queues on reset
- nvme: Export get and set features
- nvme-pci: Use host managed power state for suspend

  * linux v4.15 ftbfs on a newer host kernel (e.g. hwe) (LP: #1823429)
- selinux: use kernel linux/socket.h for genheaders and mdp

  * 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all (LP: #1830433)
- x86/mm/pat: Disable preemption around __flush_tlb_all()
- x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init()
- x86/mm: Disable ioremap free page handling on x86-PAE
- ioremap: Update pgtable free interfaces with addr
- x86/mm: Add TLB purge to free pmd/pte page interfaces
- x86/init: fix build with CONFIG_SWAP=n
- x86/mm: provide pmdp_establish() helper
- x86/mm: Use WRITE_ONCE() when setting PTEs

  * hinic: fix oops due to race in set_rx_mode (LP: #1832048)
- hinic: fix a bug in set

[Desktop-packages] [Bug 1799920] Re: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade

2019-07-22 Thread Cedric M

Hi,

I have switched from Gnome to i3, this fixed the issue for me.

The underlying issue might have been fixed by
https://cgit.freedesktop.org/drm-
tip/commit/?id=3cf71bc9904d7ee4a25a822c5dcb54c7804ea388, but I didn't
check.

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

Title:
  External Dell P2715Q doesn't wake up from standby anymore after 18.04
  -> 18.10 upgrade

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  Since upgrading to 18.10, my Dell P2715Q external screen (connected to
  a Dell XPS 13 9343 laptop) fails to wakeup after a period of
  inactivity:

  - leave the laptop idle for a while, gnome screen lock will take over
  and shut down the internal panel & external screen (it enters power
  saving mode). Same behaviour as 18.04.

  - however, if I come back after an hour or so and move the mouse or
  press a key, only the internal panel wakes up. The external screen
  remains blank (Xorg probably think that the external screen is on as
  the password prompt of gnome screen lock will not be visible on the
  internal panel, it's probably displayed on the blank surface -- I have
  to enter my password blind to get back to the desktop).

  
  Running xrandr without any argument sometimes helps getting the external 
screen to turn on.
  When it does not, I have to turn the screen OFF and ON again.

  I haven't seen any error message in dmesg or Xorg.0.log.

  
  $ uname -a
  Linux Aurora 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ lspci -vv
  00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
Subsystem: Dell Broadwell-U Host Bridge -OPI
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 
09) (prog-if 00 [VGA controller])
Subsystem: Dell HD Graphics 5500
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
Subsystem: Dell Broadwell-U Audio Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor 
Thermal Subsystem (rev 09)
Subsystem: Dell Broadwell-U Processor Thermal Subsystem
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03) (prog-if 30 [XHCI])
Subsystem: Dell Wildcat Point-LP USB xHCI Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd

  00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
Subsystem: Dell Wildcat Point-LP MEI Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: mei_me

  00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
Subsystem: Dell Wildcat Point-LP High Definition Audio Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#1 (rev e3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pc

Re: [Desktop-packages] [Bug 1799103] Re: [radeon] Screen corrupted (skewed stride) after boot

2019-07-22 Thread fiamma

hi Daniel,

Thank you for the update. Been considering upgrading to the latest ubuntu
version, will likely do it soon.

Thanks again and good work.


On Mon, Jul 22, 2019 at 6:21 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Thank you for reporting this bug to Ubuntu.
> Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
>
> See this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> We appreciate that this bug may be old and you might not be interested
> in discussing it any more. But if you are then please upgrade to the
> latest Ubuntu version and re-test. If you then find the bug is still
> present in the newer Ubuntu version, please add a comment here telling
> us which new version it is in and change the bug status to Confirmed.
>
> ** Changed in: mutter (Ubuntu)
>Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799103
>
> Title:
>   [radeon] Screen corrupted (skewed stride) after boot
>
> Status in mutter package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   after reboot during upgrade 18.04 to 18.10, screen doesn't show login,
> see pic.
>   However, if I mouseover the line, colors/lines change, and if I click
> middle of screen I see the cursor changing from 'arrow' to 'vertical line
> where you can type'. I then type the login password and voilà! I get the
> cosmic cuttlefish desktop and everything works fine :-D
>
>   I have 2 more pics for the blind/hidden login sequence
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: xorg 1:7.7+19ubuntu8
>   ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
>   Uname: Linux 4.18.0-10-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.10-0ubuntu13
>   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: Mon Oct 22 01:57:20 2018
>   DistUpgraded: 2018-10-20 12:00:41,261 DEBUG icon theme changed,
> re-reading
>   DistroCodename: cosmic
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e]
> (prog-if 00 [VGA controller])
>  Subsystem: ASUSTeK Computer Inc. RS690 [Radeon X1200] [1043:826d]
>   InstallationDate: Installed on 2018-10-05 (16 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
>   MachineType: System manufacturer System Product Name
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic
> root=UUID=ed7ef936-bff3-46c8-887d-205d5a70d4d4 ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
>   dmi.bios.date: 06/26/2007
>   dmi.bios.vendor: Phoenix Technologies, LTD
>   dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 0901
>   dmi.board.name: M2A-VM
>   dmi.board.vendor: ASUSTeK Computer INC.
>   dmi.board.version: 1.XX
>   dmi.chassis.asset.tag: 123456789000
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Chassis Manufacture
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision0901:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
>   dmi.product.name: System Product Name
>   dmi.product.version: System Version
>   dmi.sys.vendor: System manufacturer
>   version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
>   version.libdrm2: libdrm2 2.4.95-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20171229-1ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
>   xserver.bootTime: Sat Oct 20 22:32:39 2018
>   xserver.configfile: default
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.20.1-3ubuntu2
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1799103/+subscriptions
>


-- 
It's illegal to use a legal name, read and share bccrss.wordpress.com

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

Title:
  [radeon] Screen corrupted (skewed stride) after boot

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  after reboot during upgrade 18.04 to 18.10, screen doesn

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

2019-07-22 Thread Debbie

I have this problem BUT suspect if is system wide and not just firefox. Looking 
up just now as it took over 20 MINUTES to open the attach dialogue box (using 
web.whatsapp). This is a ridiculous amount of time and first time it has been 
this long. 
Any suggestions are welcomed as to how I can look into this

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1836462] Re: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications

2019-07-22 Thread klfyt

https://bugzilla.redhat.com/show_bug.cgi?id=1731759


** Bug watch added: Red Hat Bugzilla #1731759
   https://bugzilla.redhat.com/show_bug.cgi?id=1731759

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

Title:
  Renaming Templates to # Templates fixes speed issues present in wide
  range of desktop applications

Status in xdg-user-dirs package in Ubuntu:
  New
Status in xdg-user-dirs package in Fedora:
  Unknown

Bug description:
  
  Renaming "Templates" to "# Templates" fixes a lot of speed issues
  in a range of desktop applications, e.g.
  file managers, text editors, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462/+subscriptions

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

[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language

Done. You should have permission to make those changes yourself, but I
have noticed many people are not familiar with how to do it, even after
being told to do so...

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

Title:
  Impossible to unlock the screen when using non-English language

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Add another keyboard layout, e.g. Russian. Set key combination to switch 
languages to Capslock
  2. Change keyboard layout to Russian.
  3. Lock the screen with Ctrl-Alt-l
  4. Try to unlock the screen

  No matter what it's impossible now to unlock the screen. Changing keyboard 
layout with key combination or using mouse doesn't help. System always reports 
invalid password.
  It works absolutely fine if keyboard layout before locking the screen was 
English.

  I was able to reproduce it on clean 16.10 install in VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 26 16:43:30 2016
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-09-16 (100 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago)

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

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

[Desktop-packages] [Bug 1814125] Re: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked

** No longer affects: mutter

** Tags removed: fixed-in-3.33.3 fixed-upstream

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

Title:
  [nvidia] gnome-shell eats 100% cpu when seconds display is on and
  screen is locked

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu 
desktop (gnome-shell), no application running
  just activate second display in gnome tweak, let it lock itself
  the fan is going fast, simply moving the mouse and the fan slow down.
  wrote a simple script to append a top every minut in a log file, show that 
gnome-shell consumes 100% when locked.
  workaround : disabling second displaying and no more CPU usage / fan noise 
when locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  415.27  Thu Dec 20 17:25:03 
CST 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 Jan 31 16:19:16 2019
  DistUpgraded: 2018-12-30 21:42:17,971 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 415.27, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2018-06-08 (236 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=174e8747-a737-411b-bfaf-4e6795426fea ro quiet splash nouveau.runpm=0 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-30 (31 days ago)
  dmi.bios.date: 10/13/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0502
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  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/ubuntu/+source/gnome-shell/+bug/1814125/+subscriptions

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

[Desktop-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

This bug was fixed in the package gtk+3.0 - 3.22.30-1ubuntu4

---
gtk+3.0 (3.22.30-1ubuntu4) bionic; urgency=medium

  * debian/patches/print-dialog-check-cups-custom-options.patch:
- Print dialog: Check whether an unknown option setting is actually a
  custom setting, patch from upstream (LP: #1763520, Upstream merge
  request: #434, #717).

 -- Till Kamppeter   Wed,  5 Jun 2019 15:46:01
+0200

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file (in /etc/cups/ppd/) removing the paper size 
you have selected for your job in the PageSize, PageRegion, PaperDimension, and 
ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine:

[Desktop-packages] [Bug 1837359] Re: vte does not support xterm's REP (repeat characters)

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

** Changed in: vte2.91 (Ubuntu)
   Status: New => Confirmed

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

Title:
  vte does not support xterm's REP (repeat characters)

Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  This only affects xenial (libvte2.91-0.42.5):

  Steps to reproduce: (e.g.) use gnome-terminal on xenial to login to
  a remote machine via SSH. The remote is an up-to-date server with ncurses6.
  The bug is seen on a variety of programs using ncurses, due to VTE not being
  100% xterm compatible.

  Here's the bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=787701

  As seen in the bug report above, a patch has been backported up to v.0.46
  Xenial's using 0.42 an is therefore affected.
  Here's the 'original' patch: 
https://gitlab.gnome.org/GNOME/vte/commit/e81ecf7408a943566196d03b605a05a197381068

  And attached is a patch that applies to 0.42

  Notice, that src/vteseq-n.cc needs to be re-generated.

  Build- & run-tested on 16.04.6, this resolves the ncurses/gnome-
  terminal issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1837359/+subscriptions

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

[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language

** Tags removed: cosmic
** Tags added: disco

** Changed in: gdm3 (Ubuntu)
   Status: Won't Fix => Confirmed

** Changed in: gnome-shell (Ubuntu)
   Status: Won't Fix => Confirmed

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

Title:
  Impossible to unlock the screen when using non-English language

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Add another keyboard layout, e.g. Russian. Set key combination to switch 
languages to Capslock
  2. Change keyboard layout to Russian.
  3. Lock the screen with Ctrl-Alt-l
  4. Try to unlock the screen

  No matter what it's impossible now to unlock the screen. Changing keyboard 
layout with key combination or using mouse doesn't help. System always reports 
invalid password.
  It works absolutely fine if keyboard layout before locking the screen was 
English.

  I was able to reproduce it on clean 16.10 install in VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 26 16:43:30 2016
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-09-16 (100 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago)

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

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

[Desktop-packages] [Bug 1837359] Re: vte does not support xterm's REP (repeat characters)

2019-07-22 Thread Ubuntu Foundations Team Bug Bot

The attachment "vte0.42_rep_support.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  vte does not support xterm's REP (repeat characters)

Status in vte2.91 package in Ubuntu:
  New

Bug description:
  This only affects xenial (libvte2.91-0.42.5):

  Steps to reproduce: (e.g.) use gnome-terminal on xenial to login to
  a remote machine via SSH. The remote is an up-to-date server with ncurses6.
  The bug is seen on a variety of programs using ncurses, due to VTE not being
  100% xterm compatible.

  Here's the bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=787701

  As seen in the bug report above, a patch has been backported up to v.0.46
  Xenial's using 0.42 an is therefore affected.
  Here's the 'original' patch: 
https://gitlab.gnome.org/GNOME/vte/commit/e81ecf7408a943566196d03b605a05a197381068

  And attached is a patch that applies to 0.42

  Notice, that src/vteseq-n.cc needs to be re-generated.

  Build- & run-tested on 16.04.6, this resolves the ncurses/gnome-
  terminal issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1837359/+subscriptions

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

[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2019-07-22 Thread Alexander Vlasov

I still can reproduce it on latest version of Ubuntu - 19.04

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

Title:
  Impossible to unlock the screen when using non-English language

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Add another keyboard layout, e.g. Russian. Set key combination to switch 
languages to Capslock
  2. Change keyboard layout to Russian.
  3. Lock the screen with Ctrl-Alt-l
  4. Try to unlock the screen

  No matter what it's impossible now to unlock the screen. Changing keyboard 
layout with key combination or using mouse doesn't help. System always reports 
invalid password.
  It works absolutely fine if keyboard layout before locking the screen was 
English.

  I was able to reproduce it on clean 16.10 install in VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 26 16:43:30 2016
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-09-16 (100 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago)

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

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

[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2019-07-22 Thread Alexander Vlasov

Please reopen the bug and change status to Confirmed

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

Title:
  Impossible to unlock the screen when using non-English language

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Add another keyboard layout, e.g. Russian. Set key combination to switch 
languages to Capslock
  2. Change keyboard layout to Russian.
  3. Lock the screen with Ctrl-Alt-l
  4. Try to unlock the screen

  No matter what it's impossible now to unlock the screen. Changing keyboard 
layout with key combination or using mouse doesn't help. System always reports 
invalid password.
  It works absolutely fine if keyboard layout before locking the screen was 
English.

  I was able to reproduce it on clean 16.10 install in VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 26 16:43:30 2016
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-09-16 (100 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago)

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

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

[Desktop-packages] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc

2019-07-22 Thread Alexander E. Patrakov

Ping - did I follow the instructions correctly?

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

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

Title:
  xorg crashes on virgl with 3d enabled (Haswell on the host),
  ms_dri2_schedule_wait_msc

Status in xorg-server package in Ubuntu:
  New
Status in xorg package in Fedora:
  Unknown

Bug description:
  I have recently files this bug:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and
  decided to test if it affects Ubuntu 19.04.

  Just to remind you, this was about xorg crashing in a virtual machine
  that uses virtio VGA with virgl enabled. The host is Arch Linux, the
  CPU is Intel Core i7 4770S (Haswell).

  Well, xorg crashes on 19.04, too, but with a different backtrace, and
  adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a
  separate bug.

  Disabling virgl on qemu command line helps, but I would rather have it
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Thu Jul 18 21:09:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-20181126_142135-anatol
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1837359] [NEW] vte does not support xterm's REP (repeat characters)

2019-07-22 Thread P. Wassi

Public bug reported:

This only affects xenial (libvte2.91-0.42.5):

Steps to reproduce: (e.g.) use gnome-terminal on xenial to login to
a remote machine via SSH. The remote is an up-to-date server with ncurses6.
The bug is seen on a variety of programs using ncurses, due to VTE not being
100% xterm compatible.

Here's the bug report: https://bugzilla.gnome.org/show_bug.cgi?id=787701

As seen in the bug report above, a patch has been backported up to v.0.46
Xenial's using 0.42 an is therefore affected.
Here's the 'original' patch: 
https://gitlab.gnome.org/GNOME/vte/commit/e81ecf7408a943566196d03b605a05a197381068

And attached is a patch that applies to 0.42

Notice, that src/vteseq-n.cc needs to be re-generated.

Build- & run-tested on 16.04.6, this resolves the ncurses/gnome-terminal
issues

** Affects: vte2.91 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "vte0.42_rep_support.patch"
   
https://bugs.launchpad.net/bugs/1837359/+attachment/5278410/+files/vte0.42_rep_support.patch

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

Title:
  vte does not support xterm's REP (repeat characters)

Status in vte2.91 package in Ubuntu:
  New

Bug description:
  This only affects xenial (libvte2.91-0.42.5):

  Steps to reproduce: (e.g.) use gnome-terminal on xenial to login to
  a remote machine via SSH. The remote is an up-to-date server with ncurses6.
  The bug is seen on a variety of programs using ncurses, due to VTE not being
  100% xterm compatible.

  Here's the bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=787701

  As seen in the bug report above, a patch has been backported up to v.0.46
  Xenial's using 0.42 an is therefore affected.
  Here's the 'original' patch: 
https://gitlab.gnome.org/GNOME/vte/commit/e81ecf7408a943566196d03b605a05a197381068

  And attached is a patch that applies to 0.42

  Notice, that src/vteseq-n.cc needs to be re-generated.

  Build- & run-tested on 16.04.6, this resolves the ncurses/gnome-
  terminal issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1837359/+subscriptions

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

[Desktop-packages] [Bug 1802168] Re: Unable to get right-click working on ThinkPad T480s