date:20181207

** Changed in: gvfs
   Status: Confirmed => Expired

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

Title:
  gvfs-fuse: not able to set smb timestamps

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Triaged
Status in gvfs package in Fedora:
  Fix Released
Status in gvfs package in openSUSE:
  Won't Fix

Bug description:
  Binary package hint: gvfs

  Apparently this bug was supposed to have been fixed as of gvfs 1.1.1.
  As of 1.1.6-0ubuntu2 on Jaunty I still see the issue.

  Steps
  1. Mount a remote smb fileshare
  2. In the terminal cd to the ~/.gvfs/path/to/mount
  3. touch -d "some date" foo

  Result:

  touch: settings times of `foo': Operation not supported

  
  Could this be some sort of configuration problem on the samba side, note 
copying files to the samba server works fine for keeping proper dates. This may 
be an Ubuntu specific issue, somehow(?), since upstream claims this issue was 
corrected in 1.1.1, or else upstream didn't actually fix the problem like they 
thought.

  Chris

  https://bugzilla.redhat.com/show_bug.cgi?id=479199#c28

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

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

[Desktop-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]

2018-12-07 Thread Launchpad Bug Tracker

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

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth device not detected after resume from suspend [Qualcomm
  Atheros QCA9565]

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Expired

Bug description:
  When I suspend my laptop, it often happens that the bluetooth stops
  working. From gnome settings it is shown like if I had no bluetooth
  device at all.

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter 
[1a3b:2130]
Kernel driver in use: ath9k
Kernel modules: ath9k
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
  --
  04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1043:200f]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
  Bus 001 Device 006: ID 13d3:3408 IMC Networks 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  4.15.0-32-generic
  [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
  [   35.407491] Bluetooth: Core ver 2.22
  [   35.407504] Bluetooth: HCI device and connection manager initialized
  [   35.407506] Bluetooth: HCI socket layer initialized
  [   35.407507] Bluetooth: L2CAP socket layer initialized
  [   35.407510] Bluetooth: SCO socket layer initialized
  [   53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   53.501780] Bluetooth: BNEP filters: protocol multicast
  [   53.501783] Bluetooth: BNEP socket layer initialized
  [   87.220137] Bluetooth: RFCOMM TTY layer initialized
  [   87.220143] Bluetooth: RFCOMM socket layer initialized
  [   87.220149] Bluetooth: RFCOMM ver 1.11
  [ 1675.503865] usb 1-5: device firmware changed
  [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err
  [ 1681.095546] Bluetooth: Loading patch file failed
  [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=10248 
label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined"


  Trying to use bluetooth from bluetoothctl
  $ bluetoothctl
  Agent registered
  [bluetooth]# scan on
  No default controller available

  
  Trying to restart the bluetooth service doesn't produce any effect:
  $ sudo service bluetooth restart

  
  Getting bluetooth service status:
  $ sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago
   Docs: man:bluetoothd(8)
   Main PID: 24999 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/bluetooth.service
 └─24999 /usr/lib/bluetooth/bluetoothd

  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service...
  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service.
  elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service...
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48
  elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service.
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management 
interface 1
  lines 1-17/17 (END)

  
  Reloading the driver:
  $ sudo modprobe -r btusb; sudo modprobe btusb;
  $ sudo service bluetooth restart

  
  None of these attempts could solve the issue.


  What happens?
  Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth 
controller is no longer recognised and bluetooth service cannot be used anymore.

  What would you expect?
  Bluetooth controller to be recognised and working also after resume.

[Desktop-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]

2018-12-07 Thread Launchpad Bug Tracker

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

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

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

Title:
  Bluetooth device not detected after resume from suspend [Qualcomm
  Atheros QCA9565]

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Expired

Bug description:
  When I suspend my laptop, it often happens that the bluetooth stops
  working. From gnome settings it is shown like if I had no bluetooth
  device at all.

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter 
[1a3b:2130]
Kernel driver in use: ath9k
Kernel modules: ath9k
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
  --
  04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1043:200f]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
  Bus 001 Device 006: ID 13d3:3408 IMC Networks 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  4.15.0-32-generic
  [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
  [   35.407491] Bluetooth: Core ver 2.22
  [   35.407504] Bluetooth: HCI device and connection manager initialized
  [   35.407506] Bluetooth: HCI socket layer initialized
  [   35.407507] Bluetooth: L2CAP socket layer initialized
  [   35.407510] Bluetooth: SCO socket layer initialized
  [   53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   53.501780] Bluetooth: BNEP filters: protocol multicast
  [   53.501783] Bluetooth: BNEP socket layer initialized
  [   87.220137] Bluetooth: RFCOMM TTY layer initialized
  [   87.220143] Bluetooth: RFCOMM socket layer initialized
  [   87.220149] Bluetooth: RFCOMM ver 1.11
  [ 1675.503865] usb 1-5: device firmware changed
  [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err
  [ 1681.095546] Bluetooth: Loading patch file failed
  [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=10248 
label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined"


  Trying to use bluetooth from bluetoothctl
  $ bluetoothctl
  Agent registered
  [bluetooth]# scan on
  No default controller available

  
  Trying to restart the bluetooth service doesn't produce any effect:
  $ sudo service bluetooth restart

  
  Getting bluetooth service status:
  $ sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago
   Docs: man:bluetoothd(8)
   Main PID: 24999 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/bluetooth.service
 └─24999 /usr/lib/bluetooth/bluetoothd

  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service...
  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service.
  elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service...
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48
  elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service.
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management 
interface 1
  lines 1-17/17 (END)

  
  Reloading the driver:
  $ sudo modprobe -r btusb; sudo modprobe btusb;
  $ sudo service bluetooth restart

  
  None of these attempts could solve the issue.


  What happens?
  Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth 
controller is no longer recognised and bluetooth service cannot be used anymore.

  What would you expect?
  Bluetooth controller to be recognised and working also after resume.

  ProblemType: Bug

[Desktop-packages] [Bug 1795342] Re: High Power Consumption

2018-12-07 Thread Irfan

Thanks and I tested it many times. Kept the system idle with zero apps
running and the power usage was still high.

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

Title:
  High Power Consumption

Status in The Ubuntu Power Consumption Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am running Ubuntu on Thinkpad. I am facing battery back up issues on both 
18.04 and 18.10 versions. Before that I was running Ubuntu 16.04 with a normal 
back of almost 4 hours ( 2 Sony Batteries with normal back up of up to min of 6 
hours on Linux Mint 19) and when upgrading to 18.04 it reduced to 3 hours max 
on normal usage and less than 2 hours on heavy use.
  I tried installing Unity session on 18.04/10, the back up increased. I think 
it is Gnome doing the mess.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1795342/+subscriptions

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

[Desktop-packages] [Bug 1807482] [NEW] package libreoffice-calc (not installed) failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/libreoffice/program/libscfiltlo.so' para '/us

2018-12-07 Thread Richard Queiroz Carvalho

Public bug reported:

Sempre que ligo o computador, aparece um alerta de erro no programa

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libreoffice-calc (not installed)
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Dec  7 16:21:44 2018
ErrorMessage: não pode copiar dados extráidos para 
'./usr/lib/libreoffice/program/libscfiltlo.so' para 
'/usr/lib/libreoffice/program/libscfiltlo.so.dpkg-new': fim de ficheiro ou 
stream inesperado
InstallationDate: Installed on 2018-12-04 (3 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: libreoffice
Title: package libreoffice-calc (not installed) failed to install/upgrade: não 
pode copiar dados extráidos para './usr/lib/libreoffice/program/libscfiltlo.so' 
para '/usr/lib/libreoffice/program/libscfiltlo.so.dpkg-new': fim de ficheiro ou 
stream inesperado
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libreoffice-calc (not installed) failed to install/upgrade:
  não pode copiar dados extráidos para
  './usr/lib/libreoffice/program/libscfiltlo.so' para
  '/usr/lib/libreoffice/program/libscfiltlo.so.dpkg-new': fim de
  ficheiro ou stream inesperado

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Sempre que ligo o computador, aparece um alerta de erro no programa

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Dec  7 16:21:44 2018
  ErrorMessage: não pode copiar dados extráidos para 
'./usr/lib/libreoffice/program/libscfiltlo.so' para 
'/usr/lib/libreoffice/program/libscfiltlo.so.dpkg-new': fim de ficheiro ou 
stream inesperado
  InstallationDate: Installed on 2018-12-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libreoffice
  Title: package libreoffice-calc (not installed) failed to install/upgrade: 
não pode copiar dados extráidos para 
'./usr/lib/libreoffice/program/libscfiltlo.so' para 
'/usr/lib/libreoffice/program/libscfiltlo.so.dpkg-new': fim de ficheiro ou 
stream inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1807480] [NEW] [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, dropouts or crackling sound

2018-12-07 Thread Russell Gundlach

Public bug reported:

Whether I record with aux earbuds(with mics) or the internal mic I hear
crackling with each sound. I tried using this
https://wiki.ubuntu.com/Audio/PositionReporting but with no success.
What should I do?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rgundlach2   2214 F pulseaudio
 /dev/snd/controlC0:  rgundlach2   2214 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  7 20:37:12 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
Symptom_Card: Built-in Audio - HD-Audio Generic
Symptom_Jack: Mic, Internal
Symptom_PulseAudioLog:
 Dec 07 20:31:09 hp-pavillion dbus-daemon[1336]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.36' (uid=121 pid=1788 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
 Dec 07 20:33:56 hp-pavillion pulseaudio[1788]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, 
dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2018
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8353
dmi.board.vendor: HP
dmi.board.version: 37.34
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.26:bd07/25/2018:svnHP:pnHPPavilionLaptop15-cd0xx:pvr:rvnHP:rn8353:rvr37.34:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cd0xx
dmi.sys.vendor: HP
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-12-07T20:19:52.343950

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

Title:
  [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Whether I record with aux earbuds(with mics) or the internal mic I
  hear crackling with each sound. I tried using this
  https://wiki.ubuntu.com/Audio/PositionReporting but with no success.
  What should I do?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rgundlach2   2214 F pulseaudio
   /dev/snd/controlC0:  rgundlach2   2214 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 20:37:12 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioLog:
   Dec 07 20:31:09 hp-pavillion dbus-daemon[1336]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.36' (uid=121 pid=1788 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
   Dec 07 20:33:56 hp-pavillion pulseaudio[1788]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8353
  dmi.board.vendor: HP
  dmi.board.version: 37.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.26:bd07/25/2018:svnHP:pnHPPavilionLaptop15-cd0xx:pvr:rvnHP:rn8353:rvr37.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cd0xx
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf:

[Desktop-packages] [Bug 1129144] Re: Background can not be clicked in Files (Nautilus) 3.6.3, in listview mode

2018-12-07 Thread Casey

This problem was fixed in Nautilus 3.30. Is there any possibly of
backporting the patches to bionic?

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

Title:
  Background can not be clicked in Files (Nautilus) 3.6.3, in listview
  mode

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  In listview mode, Nautilus does not allow clicking on background, when
  browsing a folder with more files than a single page.

  This must be classified as a bug because:
  1. Background click is necessary to unselect a file;
  2. Background click is available in iconview mode, so it is a doubtful 
behavior;
  3. Users are accustomed to access context menu right clicking background in 
order to create folder, share folder, create file, etc;
  4. Files can't be dragged & dropped into current folder.

  Furthermore, it is a kind of regression, since this error has been
  corrected in a earlier version.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Mon Feb 18 11:04:34 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+296+84'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'173'
  InstallationDate: Installed on 2013-02-17 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130208)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767660] Re: Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double click button no longer results in a double click event

2018-12-07 Thread Sean Chu

This affects me too:
RollerMouse Red
Kubuntu 18.10

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

Title:
  Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double
  click button no longer results in a double click event

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libinput package in Ubuntu:
  Incomplete

Bug description:
  ### Expected behaviour
  My "Contour Design RollerMouse Free 2" has a specific button for double 
click. This button should with one physical click result in double click 
(button press, button release, button press and button release).

  This works as expected without issues in Ubuntu 16.04 LTS
  4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64

  ### Experienced behaviour
  Only one mouse click is registered (button press and button release). Tested 
with "xev" and "xinput test"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 16:26:08 2018
  InstallationDate: Installed on 2018-04-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1806385]

2018-12-07 Thread Xiscofauli

Also reproduced in

Version: 4.4.0.0.alpha2+
Build ID: b21df5a993a3815cf736fe3d2eab73eee646b38e

in

Version 4.1.0.0.alpha0+ (Build ID:
efca6f15609322f62a35619619a6d5fe5c9bd5a)

the double click wasn't implemented...

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

Title:
  Creating a new slide by double click not working correctly

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

Bug description:
  Version: 6.1.3.2
  Build-ID: libreoffice-6.1.3.2-snap1

  You can create new slides in impress by double clicking on the empty
  part of the slides pane (below the existing slide). However, this
  works only as expected while the slides pane actually has empty space
  at the bottom.

  As soon as I have created a few slides, the slides pane is completely
  filled, and two things happen:

  (1) Improvement: It is very hard to double click on the thin white
  space at the bottom of the filled slides pane. This could be improved
  by always letting a few pixels at the bottom to click on.

  (2) Bug: You can actually manage to double click there and this
  creates a new slide. However, this new slide is not filed at the end
  of slides (as it should) but appears at a strange location somewhere
  in the middle of slides. This is definitely wrong.

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

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

[Desktop-packages] [Bug 481865] Re: Cannot see Windows shared folders

** Changed in: gvfs
   Status: New => Expired

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

Title:
  Cannot see Windows shared folders

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  Since upgraded to Ubuntu 9.10 (Karmic Koala) I can't see in nautilus
  windows shared folders. I know folders are there and somehow
  reachables, because I can see them in smbclient (see attched image)

  nautilus: 1:2.28.1-0ubuntu2
  smbclient: 2:3.4.0-3ubuntu5

  When nautilus runs via terminal with nautilus --browser I get this
  output AFTER authentication:

  natxoo@portnatxoo:~$ nautilus --browser

  (nautilus:5855): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
  Initializing nautilus-open-terminal extension

  ** (nautilus:5855): WARNING **: No marshaller for signature of signal
  'UploadFinished'

  ** (nautilus:5855): WARNING **: No marshaller for signature of signal
  'DownloadFinished'

  ** (nautilus:5855): WARNING **: No marshaller for signature of signal 
'ShareCreateError'
  Initializing nautilus-gdu extension

  (nautilus:5855): GLib-GObject-CRITICAL **:
  g_type_instance_get_private: assertion `instance != NULL &&
  instance->g_class != NULL' failed

  ** (nautilus:5855): CRITICAL **: dbus_g_proxy_begin_call: assertion
  `DBUS_IS_G_PROXY (proxy)' failed

  (nautilus:5855): Gtk-WARNING **: Refusing to add non-unique action
  'NautilusOpenTerminal::open_terminal' to action group
  'ExtensionsMenuGroup'

  --- Hash table keys for warning below:
  --> natxoo
  --> network:
  --> inode/directory
  --> Natxo Oyanguren
  --> smb-server:server=visvr
  --> l2053
  --> smb-share:server=visvr,share=documentos

  (nautilus:5855): Eel-WARNING **: "unique eel_ref_str" hash table still
  has 7 elements at quit time (keys above)

  (nautilus:5855): Eel-WARNING **: "nautilus-directory.c: directories" hash 
table still has 5 elements at quit time
  Shutting down nautilus-gdu extension
  Shutting down nautilus-open-terminal extension

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

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

[Desktop-packages] [Bug 1806847] Re: FTBFS in disco-proposed

2018-12-07 Thread Olivier Tilloy

libreoffice 1:6.1.3-0ubuntu7 successfully built on all architectures in
disco-proposed.

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

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

Title:
  FTBFS in disco-proposed

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  LibreOffice 1:6.1.3-0ubuntu6 has been failing to build in disco-proposed on 
amd64 and arm64 for about a week.
  The failure is a unit test that segfaults (CppunitTest_sw_odfexport).

  I have reproduced the segmentation fault, I'm attaching a backtrace.

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

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: New => In Progress

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

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

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in cups-filters source package in Bionic:
  Invalid
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in cups-filters source package in Cosmic:
  Invalid
Status in gtk+3.0 source package in Cosmic:
  In Progress

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 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: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups

[Desktop-packages] [Bug 626321]

2018-12-07 Thread 1criticoder

Given the lack of any movement on the relevant feature request of Free
Desktop in the almost *11* years since its filing, perhaps it's time to
re-evaluate whether Wine should be made to replicate the behavior of
Windows using the Free Desktop we have (and seemingly will continue to
have for the indefinite future) rather than the Free Desktop we wish we
had.

To be clear about the situation:
NOTOURBUG is a bit of a misnomer. This *is* a Wine bug, regardless of the 
strategy chosen for getting it fixed. Wine's mission is to replicate the 
behavior of Windows, and this issue represents a failure to do so. It may well 
be made much easier to fix if Free Desktop implemented a notion of temporary 
configuration changes like Windows has, but FD's mission is not to replicate 
Windows behaviors. For them it's merely a feature request. For Wine it remains 
a bug until the behavior matches that of Windows.

Asking FD to implement a feature rather than doing the work of making
Wine mimic it seems to have been a reasonable approach to getting this
bug fixed. But can that really still be said after 11 years of waiting?

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

Title:
  X.org server should keep track of and restore its initial (desktop)
  resolution and refresh rate

Status in Wine:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Applications like games change desktop resolution (graphics mode) for
  their needs. Unfortunately when such applications crash then X.org
  server doesn't revert the resolution back to its initial mode.

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

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

** Description changed:

+ [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 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: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied:

[Desktop-packages] [Bug 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi

2018-12-07 Thread Michael T

Added spaces-fine-in-connection-edit-window.png showing that the edit
connection window will accept spaces in filenames.

** Attachment added: "Edit connection window will accept spaces in filenames"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1807460/+attachment/5220197/+files/spaces-fine-in-connection-edit-window.png

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

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

Bug description:
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

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

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

[Desktop-packages] [Bug 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi

2018-12-07 Thread Michael T

Adding wpa2-tls-root-cert-no-spaces.png which shows settings are
acceptable, the red box disappears and the connect button becomes
available when file is renamed to remove spaces.

** Attachment added: "Shows settings are acceptable when file is renamed to 
remove spaces."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1807460/+attachment/5220196/+files/wpa2-tls-root-cert-no-spaces.png

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

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

Bug description:
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

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

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

[Desktop-packages] [Bug 1807460] [NEW] Filenames with spaces not accepted when connecting to certificate-authenticated wifi

2018-12-07 Thread Michael T

Public bug reported:

This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

When connecting to a certificate-authenticated wifi network (WPA/WPA2
Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
Authentication Required" dialogue is displayed, prompting the user to
select their CA and user certificates.

Unexpected behaviour: If any of the files have spaces in their
filenames, after choosing them in the file picker the field is
highlighted by a red box, and the 'Connect' button is greyed out.

This is depicted in the attachment network-authentication-red-box-
spaces-filename.png

There is also no explanation offered for why the red box highlight is
present - no tooltip, no help from pressing F1, no popup, and as far as
I can find no logs.

If you move/rename the file, so there are no spaces in the filename, the
problem is worked around.

The problem is not present on the edit connection dialogue; filenames
with spaces are acceptable there.

The problem was also not present on Ubuntu 16.04, and users who upgrade
from 16.04 to 18.04 will find their connection keeps working. It is only
when creating an entirely new connection (or after forgetting the
connection and recreating it) that the problem dialog appears.

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

** Attachment added: "network-authentication-red-box-spaces-filename.png"
   
https://bugs.launchpad.net/bugs/1807460/+attachment/5220195/+files/network-authentication-red-box-spaces-filename.png

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

Title:
  Filenames with spaces not accepted when connecting to certificate-
  authenticated wifi

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

Bug description:
  This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS

  When connecting to a certificate-authenticated wifi network (WPA/WPA2
  Enterprise, authentication TLS) for the first time, the "Wi-Fi Network
  Authentication Required" dialogue is displayed, prompting the user to
  select their CA and user certificates.

  Unexpected behaviour: If any of the files have spaces in their
  filenames, after choosing them in the file picker the field is
  highlighted by a red box, and the 'Connect' button is greyed out.

  This is depicted in the attachment network-authentication-red-box-
  spaces-filename.png

  There is also no explanation offered for why the red box highlight is
  present - no tooltip, no help from pressing F1, no popup, and as far
  as I can find no logs.

  If you move/rename the file, so there are no spaces in the filename,
  the problem is worked around.

  The problem is not present on the edit connection dialogue; filenames
  with spaces are acceptable there.

  The problem was also not present on Ubuntu 16.04, and users who
  upgrade from 16.04 to 18.04 will find their connection keeps working.
  It is only when creating an entirely new connection (or after
  forgetting the connection and recreating it) that the problem dialog
  appears.

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

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

[Desktop-packages] [Bug 1481835]

2018-12-07 Thread Dgp-mail

*** Bug 121950 has been marked as a duplicate of this bug. ***

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

Title:
  [UPSTREAM] Unable to group raster image(s) with drawing object(s)

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

Bug description:
  Steps to reproduce:
 1. Create new document in LibreOffice Writer
 2. put rester images into document and put on images some drawing objects 
(arrows, other shapes), text. 
 3. try to group images with drawing objects.

  Expected behaviour:
 User can select and group image(s) with drawing object(s)

  Actual behaviour:
 User can not select and group image(s) with drawing object(s)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice 1:3.5.7-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  Date: Wed Aug  5 18:59:59 2015
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

debdiff for disco.

** Patch added: "gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220192/+files/gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu3.debdiff

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

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

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in cups-filters source package in Bionic:
  Invalid
Status in gtk+3.0 source package in Bionic:
  New
Status in cups-filters source package in Cosmic:
  Invalid
Status in gtk+3.0 source package in Cosmic:
  New

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: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

debdiff for cosmic.

** Patch added: "gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu2.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220193/+files/gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu2.1.debdiff

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

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

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in cups-filters source package in Bionic:
  Invalid
Status in gtk+3.0 source package in Bionic:
  New
Status in cups-filters source package in Cosmic:
  Invalid
Status in gtk+3.0 source package in Cosmic:
  New

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: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

I have now added debdiffs for disco and for the SRUs. Please can someone
with appropriate rights upload them? Thanks.

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

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

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in cups-filters source package in Bionic:
  Invalid
Status in gtk+3.0 source package in Bionic:
  New
Status in cups-filters source package in Cosmic:
  Invalid
Status in gtk+3.0 source package in Cosmic:
  New

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: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

debdiff for bionic.

** Patch added: "gtk+3.0_3.22.30-1ubuntu1_3.22.30-1ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220194/+files/gtk+3.0_3.22.30-1ubuntu1_3.22.30-1ubuntu1.1.debdiff

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

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

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in cups-filters source package in Bionic:
  Invalid
Status in gtk+3.0 source package in Bionic:
  New
Status in cups-filters source package in Cosmic:
  Invalid
Status in gtk+3.0 source package in Cosmic:
  New

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: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

** Changed in: cups
   Status: New => Fix Released

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

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Trusty:
  Invalid
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress
Status in cups package in Debian:
  Fix Released

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

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

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

[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

2018-12-07 Thread will9183

Thanks for the suggestion. It does stop the cursor from getting stuck on
the left side of the screen but it causes the cursor to have more
problems including disappearing in Chrome when there is no movement,
multiple cursors appearing, and other weird artifacts on the screen.
Switching to "uxa"causes the mouse to get stuck on the left side of the
screen again.

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

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

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/gnome-shell/+bug/1767654/+subscriptions

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

[Desktop-packages] [Bug 1807452] [NEW] Unable to copy address from location entry by drop-down menu and mouse on Ubuntu 18.04

2018-12-07 Thread Norbert

Public bug reported:

Steps to reproduce:
1. Open Nautilus
2. Try to make right click on address / location bar to select *Copy* action 
from drop-down menu

Expected behavior:
* option is in place as in 16.04 LTS, user can click on it to send current 
location to the clipboard

Actual behavior:
* option is missed, user can't copy the current location to the clipboard

Note:
first seen on AskUbuntu - https://askubuntu.com/q/1099239/66509

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  7 23:17:38 2018
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x549+268+38'"
InstallationDate: Installed on 2018-04-28 (223 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: apport-bug bionic

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

Title:
  Unable to copy address from location entry by drop-down menu and mouse
  on Ubuntu 18.04

Status in nautilus package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Open Nautilus
  2. Try to make right click on address / location bar to select *Copy* action 
from drop-down menu

  Expected behavior:
  * option is in place as in 16.04 LTS, user can click on it to send current 
location to the clipboard

  Actual behavior:
  * option is missed, user can't copy the current location to the clipboard

  Note:
  first seen on AskUbuntu - https://askubuntu.com/q/1099239/66509

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 23:17:38 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x549+268+38'"
  InstallationDate: Installed on 2018-04-28 (223 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2

2018-12-07 Thread Simon Williams

Got the commands to run without error, but even after a reset, no sound.

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1802680] Re: Adding keyboard layout broken without logout

2018-12-07 Thread Matt Arsenault

I mean to 18.10

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

Title:
  Adding keyboard layout broken without logout

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  On my system, the default keyboard layout is English (Colemak). I have
  English (US) as a secondary keyboard layout.

  I attempted to add Russian, which worked. However, when I switched to
  it using Super+Space, input was really done in Qwerty. Both Russian
  and English (US) were effectively qwerty options until I logged out
  and back in.

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

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

[Desktop-packages] [Bug 1687864] Re: auto-login and "privacy -> auto screen lock -> disable" do not work

2018-12-07 Thread Wolf

When booting my system, it does auto-login without typing in my password. 
That's fine.
When I resume the system from suspend, I always have to type in my password, 
but there is no need for that, I want auto-login after suspend as well.

As I understood @seb128, this is correct behaviour. True?
In that case I'd like to state that this does not make much sense for me, IMHO 
there should be an option to enable "auto-login after suspend" as well.

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

Title:
  auto-login and "privacy -> auto screen lock -> disable" do not work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On my machine, after booting I always have to type in my password,
  allthough I set "settings -> users -> auto login".

  The same happens after resume from suspend, allthough I set "privacy
  -> auto screen lock" to "disabled". In both cases the screen attached
  appears.

  My system:
  ubuntu 16.10
  gnome desktop
  lightdm

  Cheers,
  Wolf

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

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

[Desktop-packages] [Bug 1807435] [NEW] package evince 3.28.4-0ubuntu1 failed to install/upgrade: problèmes de dépendances - laissé non configuré

2018-12-07 Thread tarik virot

Public bug reported:

A pop up windows appeared and redirected me here. I don't know what to
put.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: evince 3.28.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Dec  7 19:41:49 2018
ErrorMessage: problèmes de dépendances - laissé non configuré
InstallationDate: Installed on 2018-10-22 (46 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=ad858553-71b9-4b3c-bfd8-40fcca50042b ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
SourcePackage: evince
Title: package evince 3.28.4-0ubuntu1 failed to install/upgrade: problèmes de 
dépendances - laissé non configuré
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package evince 3.28.4-0ubuntu1 failed to install/upgrade: problèmes de
  dépendances - laissé non configuré

Status in evince package in Ubuntu:
  New

Bug description:
  A pop up windows appeared and redirected me here. I don't know what to
  put.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Dec  7 19:41:49 2018
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2018-10-22 (46 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=ad858553-71b9-4b3c-bfd8-40fcca50042b ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: evince
  Title: package evince 3.28.4-0ubuntu1 failed to install/upgrade: problèmes de 
dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Incomplete => In Progress

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

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

Title:
  different behaviors for switch display mode between xenial and bionic

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  When the "Fn lock" is enabled, we can switch the video mode by one key: 
video-key (Fn+F8).
  But, the key event is too frequent. It's hard to select the wanted video mode.

  Reproduce steps: Press down the Video-out hotkey

  Expected results: User can select Video mode precisely by Video-out hotkey
  Actual results: The speed of switch video mode is too fast makes can not 
select Video mode precisely

  Notebook: XPS 13

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772811/+subscriptions

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

[Desktop-packages] [Bug 1797120] Re: window menu does not include 'always on visible workspace'

2018-12-07 Thread Scott Moser

Well, I think I found out what was happening.

In gnome-tweaks I had somehow gotten 'Workspaces' -> 'Display Handling'
set to 'Workspaces on primary display only'.

So what happened was that there was only a single workspace on the
"second" head and thus no need for "always on visible workspace".

I'm going to close this as 'Invalid'.


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

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

Title:
  window menu does not include 'always on visible workspace'

Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I filed bug 1795410 a few weeks ago complaining that the 'alt space'
  didn't bring up the window menu.  That is now fixed (seemingly likely
  with mutter 3.3.0-6).

  However, the window menu that does come up does not have an entry for
  'Always on visible workspace' as it used to.

  You can still create a custom shortcut in the gnome-control-center to
  toggle this, but that is not as useful or discoverable as in the
  window menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: mutter 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 09:21:40 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1175 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1807433] [NEW] sane backends library at the wrong place?

2018-12-07 Thread donpalavi

Public bug reported:

Hi,

I tried to install the epson wf-2630 network scanner. I have installed
the software from the epson website.

After installing and setting up the sane /etc/sane.d/dll.conf for
epkowa, simple-scan and xsane worked, but not iscan.

Tried many different things, I have finally find out that the libary-
data for epkowa was not in /usr/lib/x86_64-linux-gnu/sane but in
/usr/lib/sane. Note that the only data in /usr/lib/sane is:

libsane-epkowa.la  libsane-epkowa.so.1  libsane-epkowa.so.1.0.15


After copying these files from /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane 
everything worked fine.

I do not know if it is a bug or not.

Best regards

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  sane backends library at the wrong place?

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Hi,

  I tried to install the epson wf-2630 network scanner. I have installed
  the software from the epson website.

  After installing and setting up the sane /etc/sane.d/dll.conf for
  epkowa, simple-scan and xsane worked, but not iscan.

  Tried many different things, I have finally find out that the libary-
  data for epkowa was not in /usr/lib/x86_64-linux-gnu/sane but in
  /usr/lib/sane. Note that the only data in /usr/lib/sane is:

  libsane-epkowa.la  libsane-epkowa.so.1  libsane-epkowa.so.1.0.15

  
  After copying these files from /usr/lib/sane to 
/usr/lib/x86_64-linux-gnu/sane everything worked fine.

  I do not know if it is a bug or not.

  Best regards

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

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

[Desktop-packages] [Bug 1783364] Re: Preference 'recursive-search' is ignored when set to 'never'

2018-12-07 Thread mkurz

Duplicate of #1767027 - is fixed already and can be closed.

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

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

Title:
  Preference 'recursive-search' is ignored when set to 'never'

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  ---
  1. Run
  gsettings set org.gnome.nautilus.preferences recursive-search 'never'

  2. Restart Nautilus

  3. Search within Nautilus

  Current behavior
  ---
  Even after setting recursive-search to 'never' the search is still executed 
recursive.

  Expected behavior
  ---
  After setting recursive-search to 'never' the search should be not recursive 
anymore (only the current folder should be searched).

  Reproducible in:
  ---
  Ubuntu 18.04 with Nautilus 3.26.3-0ubuntu4

  Releated upstream bugs:
  https://gitlab.gnome.org/GNOME/nautilus/issues/547
  https://gitlab.gnome.org/GNOME/nautilus/issues/520

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

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

[Desktop-packages] [Bug 1802680] Re: Adding keyboard layout broken without logout

2018-12-07 Thread Matt Arsenault

This was after updating to 18.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/1802680

Title:
  Adding keyboard layout broken without logout

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  On my system, the default keyboard layout is English (Colemak). I have
  English (US) as a secondary keyboard layout.

  I attempted to add Russian, which worked. However, when I switched to
  it using Super+Space, input was really done in Qwerty. Both Russian
  and English (US) were effectively qwerty options until I logged out
  and back in.

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

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

[Desktop-packages] [Bug 1754092] Re: firefox esr loading bookmark limbo

2018-12-07 Thread Galen Thurber

affects 18.04.1 LTS
Firefox 63.03

I've done a reset Firefox as well, problem still persists.

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

Title:
  firefox esr loading bookmark limbo

Status in firefox package in Ubuntu:
  New

Bug description:
  on three computers I use Firefox ESR
  which all have the odd behaviour of not loading a bookmark.
  I'll select a bookmark ex: youtube.com and the tab icon will rotate but the 
page never loads & never times out. The limbo will happen with various 
bookmarks, cache has been cleared.
  To fix the limbo problem I'll hit enter once in the address bar.
  The limbo happens on 
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  and
  Ubuntu 14.04.5LTS
  and MX Linux 17

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

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

[Desktop-packages] [Bug 1806961] Re: Lock can be circumvented by switching tty when using lightdm

2018-12-07 Thread Eduardo dos Santos Barretto

** Tags added: community-security

** Information type changed from Private Security to Public Security

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

Title:
  Lock can be circumvented by switching tty when using lightdm

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce (only works on X11, not on wayland):
  1) install lightdm
    a) run "sudo apt install lightdm" on a fresh 18.04 install of ubuntu
    b) switch to lightdm with "sudo dpkg-reconfigure gdm3"
    c) reboot to make the login manager switch take effect
  2) log in to your account
  3) click switch user (clicking lock should also work) in the dropdown in the 
top right corner
  4) switch to a different tty (ctrl+alt+f2 for example)
  5) switch back to your original tty (with lightdm usally tty 7)

  You are now logged back in your account without having to type your
  password.

  I have marked lightdm as the vulnerable package because all I had to
  do to reproduce the issue was install lightdm with "sudo apt install
  lightdm" and then switch to lightdm with "sudo dpkg-reconfigure gdm3"

  So I think something should either be changed in lightdm or in dpkg-
  reconfigure.

  I have been told that I should be using light-locker instead of dm-tool, but 
I have no idea what those things are, or how to switch between them, i'm just 
clicking switch user.
  The user does not know, and is never informed of the existence of these tools.

  Since neither apt, nor dpkg-reconfigure warns me that i should use
  lightlocker instead of dm-tool, I think this is still a security
  vulnerability, because a user that wants to use lightdm and installs
  it by quickly searching online for "how to switch login managers" will
  not be informed of this vulnerability.

  Extra info:
  ubuntu 18.04 (fully up to date)
  lightdm version 1.26.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1806080] Re: [snap] Chromium snap crashes when trying to access fs

2018-12-07 Thread Efthimios Chaskaris

It works with version 71.0.3578.80  (538). It is currently available in
the candidate channel.

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

Title:
  [snap] Chromium snap crashes when trying to access fs

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When I attempt to upload or save on certain pages it crashes the browser.  
Some examples below.
  Does not happen on Google Drive.  Looks like it's trying to query the fs and 
dies when it can't.

  
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  Codename: xenial
  Kernel: 4.15.0-39-generic
  Chromium:   Version 70.0.3538.110 (Official Build) snap (64-bit)

  
  # Right click on blank page "save as"
  Nov 30 16:31:00 $HOSTNAME kernel: [35208.515968] audit: type=1400 
audit(1543595460.939:151): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=30734 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  # Restart browser
  Nov 30 16:31:04 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=32093 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
  Nov 30 16:31:04 $HOSTNAME kernel: [35212.081247] audit: type=1107 
audit(1543595464.507:152): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=31991 label="snap.chromium.chromium" 
peer_pid=24826 peer_label="unconfined"
  Nov 30 16:31:05 $HOSTNAME kernel: [35213.238692] audit: type=1400 
audit(1543595465.663:153): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=31991 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Nov 30 16:31:05 $HOSTNAME kernel: [35213.274048] audit: type=1400 
audit(1543595465.699:154): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=31991 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  # Right click on blank page "save as" #2
  Nov 30 16:31:08 $HOSTNAME kernel: [35216.557849] audit: type=1400 
audit(1543595468.983:155): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=31991 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  # Restart browser
  Nov 30 16:31:13 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=32646 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
  Nov 30 16:31:14 $HOSTNAME kernel: [35221.656759] audit: type=1107 
audit(1543595474.083:156): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=32544 label="snap.chromium.chromium" 
peer_pid=24826 peer_label="unconfined"
  Nov 30 16:31:23 $HOSTNAME kernel: [35230.641856] audit: type=1400 
audit(1543595483.067:157): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=32544 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Nov 30 16:31:23 $HOSTNAME kernel: [35230.660955] audit: type=1400 
audit(1543595483.087:158): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=32544 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  
  # Upload to Salesforce case #2
  Nov 30 16:31:46 $HOSTNAME kernel: [35253.816946] audit: type=1400 
audit(1543595506.243:159): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=32544 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  # Restart browser
  Nov 30 16:31:56 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=938 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
  Nov 30 16:31:56 $HOSTNAME kernel: [35264.509009] audit: type=1107 
audit(1543595516.935:160): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager"

[Desktop-packages] [Bug 1648534] Re: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_in

2018-12-07 Thread Marius Gedminas

** Attachment added: "after-update-later.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+attachment/5220141/+files/after-update-later.txt

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

Title:
  gnome-software crashed with SIGTRAP in g_wakeup_new from
  g_main_context_new from g_dbus_connection_send_message_with_reply_sync
  from g_dbus_connection_call_sync_internal from
  g_dbus_connection_call_sync

Status in gnome-software package in Ubuntu:
  Confirmed
Status in gnome-software source package in Xenial:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at 
https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1802680] Re: Adding keyboard layout broken without logout

Thank you for your bug report. What Ubuntu version do you use? There is
a know issue in 18.10 which is resolved 3.30.2 (which isn't in Ubuntu
yet)

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Adding keyboard layout broken without logout

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  On my system, the default keyboard layout is English (Colemak). I have
  English (US) as a secondary keyboard layout.

  I attempted to add Russian, which worked. However, when I switched to
  it using Super+Space, input was really done in Qwerty. Both Russian
  and English (US) were effectively qwerty options until I logged out
  and back in.

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

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

[Desktop-packages] [Bug 1648534] Re: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_in

2018-12-07 Thread Marius Gedminas

Saw this crash for the first time.

I'm on Ubuntu 18.10.  Every time I ask gnome-software to check for
updates, the number of open files (watch 'ls /proc/$(pidof gnome-
software)/fd') grows by 25, then drops a bit and settles down to 7
higher than it was before.

I'm attaching two snapshots of ls -l /proc/$(pidof gnome-software)/fd,
before I triggered an update check, and after it told me there were no
updates available.


** Attachment added: "before-update.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+attachment/5220140/+files/before-update.txt

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

Title:
  gnome-software crashed with SIGTRAP in g_wakeup_new from
  g_main_context_new from g_dbus_connection_send_message_with_reply_sync
  from g_dbus_connection_call_sync_internal from
  g_dbus_connection_call_sync

Status in gnome-software package in Ubuntu:
  Confirmed
Status in gnome-software source package in Xenial:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at 
https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1789082] Re: Wacom - change screen causes log out

Could you add your journalctl log after getting the issue?

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

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

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

Title:
  Wacom - change screen causes log out

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

Bug description:
  After setting the wacom to map single screen then set one of the
  buttons to change screen, on each press it does change screen,
  although it does go through the both screen mode as well, which is
  annoying. However, on each press of the button you are also logged out
  and have to log in again, this makes this function not useable

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 26 11:12:41 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-05-21 (96 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1589052] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

** Information type changed from Private to Public

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

Title:
  gnome-control-center crashed with SIGSEGV in
  g_type_check_instance_cast()

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

Bug description:
  1. Open the network panel in g-c-c
  2. Run `sudo service network-manager restart`

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Jun  4 03:00:24 2016
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2015-05-19 (381 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc283b5691b :
movzbl 0x16(%rdx),%eax
   PC (0x7fc283b5691b) ok
   source "0x16(%rdx)" (0x7001e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
g_type_check_instance_cast()
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (41 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sbuild sudo

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

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

[Desktop-packages] [Bug 1772811] Re: different behaviors for switch display mode between xenial and bionic

Ok, good. So it means the function is fixed, a better experience would
be to not show the UI at all or keep it on screen longer then

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

Title:
  different behaviors for switch display mode between xenial and bionic

Status in OEM Priority Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  When the "Fn lock" is enabled, we can switch the video mode by one key: 
video-key (Fn+F8).
  But, the key event is too frequent. It's hard to select the wanted video mode.

  Reproduce steps: Press down the Video-out hotkey

  Expected results: User can select Video mode precisely by Video-out hotkey
  Actual results: The speed of switch video mode is too fast makes can not 
select Video mode precisely

  Notebook: XPS 13

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772811/+subscriptions

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

[Desktop-packages] [Bug 1318898] Re: Keyboard Shortcut to HUD (Left Alt) Conflicts with that to Taking Screenshot to Current Window (Alt + PrScrn)

There is no HUD in recent versions of Ubuntu/under GNOME, closing that
one

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

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

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

Title:
  Keyboard Shortcut to HUD (Left Alt) Conflicts with that to Taking
  Screenshot to Current Window (Alt + PrScrn)

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

Bug description:
  To Reproduce:
  1. Click on the title bar of any open window so that it is on top.
  2. Press PrScrn while holding the left Alt key.

  Expected:
  The 'Save Screenshot' dialog pops up.

  Actually:
  When left Alt key is pressed, HUD always pops up and makes it impossible to 
take that screenshot.

  The default keyboard shortcut to HUD is set as 'Alt L', and 'Take screenshot 
of a window' as 'Alt + Print'.
  And HUD doesn't wait for a key-releasing before it pops, which basically 
disables every combination with the left Alt key.
  After disabling the shortcut to HUD, screenshot taking works fine.

  $ lsb_release -rd
  Description:Ubuntu 14.04 LTS
  Release:14.04
  $ apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:3.6.3-0ubuntu56
Candidate: 1:3.6.3-0ubuntu56
Version table:
   *** 1:3.6.3-0ubuntu56 0
  500 http://mirrors.aliyun.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  This problem has been there for a long time. I noticed it since 12.10,
  if I remember correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu56
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 13 12:42:06 2014
  InstallationDate: Installed on 2012-08-12 (639 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2014-04-25 (17 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 1804923] Re: App freezes on Wifi page

Thank you for your bug report. Could you get a backtrace of gnome-
control-center when it is frozen (https://wiki.ubuntu.com/Backtrace)?
Could you also add your journalctl log from around the time of the
issue?

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

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

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

Title:
  App freezes on Wifi page

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

Bug description:
  The gnome-control-center app intermittently freezes when I'm on the
  WiFi page.

  Repro Steps:
  1. Start gnome-control-center.
  2. Go to the WiFi page (if not already on it).
  3. Click or scroll around on the page.

  Expected Result:
  Clicking and scrolling works normally, and is responsive.

  Actual Result:
  The app freezes and clicking and scrolling stops working intermittently. 
Perhaps it is happening when trying to refresh the WiFi networks list?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 24 00:45:28 2018
  InstallationDate: Installed on 2018-11-04 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account

Thank you for the debugging. I don't think goa requires IPv6, could you give 
details on how you disabled IPv6? Maybe doing the same steps is enough for 
others to reproduce the issue.
The issue connecting to ppas when IPv6 is enabling is a bug by itself, either 
in the software or in your local network configuration

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

** Package changed: gnome-control-center (Ubuntu) => gnome-online-
accounts (Ubuntu)

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

Title:
  Not able to log in into Google Account, aswell as Microsoft account

Status in gnome-initial-setup package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  After the first boot up of Ubuntu 18.10, it invites me to log-in into
  several accounts, including Google and Microsoft accounts. After I
  log-in into Ubuntu One, my next step is to log in my Google Account,
  but the log-in page never loads, and when it does (after a couple of
  minutes), and I insert my log in credentials, it fails the log-in
  process, all of this happens with the Microsoft account too. The
  Ubuntu One account logs-in without a hitch, but the rest does not.

  1) Description:   Ubuntu 18.10
  Release:  18.10

  2) gnome-initial-setup:
Instalado: 3.30.0-1ubuntu3
Candidato: 3.30.0-1ubuntu3.1
Tabela de versão:
   3.30.0-1ubuntu3.1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.0-1ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-initial-setup 3.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 11:12:31 2018
  ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
  InstallationDate: Installed on 2018-11-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1795142] Re: Allow for a custom period of inactivity before going to sleep to be selected

Thank you for your bug report, that's not something we plan to change at
the Ubuntu level but feel free to report it to the software writters on
https://gitlab.gnome.org/GNOME/gnome-control-center/issues

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Allow for a custom period of inactivity before going to sleep to be
  selected

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  The times of inactivity you are allowed to set your computer to sleep
  after are predetermined. I would like to be able to define these
  times, preferably in minutes. I know I am probably able to change the
  value through text files and the command line, but Ubuntu should be as
  user-friendly as it can be. Having to use a command line for simple
  things doesn't help with that.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 29 17:26:33 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1687864] Re: auto-login and "privacy -> auto screen lock -> disable" do not work

Thank you for your bug report, could you describe what is the issue exactly on 
bionic and add a journalctl log? From your description it doesn't seem like a 
bug
the autologin setting is for boot only, not for bypassing the screensaver on 
resume from suspend
the "auto lock screen" is for idle not for after suspend

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

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

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

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

Title:
  auto-login and "privacy -> auto screen lock -> disable" do not work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On my machine, after booting I always have to type in my password,
  allthough I set "settings -> users -> auto login".

  The same happens after resume from suspend, allthough I set "privacy
  -> auto screen lock" to "disabled". In both cases the screen attached
  appears.

  My system:
  ubuntu 16.10
  gnome desktop
  lightdm

  Cheers,
  Wolf

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

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

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

2018-12-07 Thread Lennart Rolland

This affects me.

My hw:

 + Lenovo P70
 + Cooler Master - Quickfire XTi

Description of problem:

After fresh boot I can use media keys on lenovo built in keybaord as
well as the Fn + pgup/pgdn keys on the external USB keybaord to adjust
audio volume.

But after hibernation or other power interruption this stops working.
Only workaround is reboot.


It has been like this since I installed 18.04 fresh when it was new.

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

Title:
  Keyboard shortcuts not operational on 18.04

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

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797840] Re: Event at 11:50 dont display properly on week view

Thx, It's the same as https://gitlab.gnome.org/GNOME/gnome-
calendar/issues/180

** Changed in: gnome-calendar (Ubuntu)
   Status: New => Triaged

** Summary changed:

- Event at 11:50 dont display properly on week view
+ Short events dont display properly on week view

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

Title:
  Short events dont display properly on week view

Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1 LTS (64-bit)
  gnome 3.28.2

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

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

[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

** Summary changed:

- [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not automatically 
detected
+ [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme

The CPU regression looks similar to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=909818#90 which has been fixed in
https://gitlab.freedesktop.org/fontconfig/fontconfig/commit/5f12f564 ,
we should probably backport that one

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

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

Title:
  Backport uuid based cache file naming scheme

Status in fontconfig package in Ubuntu:
  New
Status in fontconfig source package in Bionic:
  Fix Committed

Bug description:
  Fontconfig 2.13.0 changed the cache file naming scheme to be based on
  the contents of ".uuid" file in the directory rather than a hash of
  the directory name.  On a pure debs system this doesn't really matter
  since everything is using the same libfontconfig.so.

  When snaps are involved, it can lead to some apps not seeing the cache
  files produced by a different fontconfig version.  In particular,
  while libfontconfig 2.13 can reuse 2.12's cache files for read only
  directories, the reverse is not true.  This will be a problem for apps
  built on top of the "core18" base snap when run on later Ubuntu
  releases (cosmic, disco, etc).

  By providing a backport of the UUID cache file feature to bionic for
  use by snap applications, we'd avoid this.  Having it in bionic-
  updates would be ideal so that snapcraft picks it up automatically.

  [Impact]

   * This update changes how fontconfig cache files are named, instead
  of using md5($dir), it instead uses the contents of a $dir/.uuid file.
  No changes are made to the format of the cache file contents.

   * This change is primarily intended for use by snap applications
  built with core18: as the updated libfontconfig will fall back to the
  md5 cache file names for read-only directories without a .uuid file,
  they will be able to reuse cache files from any host system running
  fontconfig >= 2.11.95

  [Test Case]

   * After installing the update, cache files should be generated in
  /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c-
  21fc9153568c-le64.cache-7" (note the extra dashes not present in the
  MD5 based cache file names).

  [Regression Potential]

   * Applications using a non-default libfontconfig could end up not
  finding the new cache files and regenerating them in
  ~/.cache/fontconfig.

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

2018-12-07 Thread Pete

I am still seeing this with Mint 18.3 and 19  on at least 4 different
PCs but with nvidia graphics. Is there a fix somewhere?

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Relevant details]
  This bug also affects Trusty and all distributions based on it, like 
Elementary OS Freya.

  
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1718215] Re: versions of cups-filters and libqpdf do not match

2018-12-07 Thread Jouni Mettala

Hi Laura. This bug was happening in development version of Ubuntu and is
fixed. You can file a new bug. Open terminal and copy "ubuntu-bug cups"
without quotes there.

http://www.openprinting.org/printer/HP/HP-OfficeJet_Pro_8600 says this
printer is paperweight but there is a comment that says printer works.

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

Title:
  versions of cups-filters and libqpdf do not match

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  When I print a document it is sent to the printer (pdf, libreoffice,
  gedit, ...) but stops immediately and is not printed. It cannot be
  resumed and documents sent to the PDF driver result in a blank file.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cups 2.2.4-7
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 16:07:01 2017
  InstallationDate: Installed on 2013-09-03 (1476 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  Lpstat:
   device for Deskjet: hp:/net/Deskjet_D5500_series?ip=192.168.1.50
   device for HP-Photosmart-5520-series: 
hp:/net/Photosmart_5520_series?zc=HPFC15B4E0E72B
   device for HP-Photosmart-C5200-series: 
usb://HP/Photosmart%20C5200%20series?serial=MY84AG220H0559=1
   device for MP210: usb://Canon/MP210%20series?serial=638BE0=1
   device for PDF: cups-pdf:/
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-Photosmart-5520-series.ppd', '/etc/cups/ppd/PDF.ppd', 
'/etc/cups/ppd/HP-Photosmart-C5200-series.ppd', '/etc/cups/ppd/Deskjet.ppd', 
'/etc/cups/ppd/MP210.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-Photosmart-5520-series.ppd: Permission denied
   grep: /etc/cups/ppd/PDF.ppd: Permission denied
   grep: /etc/cups/ppd/HP-Photosmart-C5200-series.ppd: Permission denied
   grep: /etc/cups/ppd/Deskjet.ppd: Permission denied
   grep: /etc/cups/ppd/MP210.ppd: Permission denied
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1797840] Re: Event at 11:50 dont display properly on week view

2018-12-07 Thread Garcia David

Yes, even 15 minutes


El 3/12/18 a las 14:10, Sebastien Bacher escribió:
> How long is the event? Is it only 10 minutes? If so that's a known
> upstream issue than short event are not well displayed on the week view
>

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

Title:
  Event at 11:50 dont display properly on week view

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.1 LTS (64-bit)
  gnome 3.28.2

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

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

[Desktop-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme

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

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

Title:
  Backport uuid based cache file naming scheme

Status in fontconfig package in Ubuntu:
  New
Status in fontconfig source package in Bionic:
  Fix Committed

Bug description:
  Fontconfig 2.13.0 changed the cache file naming scheme to be based on
  the contents of ".uuid" file in the directory rather than a hash of
  the directory name.  On a pure debs system this doesn't really matter
  since everything is using the same libfontconfig.so.

  When snaps are involved, it can lead to some apps not seeing the cache
  files produced by a different fontconfig version.  In particular,
  while libfontconfig 2.13 can reuse 2.12's cache files for read only
  directories, the reverse is not true.  This will be a problem for apps
  built on top of the "core18" base snap when run on later Ubuntu
  releases (cosmic, disco, etc).

  By providing a backport of the UUID cache file feature to bionic for
  use by snap applications, we'd avoid this.  Having it in bionic-
  updates would be ideal so that snapcraft picks it up automatically.

  [Impact]

   * This update changes how fontconfig cache files are named, instead
  of using md5($dir), it instead uses the contents of a $dir/.uuid file.
  No changes are made to the format of the cache file contents.

   * This change is primarily intended for use by snap applications
  built with core18: as the updated libfontconfig will fall back to the
  md5 cache file names for read-only directories without a .uuid file,
  they will be able to reuse cache files from any host system running
  fontconfig >= 2.11.95

  [Test Case]

   * After installing the update, cache files should be generated in
  /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c-
  21fc9153568c-le64.cache-7" (note the extra dashes not present in the
  MD5 based cache file names).

  [Regression Potential]

   * Applications using a non-default libfontconfig could end up not
  finding the new cache files and regenerating them in
  ~/.cache/fontconfig.

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

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

[Desktop-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme

I installed 'fontconfig' from proposed and the package installation failed on 
that error
'fc-cache: symbol lookup error: fc-cache: undefined symbol: 
FcDirCacheCreateUUID'

It looks like the fontconfig binary should depends on the new version of
the lib and doesn't?

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

Title:
  Backport uuid based cache file naming scheme

Status in fontconfig package in Ubuntu:
  New
Status in fontconfig source package in Bionic:
  Fix Committed

Bug description:
  Fontconfig 2.13.0 changed the cache file naming scheme to be based on
  the contents of ".uuid" file in the directory rather than a hash of
  the directory name.  On a pure debs system this doesn't really matter
  since everything is using the same libfontconfig.so.

  When snaps are involved, it can lead to some apps not seeing the cache
  files produced by a different fontconfig version.  In particular,
  while libfontconfig 2.13 can reuse 2.12's cache files for read only
  directories, the reverse is not true.  This will be a problem for apps
  built on top of the "core18" base snap when run on later Ubuntu
  releases (cosmic, disco, etc).

  By providing a backport of the UUID cache file feature to bionic for
  use by snap applications, we'd avoid this.  Having it in bionic-
  updates would be ideal so that snapcraft picks it up automatically.

  [Impact]

   * This update changes how fontconfig cache files are named, instead
  of using md5($dir), it instead uses the contents of a $dir/.uuid file.
  No changes are made to the format of the cache file contents.

   * This change is primarily intended for use by snap applications
  built with core18: as the updated libfontconfig will fall back to the
  md5 cache file names for read-only directories without a .uuid file,
  they will be able to reuse cache files from any host system running
  fontconfig >= 2.11.95

  [Test Case]

   * After installing the update, cache files should be generated in
  /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c-
  21fc9153568c-le64.cache-7" (note the extra dashes not present in the
  MD5 based cache file names).

  [Regression Potential]

   * Applications using a non-default libfontconfig could end up not
  finding the new cache files and regenerating them in
  ~/.cache/fontconfig.

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

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

[Desktop-packages] [Bug 1803190] Re: non-empty directory will not delete

deleting a directory works fine with 1.36.1-0ubuntu1.2

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

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

Title:
  non-empty directory will not delete

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Summary: Deleting a directory containing 1+ files doesn't succeed.
  Nautilus shows the directory as deleted, but upon refresh it reappears
  (it was never deleted).

  * Test case

  Connect to a smb share and delete a directory

  * Regression potential

  The change is in the smb backend, check that this work still work fine

  
  Reported on https://bugzilla.gnome.org/show_bug.cgi?id=792147

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

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

[Desktop-packages] [Bug 1803158] Re: Copying file to Windows server (SMB2) via gvfsd-fuse and gvfsd-smb fails with EINVAL

copies on 1.36.1-0ubuntu1.2 work as they should

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

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

Title:
  Copying file to Windows server (SMB2) via gvfsd-fuse and gvfsd-smb
  fails with EINVAL

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  If a share on a Windows file server (not a Samba server) is mounted
  and uses the SMB2 protocol, any attempt to copy or create a file for
  writing (e.g. using the cp or cat commands from the bash shell) on the
  mount point via FUSE will create a zero-length file but the open will
  return with an EINVAL error.

  * Test case

  - mount a sahre using smb2
  - try to copy a file on the mount from e.g a command line

  * Regression potential

  Check that samba interactions keep working as they should

  The bug was reported upstream on
  https://bugzilla.gnome.org/show_bug.cgi?id=795805

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

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

[Desktop-packages] [Bug 1630905] Re: Loss of lan connection causes applications using gvfsd-sftp to hang until demon is killed

1.36.1-0ubuntu1.2 keeps working fine after suspend/resume cycles

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

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

Title:
  Loss of lan connection causes applications using gvfsd-sftp to hang
  until demon is killed

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  The gvfsd-sftp service sometime hangs

  * Test case
  - connect to a ssh server from nautilus
  - suspend the computer for longer than the ssh timeout (1 hour for example)
  - resume and try to use the connection

  * Regression potential
  Check that nautilus access to remote servers still work correctly

  -

  
  This affects an installation of Ubuntu 14.04 on a Lenovo laptop.
  When applications like nautilus or Bluefish are connected to a remote 
fileshare using sftp (ssh) via a lan connection, if the connection is lost and 
re-established the old process seems to hang blocking attempts to save data or 
use Nautilus in any way.

  This typically occurs when the connection is either lost accidentally
  or when the laptop is suspended and then unsuspended causing a loss of
  wireless connection.

  The workaround is to kill the gvsftp process manually and then
  recreate the remote connection using Nautilus.

  This bug leads to data loss if, for instance, the laptop is closed
  (starting suspend mode) while in the middle of a task that must be
  saved.

  ERROR: apport (pid 5064) Thu Oct  6 17:38:29 2016: called for pid 3309, 
signal 6, core limit 0
  ERROR: apport (pid 5064) Thu Oct  6 17:38:29 2016: executable: 
/usr/lib/gvfs/gvfsd-sftp (command line "/usr/lib/gvfs/gvfsd-sftp --spawner :1.4 
/org/gtk/gvfs/exec_spaw/28")
  ERROR: apport (pid 5064) Thu Oct  6 17:38:29 2016: debug: session gdbus call: 
(true,)

  ERROR: apport (pid 5064) Thu Oct  6 17:38:30 2016: wrote report
  /var/crash/_usr_lib_gvfs_gvfsd-sftp.1000.crash

  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  gvfs:
    Installed: 1.20.3-0ubuntu1.2
    Candidate: 1.20.3-0ubuntu1.2
    Version table:
   *** 1.20.3-0ubuntu1.2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.20.1-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-12-07 Thread Gerhard Beck

In my case the system is slowing down very much and I search for the
reason. Don't know whether this is one.

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

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

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

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

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

[Desktop-packages] [Bug 1807138] Re: [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected

2018-12-07 Thread Arne De Herdt

I'm using a Razer Blade 15 2018

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

Title:
  [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not
  automatically detected

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1728764] Re: gnome-screenshot will no longer save screenshots anywhere

Can you try starting gnome-screenshot from a command line? does it print
any error when taking the screenshot or saving it?

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

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

Title:
  gnome-screenshot will no longer save screenshots anywhere

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  It was working quite alright 2 weeks ago. I have changed nothing since
  then.

  Tonight, when trying to screencap for the gnome-sushi bug, it would
  flash as if taking a screencap for both fullscreen, and selected area
  style screenshots.

  However, it wouldn't save the screenshot anywhere.

  I'm not certain where it used to save (by default, up until 2 weeks
  ago), but I think it was Pictures.

  If I search in Nautilus for "Screenshot from 2017-10-30" I see
  previous screenshots, up until 10-30, and there are no screenshots
  saved from today, or anything since 2 weeks ago.

  I tried changing the auto-save-directory in gconf, as well as via
  terminal commands. I tried with different styles: "file:///.." as
  well as simply "/home" No matter what, screenshots still flash and
  make the click sound, but do not save in the directory. Not Desktop,
  Pictures, /tmp, Downloads.

  If I call "gnome-screenshot --interactive" from Terminal, the save
  dialog does successfully save the screenshot.

  I have no idea how to replicate this bug, because I did nothing to
  create this bug. Just 2 weeks after taking several successful
  screenshots, gnome-screenshot no longer saves screenshots. Anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 30 22:11:36 2017
  InstallationDate: Installed on 2017-09-20 (40 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to artful on 2017-10-04 (26 days ago)

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

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

[Desktop-packages] [Bug 1639675] Re: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all

The issue was fixed in the kernel
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=c1732ede5

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

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

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

Title:
  [X555UB, Realtek ALC256, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On ubuntu 16.04 only mic does not work but now 16.10  sounds don`t
  play too

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrey 2177 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  7 05:17:43 2016
  InstallationDate: Installed on 2016-11-07 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrey 2177 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1806860] Re: Pulseaudio module-jack-source unable to connect to jackd2

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

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

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

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  
  So it seems module-jack-source / sink are guessing the wrong shared memory 
paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2 
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1604235] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all, mic does not record any sound tried almost all ways to fix it, but nothing worked.

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

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all, mic does not
  record any sound tried almost all ways to fix it, but nothing worked.

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Even headphones does not automatically detect in this laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yashwanth   3716 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jul 19 10:04:49 2016
  InstallationDate: Installed on 2016-07-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yashwanth   3716 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

Could be that it requires an hack similar to
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/sound/pci/hda/patch_realtek.c?id=b72f936f with your ids
being 1025:1269

Do you feel like manually patching that in the driver you build to see
if that fixes the issue?

it would be adding a line
SND_PCI_QUIRK(0x1025, 0x1269, "Acer Swift SF315-52", 
ALC286_FIXUP_ACER_AIO_MIC_NO_PRESENCE),

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1807138] Re: [HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected

What laptop model do you use? Upstream kernel driver has regular fixes
like https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/sound/pci/hda/patch_realtek.c?id=c1732ede5 (the one
should be in the current kernel already though)

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Low

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

** Summary changed:

- [HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected
+ [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not automatically 
detected

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

Title:
  [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not
  automatically detected

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

2018-12-07 Thread hamid

I still have the same issue on my Desktop PC, now running 18.04, fresh
install (not upgrade from the  17.10 that had this issue), it takes a
good ~8-10 seconds for my desktop to show after hitting enter on the
login prompt.

I haven't tried turning off gnome extensions yet, I only just saw that
suggestion, but will try it when I get home. I have a laptop, a bit less
powerful than the desktop, running the same gnome extensions, but which
doesn't exhibit the login delay.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect:
  Connection refused

  then:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1807276] Re: Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

Thank you for your bug report. Can you add your journalctl log after
triggering the issue? Swipping from the bottom on an inspiron 11 using
the Ubuntu (x11) default session works here on bionic & cosmic

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

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

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

Title:
  Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.10 / GNOME Shell 3.30.1
  ALSO
  Ubuntu 18.04 LTS / GNOME Shell 3.28.1

  Steps to reproduce on our end:

  - Login (Xorg as default)
  - Attempt to swipe up with finger from below screen
  RESULT: It draws a thin vertical (desktop) selection box, but no OSK
  - Logout
  - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland'
  - ps -e | grep Xwayland #shows 'Xwayland' process is running
  - Repeat swipe up with finger from below screen
  RESULT: OSK shows up as expected

  This has been verified both in 1920x1080 as well as 3840x2160
  resolutions (also with various scaling options selected)

  Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/839

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

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

[Desktop-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

** Changed in: cups (Debian)
   Status: New => Fix Released

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

Title:
  MaxJobTime=0 results in jobs being cancelled immediately instead of
  never

Status in CUPS:
  New
Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Trusty:
  Invalid
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress
Status in cups package in Debian:
  Fix Released

Bug description:
  [Impact]

   Setting the cupsd option MaxJobTime to 0 should make the server wait 
indefinitely for the job to be ready for print. Instead, after updating 
job-cancel-after option with MaxJobTime=0 value it results in immediate 
cancelling.
  This leads to problems with using filters that take some time to process - 
the user needs to set MaxJobTime to a ridiculously high value to ensure the job 
is not going to get cancelled instead of just disabling the cancelling timeout.

  [Test Case]

   1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf.
   2. Setup a filter that takes at least several seconds to process.
  (please find a sample imagetopdf wrapper introducing 5s delay)
   3. Submit a print job matching the filter, e.g.
  lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper

  Expected result:
  The job is printed after the 5s delay.

  Actual result:
  The job is cancelled.

  [Regression Potential]

   The scope of the change is limited to fixing the MaxJobTime handling
   in scheduler/job.c and scheduler/printers.c. There should be no
   difference in behavior except for the special value of MaxJobTime=0.

  [Other Info]
  Original bug description:

  When using CUPS filters, these filters can take a few seconds to
  complete.

  In this case no documents are allowed to be lost on printing failures,
  so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu
  14.04.

  With cups on 18.04, you get the following message in /var/log/cups/error_log 
whenever the filter takes a little longer:
  I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds.

  Then, the job is deleted and lost.

  "MaxJobTime 0" is documented as "indefinite wait", but apparently cups
  treats is as "wait almost not at all".

  This issue appears to have also been filed upstream:
  https://github.com/apple/cups/issues/5438

  Temporary workaround is to set the MaxJobTime to a very large value
  instead (e.g. 3 years)

  Trusty is not affected by this bug.

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

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

[Desktop-packages] [Bug 1795854] Re: recently glitchy, no response to keyboard or mouse

2018-12-07 Thread pleabargain

You Can close this bug.
The glitchyness went away some time ago with one of the system updates.
thank you
Dennis

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

Title:
  recently glitchy, no response to keyboard or mouse

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Since update 2 days ago
  UI has been glitchy, keyboard and mouse stop responding
  click to open file... nothing happens
  mouse does not respond...then cursor starts moving again.

  This is UNWANTED behavior!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  3 13:37:56 2018
  InstallationDate: Installed on 2015-08-23 (1136 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (43 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1721893] Re: /usr/bin/gkbd-keyboard-display:11:get_preferred_height_for_width:gtk_widget_query_size_for_orientation:gtk_widget_compute_size_for_orientation:gtk_widget_get_prefe

3.26.0-3ubuntu0.18.04.1 resolves the segfault/shows the correct keymap
as well

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

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

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

Status in libgnomekbd :
  Confirmed
Status in libgnomekbd package in Ubuntu:
  Fix Released
Status in libgnomekbd source package in Bionic:
  Fix Committed
Status in libgnomekbd source package in Cosmic:
  Fix Committed

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

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

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

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

  -

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

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

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

[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

It's still unclear to me what's the problem is here? Is that only the
warning in the log or is there a feature not working?

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

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

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

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

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

[Desktop-packages] [Bug 1750069] Re: [MIR] xdg-desktop-portal-gtk

2018-12-07 Thread Ken VanDine

@seth-arnold You approved this for cosmic only.  What's the status of
getting this approved for bionic and xenial?  Getting this in bionic and
xenial would greatly improve the snap desktop support.

** Also affects: xdg-desktop-portal-gtk (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: xdg-desktop-portal-gtk (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  [MIR] xdg-desktop-portal-gtk

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk source package in Xenial:
  New
Status in xdg-desktop-portal-gtk source package in Bionic:
  New

Bug description:
  Availability
  
  Actively maintained in debian and we'll sync from debian again when 0.10 is 
avaiable.

  Built for all supported architectures.

  Rationale
  =
  Required for snaps.

  Security
  
  No known security issues, but due to the nature of this package, a security 
review is probably needed.

  
https://security-tracker.debian.org/tracker/source-package/xdg-desktop-portal-gtk
  https://launchpad.net/xdg-desktop-portal-gtk/+cve

  Quality assurance
  =
  - The Desktop Packages bug team is subscribed.

  https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xdg-desktop-portal-gtk
  https://github.com/flatpak/xdg-desktop-portal-gtk/issues

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.3

  debhelper compat 10, dh 7 style simple rules

  Maintenance
  ===
  - Actively developed upstream. Last release was 0.10, this week.
  https://github.com/flatpak/xdg-desktop-portal-gtk/commits/master

  Well-maintained in Debian by Simon McVittie (Debian's Flatpak maintainer). 
Team-maintained.
  https://salsa.debian.org/debian/xdg-desktop-portal-gtk

  Background information
  ==
  This is needed to make xdg-desktop-portal useful in Ubuntu Desktop.  See 
xdg-desktop-portal MIR bug LP: #1749672

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

The samba commit seems to be
https://github.com/samba-team/samba/commit/0dae4e2f

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

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Triaged
Status in gvfs source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that 
Nautilus displays "Empty Folder" when clicking "Windows Network"

  * Test case
  Try to browse a smb share from a bionic client

  * Regression potential
  Check that smb browsing/mounts still work as they should

  ---

  Nautilus should show smbtree nad host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
  smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by 
the processing engine)
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo 
(pid=5708)
  smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo)
  smb-network: send_reply(0x55b19a2e7820), failed=0 ()
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708)
  smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate)
  smb-network: send_reply(0x55b19a2c30c0), failed=0 ()

  Proposed solution:
  Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla
  [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394
  which implements "change to NT1" in gvfs-smb-browse to browse smbtree to 
aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to 
unsafe NT1 which most users are doing to correct this bug.

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

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

[Desktop-packages] [Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree

Thanks for the testing. Indeed there is a problem, from the build log

"Native dependency smbclient found: YES 0.3.1
Checking for function "smbc_setOptionProtocols" : NO"

The API needed is too new for our current libsmbclient version, we need to 
backport that one as well.
The other changes from the SRU are fine though and that one is just a no-change 
without the API so it probably makes sense to validate the current SRU anyway 
and do another round for libsmbclient/rebuild gvfs later

** Also affects: samba (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: gvfs (Ubuntu)
   Importance: Low => High

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

Title:
  gvfs-smb-browse can't browse samba/smb tree

Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Triaged
Status in gvfs source package in Bionic:
  Fix Committed
Status in gvfs source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that 
Nautilus displays "Empty Folder" when clicking "Windows Network"

  * Test case
  Try to browse a smb share from a bionic client

  * Regression potential
  Check that smb browsing/mounts still work as they should

  ---

  Nautilus should show smbtree nad host on the smb network.

  When inputing this command:
  killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse

  You can see the error:
  smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
  smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by 
the processing engine)
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo 
(pid=5708)
  smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo)
  smb-network: send_reply(0x55b19a2e7820), failed=0 ()
  smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708)
  smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate)
  smb-network: send_reply(0x55b19a2c30c0), failed=0 ()

  Proposed solution:
  Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla
  [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394
  which implements "change to NT1" in gvfs-smb-browse to browse smbtree to 
aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to 
unsafe NT1 which most users are doing to correct this bug.

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

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

[Desktop-packages] [Bug 1721893] Re: /usr/bin/gkbd-keyboard-display:11:get_preferred_height_for_width:gtk_widget_query_size_for_orientation:gtk_widget_compute_size_for_orientation:gtk_widget_get_prefe

Using 3.26.0-3ubuntu0.18.10.1 the command from the testcase shows the
layout without segfault, also trying with the IPA ibus method works now,
marking as verified for cosmic

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

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

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

Status in libgnomekbd :
  Confirmed
Status in libgnomekbd package in Ubuntu:
  Fix Released
Status in libgnomekbd source package in Bionic:
  Fix Committed
Status in libgnomekbd source package in Cosmic:
  Fix Committed

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

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

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

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

  -

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

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

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

[Desktop-packages] [Bug 1803186] Re: update to 1.38.1

Using 1.38.1-0ubuntu1.1 from cosmic-proposed, gvfs/nautilus works
without visible issue, marking as verified for that serie

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

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

Title:
  update to 1.38.1

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Committed

Bug description:
  * Impact

  That's a standard GNOME bugfix update, we should includ eit

  * Test case

  Make sure nautilus handling of files, mounts, device is still correct.
  The SRU is a GNOME one so follows the standard GNOME testing

  * Regression potentiel

  The changes are limited, mostly to camera and smb handling so those
  backend need the most testing

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

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

[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2

bah, sorry, you probably need the lib as well
$ wget 
https://launchpad.net/ubuntu/+source/alsa-lib/1.1.7-2/+build/15743375/+files/libasound2-data_1.1.7-2_all.deb
 
https://launchpad.net/ubuntu/+source/alsa-lib/1.1.7-2/+build/15743375/+files/libasound2_1.1.7-2_amd64.deb
$ sudo dpkg -i libasound*.deb

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)

2018-12-07 Thread R

I ~think~ I just fixed this issue on my PC (GA-B250M-DS3H with HDA Intel PCH,
ALC887-VD). Symptoms just like described on this thread:
- repeated "Jack 'Front Headphone Jack' is now plugged in" / plugged out
messages in pulseaudio logs
- acpi_listen showing plug/unplug events
- once headphones are plugged into the front jack, issue stops
- hdajackretask works as a workaround
- side effects: audio stutters, graphics freezes for a split second (looks very
much like video card lagging). OSD notifications turned off so I didn't have
those.

I had the front panel audio cable go behind the motherboard, attached to the
other cables in the case. Once I re-connected the cable to go separately from
everything else, the problem seems to have completely disappeared. Crosstalk
with other cables / motherboard seems like a likely root cause.

`pulseaudio - --log-time=1` had 'plugged in' followed by 'plugged
out' at very close timestamps (~20ms). Debouncing could avoid the side
effects and hide the problem.

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

Title:
Volume notification keeps popping up constantly (the notify-OSD bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2

2018-12-07 Thread Simon Williams

After a reboot, I now get:
dpkg: error processing archive libasound2-data_1.1.7-2_all.deb (--install):
 installing libasound2-data would break libasound2:amd64, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 libasound2-data_1.1.7-2_all.deb

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2

2018-12-07 Thread Simon Williams

I get 'dpkg frontend is locked by another process' after the dpkg
command. No idea what process this is.

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-12-07 Thread Gerhard Beck

Same problem on 18.04 LTS:
11:26:56 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
11:26:38 spice-vdagent: Cannot access vdagent virtio channel 
/dev/virtio-ports/com.redhat.spice.0
11:25:53 gnome-session-b: CRITICAL: Unable to create a DBus proxy for 
GnomeScreensaver: Fehler beim Aufruf von StartServiceByName für 
org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1

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

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

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

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

  Best regards,
  --
  Cristian Aravena Romero (caravena)

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

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

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

[Desktop-packages] [Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

2018-12-07 Thread Gerhard Beck

I can confirm the bug on an HP Laptop.
I got no gnome-shell extensions installed
I don't find it in the login, but I feel there's a quite long delay after 
logging in and before the desktop starts

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect:
  Connection refused

  then:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2

Could people having the issue test if that fixes it for them

$ wget 
https://launchpad.net/ubuntu/+source/alsa-lib/1.1.7-2/+build/15743375/+files/libasound2-data_1.1.7-2_all.deb
$ sudo dpkg -i libasound2-data_1.1.7-2_all.deb
$ reboot

it should work on bionic and cosmic

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1797749] Re: Drag and drop from File Roller to Nautilus not working

Thank you for your bug report. It works fine here, do you have any
warning on the command line if you start file-roller from there? What
type of view do you use in nautilus (icon? list? zoom level?)

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

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

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

Title:
  Drag and drop from File Roller to Nautilus not working

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  This started to appear after updating to 18.10.

  Steps to reproduce:
  * open any archive with File Roller
  * open any location in Nautilus
  * drag a file or directory from File Roller to Nautilus

  Expected:
  * selected files/directories are extracted to the drop location

  Actually happens:
  * nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu6
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 14 10:26:22 2018
  InstallationDate: Installed on 2017-12-20 (297 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-04-20T17:55:23.166649
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1806279] Re: No full screen possible in portrait mode

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

** Summary changed:

- No full screen possible in portrait mode
+ No full screen possible when the minimal width is higher than the horizontal 
resolution

** Summary changed:

- No full screen possible when the minimal width is higher than the horizontal 
resolution
+ No full screen possible when the minimal window width is higher than the 
horizontal resolution

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

Title:
  No full screen possible when the minimal window width is higher than
  the horizontal resolution

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As described above. If I rotate my laptop and want to use it in
  portrait mode, I can only use the Gnome Calendar to a very limited
  extent, because e.g. full screen is no longer possible. I will attach
  a screenshot to clarify what I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-calendar 3.30.0-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 21:37:49 2018
  InstallationDate: Installed on 2018-11-30 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1806712] Re: [MIR] fonts-yrsa-rasa

2018-12-07 Thread Matthias Klose

looks good.

Override component to main
fonts-yrsa-rasa 1.002-2 in disco: universe/misc -> main
fonts-yrsa-rasa 1.002-2 in disco amd64: universe/fonts/optional/100% -> main
fonts-yrsa-rasa 1.002-2 in disco arm64: universe/fonts/optional/100% -> main
fonts-yrsa-rasa 1.002-2 in disco armhf: universe/fonts/optional/100% -> main
fonts-yrsa-rasa 1.002-2 in disco i386: universe/fonts/optional/100% -> main
fonts-yrsa-rasa 1.002-2 in disco ppc64el: universe/fonts/optional/100% -> main
fonts-yrsa-rasa 1.002-2 in disco s390x: universe/fonts/optional/100% -> main
7 publications overridden.


** Changed in: fonts-yrsa-rasa (Ubuntu)
   Status: New => Fix Released

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

Title:
  [MIR] fonts-yrsa-rasa

Status in fonts-yrsa-rasa package in Ubuntu:
  Fix Released

Bug description:
  * Availability

  Currently version builds fine and is in sync from Debian
  https://launchpad.net/ubuntu/+source/fonts-gujr/2:1.3
  (it's a font and arch all so only amd64 build)

  * Rationale

  It's a new depends from fonts-gujr

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the package is in sync with Debian
  - there are no open bugs on debian or launchpad

  * Dependendies

  The package has no depends

  * Standards compliance

  the package is using standard packaging (dh11) and the current the
  standards-version, it is in sync from Debian

  * Maintainance

  The package is maintained in Debian by the fonts team, the desktop
  team is going to look at issues on the Ubuntu side if requires

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-yrsa-rasa/+bug/1806712/+subscriptions

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

[Desktop-packages] [Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)

2018-12-07 Thread Santiago Gala

/metoo

App indicators visible:
* accessibility
* skype (quitting skype does not make any difference)
* remmina (quitting remmina does not make any difference)
* input languages
* standard "network-volume-battery" one
I used to have the indicator-multiload too, but I removed it due to heavy log 
spam and unreadable display.

BTW, how can one remove the accessibility or keyboard indicators? I can
no longer find where or how to remove them both, as the only
functionality I need (switch keyboard layouts) is available via key
combo.

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

Title:
  Unlocking the  screen takes 5 seconds in Xorg sessions (not so much in
  Wayland sessions)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This is a fresh installation of 18.04. After entering the password and
  pressing enter, it takes 5 seconds for the lock screen to disappear.
  This problem didn't happen on the same machine with 16.04 or 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:31:48 2018
  InstallationDate: Installed on 2018-05-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1807277] Re: Cannot set tiling background for desktop