date:20190516

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

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Fix Released
Status in systemd:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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

[Desktop-packages] [Bug 1668722] Re: 60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check

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

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

Title:
  60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check

Status in SDDM:
  New
Status in sddm package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in sddm source package in Bionic:
  Fix Released
Status in xorg source package in Bionic:
  Invalid

Bug description:
  This file:
  /etc/X11/Xsession.d/60x11-common_xdg_path
  contains references to $DESKTOP_SESSION variable.

  On one of my Ubuntu installs this variable contains: "plasma",
  on the other it contains: "/usr/share/xsessions/plasma".

  I don't know where either example comes from, but the upshot is that
  paths are added to XDG_DATA_DIRS and XDG_CONFIG_DIRS that don't exist.
  MANDATORY_PATH is also affected I believe, maybe others.

  Surely a sanity check of the generated paths is in order. Seems
  pointless to add non-existent ones.

  $XDG_SESSION_DESKTOP looks like a replacement for $DESKTOP_SESSION,
  but is that true?

  Cheers!

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

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

[Desktop-packages] [Bug 1793595] Re: [radeon] Shell freezes, mostly when running chrome or editing text files.

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

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

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

Title:
  [radeon] Shell freezes, mostly when running chrome or editing text
  files.

Status in gnome-shell package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  Freezes randomly, mostly when running chrome or editing text files.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 20 16:35:29 2018
  DistUpgraded: 2018-08-28 16:25:11,641 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] 
[1002:682c] (prog-if 00 [VGA controller])
 Subsystem: Dell Cape Verde GL [FirePro W4100] [1028:2b1e]
  InstallationDate: Installed on 2018-06-04 (108 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=fc6e98f8-e80f-4e1c-ba61-e2234c5a9be5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-08-28 (23 days ago)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A25
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA25:bd02/02/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Sep 20 16:27:01 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPixArt Dell MS116 USB Optical Mouse MOUSE, id 8
   inputDell KB216 Wired Keyboard KEYBOARD, id 9
   inputDell KB216 Wired Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1820303] Re: Ubuntu 18.04 LTS

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

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

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

Title:
  Ubuntu 18.04 LTS

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  Failure to display prior desktop login GUI (Cinnamon).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Mar 15 11:46:27 2019
  DistUpgraded: 2019-03-15 10:30:23,145 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 7340] [1043:14e7]
  InstallationDate: Installed on 2019-03-11 (4 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  MachineType: ASUSTeK COMPUTER INC. X55U
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-15 (0 days ago)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X55U.423
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X55U
  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.:bvrX55U.423:bd08/06/2013:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X55U
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Mar 15 11:19:59 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1793595] Re: [radeon] Shell freezes, mostly when running chrome or editing text files.

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

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

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

Title:
  [radeon] Shell freezes, mostly when running chrome or editing text
  files.

Status in gnome-shell package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  Freezes randomly, mostly when running chrome or editing text files.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 20 16:35:29 2018
  DistUpgraded: 2018-08-28 16:25:11,641 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] 
[1002:682c] (prog-if 00 [VGA controller])
 Subsystem: Dell Cape Verde GL [FirePro W4100] [1028:2b1e]
  InstallationDate: Installed on 2018-06-04 (108 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=fc6e98f8-e80f-4e1c-ba61-e2234c5a9be5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-08-28 (23 days ago)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A25
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA25:bd02/02/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Sep 20 16:27:01 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPixArt Dell MS116 USB Optical Mouse MOUSE, id 8
   inputDell KB216 Wired Keyboard KEYBOARD, id 9
   inputDell KB216 Wired Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1829458] [NEW] [ubuntu 19.04]All .desktop configuration files are opening in text editor

2019-05-16 Thread Ron Stephen Mathew

Public bug reported:

All .desktop configuration files are opening in text editor. Because of
that we can't creat custom shortcuts and having troubles while
application making. Please fix this bug on next update. I have an Ubuntu
19.04.

Tanks

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [ubuntu 19.04]All .desktop configuration files are opening in text
  editor

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  All .desktop configuration files are opening in text editor. Because
  of that we can't creat custom shortcuts and having troubles while
  application making. Please fix this bug on next update. I have an
  Ubuntu 19.04.

  Tanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1829458/+subscriptions

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

[Desktop-packages] [Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme

2019-05-16 Thread Omar Rigoberto Hernandez Sapiens

Same issue.

Looks like it's the snap version of communitheme-dark.

Switched to communitheme using gnome-tweaks and got the solid-white
background back, though switching back to thedark version and the
transparent background is still there.

Note: First, I tried Mihai Banu (m-banu94) solution and then returned to
snap communitheme (not wayland)

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

Title:
  Transparent background of calculator in ubuntu 18.04 using
  communitheme

Status in gnome-calculator package in Ubuntu:
  Invalid

Bug description:
  It also happen in system monitor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  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: communitheme:ubuntu:GNOME
  Date: Sat Apr 28 08:34:55 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1701047] Re: Renaming of conf file fails

2019-05-16 Thread Gunnar Hjalmarsson

** Also affects: fonts-telu-extra (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fonts-telu-extra (Ubuntu)
   Importance: Undecided => Medium

** Changed in: fonts-telu-extra (Ubuntu)
   Status: New => In Progress

** Changed in: fonts-telu-extra (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: fonts-telu-extra (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: fonts-telu-extra (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: fonts-telu-extra (Ubuntu Bionic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Description changed:

  [Impact]
  The fix of  wasn't accomplished properly. 
Renamings of conf files weren't addressed in maintainer scripts, upgrades from 
previous versions fail in this respect, and the package system generates 
warning messages.
  
  The problem has been reported in Debian, and the purpose of this bug
  report is to keep track of the progress.
  
  [Justification]
  This config file is broken in xenial and will still be broken on upgrade to 
bionic, which means the fonts in question will not be available to the system 
as intended if the user has upgraded.
  
  [Test case]
  For each of
  - fonts-beng-extra
  - fonts-deva-extra
  - fonts-gujr-extra
  - fonts-guru-extra
- - fonts-orya-extra:
+ - fonts-orya-extra
+ - fonts-telu-extra:
  
  * Purge the package if installed and clean up possible leftovers
-   due to the issue.
+   due to the issue.
  
  * Install the Xenial version of the package and find that the symlink
-   in /etc/fonts/conf.d incorrectly points to a directory.
+   in /etc/fonts/conf.d incorrectly points to a directory.
  
  * Install the version in bionic-release and find that the attempt
-   to fix the issue fails
+   to fix the issue fails
  
  * Install the version in bionic-proposed and find that it fixes the
-   issue and that the symlink now correctly points to the conf file.
+   issue and that the symlink now correctly points to the conf file.
  
  [Regression potential]
  Because this modifies maintainer scripts there is possibility of introducing 
a regression that will cause the package to fail to unpack.

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

Title:
  Renaming of conf file fails

Status in fonts-beng-extra package in Ubuntu:
  Fix Released
Status in fonts-deva-extra package in Ubuntu:
  Fix Released
Status in fonts-gujr-extra package in Ubuntu:
  Fix Released
Status in fonts-guru-extra package in Ubuntu:
  Fix Released
Status in fonts-orya-extra package in Ubuntu:
  Fix Released
Status in fonts-telu-extra package in Ubuntu:
  In Progress
Status in fonts-beng-extra source package in Bionic:
  Fix Released
Status in fonts-deva-extra source package in Bionic:
  Fix Released
Status in fonts-gujr-extra source package in Bionic:
  Fix Released
Status in fonts-guru-extra source package in Bionic:
  Fix Released
Status in fonts-orya-extra source package in Bionic:
  Fix Released
Status in fonts-telu-extra source package in Bionic:
  In Progress
Status in fonts-beng-extra package in Debian:
  New
Status in fonts-deva-extra package in Debian:
  New
Status in fonts-gujr-extra package in Debian:
  New
Status in fonts-guru-extra package in Debian:
  New
Status in fonts-orya-extra package in Debian:
  New

Bug description:
  [Impact]
  The fix of  wasn't accomplished properly. 
Renamings of conf files weren't addressed in maintainer scripts, upgrades from 
previous versions fail in this respect, and the package system generates 
warning messages.

  The problem has been reported in Debian, and the purpose of this bug
  report is to keep track of the progress.

  [Justification]
  This config file is broken in xenial and will still be broken on upgrade to 
bionic, which means the fonts in question will not be available to the system 
as intended if the user has upgraded.

  [Test case]
  For each of
  - fonts-beng-extra
  - fonts-deva-extra
  - fonts-gujr-extra
  - fonts-guru-extra
  - fonts-orya-extra
  - fonts-telu-extra:

  * Purge the package if installed and clean up possible leftovers
    due to the issue.

  * Install the Xenial version of the package and find that the symlink
    in /etc/fonts/conf.d incorrectly points to a directory.

  * Install the version in bionic-release and find that the attempt
    to fix the issue fails

  * Install the version in bionic-proposed and find that it fixes the
    issue and that the symlink now correctly points to the conf file.

  [Regression potential]
  Because this modifies maintainer scripts there is possibility of introducing 
a regression that will cause the package to fail to unpack.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1829400] Re: [Intel Core 2 Duo T7250] screen loop after suspension. Kernel 4.15 fails but 4.4.0 works.

Thanks for the bug report.

Please try to find the two closest kernel versions where one works and
one doesn't. You can download them from:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

** Summary changed:

- screen loop after suspension
+ [Intel Core 2 Duo T7250] screen loop after suspension.  Kernel 4.15 fails but 
4.4.0 works.

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

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

Title:
  [Intel Core 2 Duo T7250] screen loop after suspension.  Kernel 4.15
  fails but 4.4.0 works.

Status in linux package in Ubuntu:
  New

Bug description:

  Hello,
  I have a DELL PA-10 wtih GM965 intel graphic card. It couldn't boot with 4.15 
kernel and I have to use 4.4.0. I'm using the default driver, I didn't find an 
other.

  The computer boot faster aplying this fix but I continue to have a problem 
with the suspension. After after a suspension the screen blink between two kind 
of blank screen and never start.
  Is there a solution for that?
  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  Uname: Linux 4.4.0-146-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 16 17:03:54 2019
  DistUpgraded: 2019-04-27 17:06:11,246 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Latitude D630 [1028:01f9]
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f9]
  InstallationDate: Installed on 2016-06-18 (1062 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-146-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2019-04-27 (18 days ago)
  dmi.bios.date: 11/24/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1829430] Re: [nouveau] Xorg freeze

Thanks for the bug report.

1. If you have any gnome-shell extensions (other than the default Ubuntu
ones) then please uninstall them and retest. We find a large number of
bugs are caused by Gnome extensions.

2. Your kernel log mentions a few errors from the nouveau kernel driver:

[  274.310794] nouveau :01:00.0: bus: MMIO read of  FAULT at 619444 
[ IBUS ]
[  274.959650] nouveau :01:00.0: bus: MMIO read of  FAULT at 619444 
[ IBUS ]
[  294.627149] nouveau :01:00.0: bus: MMIO read of  FAULT at 619444 
[ IBUS ]
[  305.108717] nouveau :01:00.0: bus: MMIO read of  FAULT at 619444 
[ IBUS ]

but we can't know for sure if those are related to what you see.

Please try installing the proprietary Nvidia driver instead, as it
usually provides better stability:

  sudo apt install nvidia-driver-418

I am confident one of those two suggestions will solve the problem.
Please tell us which (if any) works.


** Summary changed:

- Xorg freeze
+ [nouveau] Xorg freeze

** Tags added: nouveau

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

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

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

Title:
  [nouveau] Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Every time i press the "windows" key which is by default mapped to
  "launch gnome search" the search launches but i cannot close it. The
  Escape key doesn't work at all and as far as i know the only solution
  to this problem is to log out and login again. This didnt occur when I
  was using 18.10 but after the upgrade to 19.04 this is indeed a
  problem. I'm aware that this issue might have something to so with the
  graphics drivers.

  root@aeshatter-XPS-15-9550:/home/aeshatter# lshw -c video
*-display 
 description: 3D controller
 product: GM107M [GeForce GTX 960M]
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:01:00.0
 version: a2
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom
 configuration: driver=nouveau latency=0
 resources: irq:126 memory:dc00-dcff memory:b000-bfff 
memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07
*-display
 description: VGA compatible controller
 product: HD Graphics 530
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:127 memory:db00-dbff memory:7000-7fff 
ioport:f000(size=64) memory:c-d

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 16 22:00:45 2019
  DistUpgraded: 2019-05-06 07:50:18,514 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell XPS 15 9550 [1028:06e4]
 Subsystem: Dell XPS 15 9550 [1028:06e4]
  InstallationDate: Installed on 2016-06-07 (1073 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=a31f340c-9c8b-441e-a80e-2684dd9d9ae9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to disco on 2019-05-06 (10 days ago)
  dmi.bios.date: 10/11/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd10/11/2018:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550

[Desktop-packages] [Bug 1828116] Re: Password works uppercase and lowercase

2019-05-16 Thread Seth Arnold

It's almost certainly unrelated to your report, but check out these
errors in your logs:

May 16 08:16:11 hostname /usr/lib/gdm3/gdm-x-session[1820]: 
/usr/bin/prime-supported: 38: /usr/bin/prime-supported: cannot create 
/var/log/prime-supported.log: Permission denied
May 16 08:16:11 hostname /usr/lib/gdm3/gdm-x-session[1820]: 
/sbin/prime-offload: 30: /sbin/prime-offload: cannot create 
/var/log/prime-offload.log: Permission denied

These may be indicative of further problems elsewhere in your video
drivers.

Thanks

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

Title:
  Password works uppercase and lowercase

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

Bug description:
  When I log in on the console, I can type my password either uppercase
  or lowercase. I can log in regardless.

  $ uname -a
  4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  Ubuntu 18.04 patched as of today.

  $ sudo cat /etc/shadow | grep $USER
  ...:$6$...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-06 (94 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1829448] [NEW] desktop icons vanish with libre office writer file save

2019-05-16 Thread peterzay

Public bug reported:

Procedure to reproduce this bug:
- odt file resides on desktop
- double click to edit
- save
- many but not all desktop icons vanish
- click X to close writer window
- vanished desktop icons reappear

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libreoffice-core 1:6.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 16 20:05:52 2019
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2019-04-18 (28 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  desktop icons vanish with libre office writer file save

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Procedure to reproduce this bug:
  - odt file resides on desktop
  - double click to edit
  - save
  - many but not all desktop icons vanish
  - click X to close writer window
  - vanished desktop icons reappear

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice-core 1:6.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 16 20:05:52 2019
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2019-04-18 (28 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1829156] Re: Chrome multimedia keys doesn't work after screen lock 18.04

Button on the keyboard? Also you wrote "other programs like vlc & stock
video player." did that miss some words, or could you explain what it
means?

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

Title:
  Chrome multimedia keys doesn't work after screen lock 18.04

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

Bug description:
  So chrome introduced this multimedia key support and it works pretty
  well. I use google play music to listen to music and the play/pause
  multimedia keys are useful. but at an event where the screen is locked
  and i log back in, the multimedia keys doesn't work. i have to restart
  chrome to make it work again.

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

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

[Desktop-packages] [Bug 1828116] Re: Password works uppercase and lowercase

2019-05-16 Thread G S

If it's too short, I'll paste the full log.

> Does it happen with simple password? like if you "sudo passwd "
and set "one" does it log in using "ONE"?

Yes

> "dpkg -l | grep pam"

ii  libpam-cap:amd64   1:2.25-1.2   
amd64POSIX 1003.1e capabilities (PAM module)
ii  libpam-gnome-keyring:amd64 3.28.0.2-1ubuntu1.18.04.1
amd64PAM module to unlock the GNOME keyring upon login
ii  libpam-modules:amd64   1.1.8-3.6ubuntu2.18.04.1 
amd64Pluggable Authentication Modules for PAM
ii  libpam-modules-bin 1.1.8-3.6ubuntu2.18.04.1 
amd64Pluggable Authentication Modules for PAM - helper 
binaries
ii  libpam-runtime 1.1.8-3.6ubuntu2.18.04.1 
all  Runtime support for the PAM library
ii  libpam-systemd:amd64   237-3ubuntu10.21 
amd64system and service manager - PAM module
ii  libpam0g:amd64 1.1.8-3.6ubuntu2.18.04.1 
amd64Pluggable Authentication Modules library
ii  thunderbird1:60.6.1+build2-0ubuntu0.18.04.1 
amd64Email, RSS and newsgroup client with integrated spam 
filter

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

Title:
  Password works uppercase and lowercase

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

Bug description:
  When I log in on the console, I can type my password either uppercase
  or lowercase. I can log in regardless.

  $ uname -a
  4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  Ubuntu 18.04 patched as of today.

  $ sudo cat /etc/shadow | grep $USER
  ...:$6$...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-06 (94 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1828116] Re: Password works uppercase and lowercase

2019-05-16 Thread G S

** Attachment added: "journalctl"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+attachment/5264391/+files/journal

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

Title:
  Password works uppercase and lowercase

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

Bug description:
  When I log in on the console, I can type my password either uppercase
  or lowercase. I can log in regardless.

  $ uname -a
  4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  Ubuntu 18.04 patched as of today.

  $ sudo cat /etc/shadow | grep $USER
  ...:$6$...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-06 (94 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1829364] Re: Will not play sound via HDMI unless you run pavucontrol first

2019-05-16 Thread Jarno Suni

When pavucontrol is not running, it depends on sample rate of playback,
whether or not the sound is audible:

$ speaker-test -r 48000
not audible

$ speaker-test -r 47999
audible

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

Title:
  Will not play sound via HDMI unless you run pavucontrol first

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Does not play sound via sink output:iec958-stereo unless I start
  pavucontrol before running the player such as paplay. Player does not
  show any error and takes its time to play, but there is no sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1829430] [NEW] Xorg freeze

2019-05-16 Thread Gabriel Holmlund

Public bug reported:

Every time i press the "windows" key which is by default mapped to
"launch gnome search" the search launches but i cannot close it. The
Escape key doesn't work at all and as far as i know the only solution to
this problem is to log out and login again. This didnt occur when I was
using 18.10 but after the upgrade to 19.04 this is indeed a problem. I'm
aware that this issue might have something to so with the graphics
drivers.

root@aeshatter-XPS-15-9550:/home/aeshatter# lshw -c video
  *-display 
   description: 3D controller
   product: GM107M [GeForce GTX 960M]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a2
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list rom
   configuration: driver=nouveau latency=0
   resources: irq:126 memory:dc00-dcff memory:b000-bfff 
memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07
  *-display
   description: VGA compatible controller
   product: HD Graphics 530
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 06
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:127 memory:db00-dbff memory:7000-7fff 
ioport:f000(size=64) memory:c-d

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 16 22:00:45 2019
DistUpgraded: 2019-05-06 07:50:18,514 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
 virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Today
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Dell XPS 15 9550 [1028:06e4]
   Subsystem: Dell XPS 15 9550 [1028:06e4]
InstallationDate: Installed on 2016-06-07 (1073 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. XPS 15 9550
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=a31f340c-9c8b-441e-a80e-2684dd9d9ae9 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to disco on 2019-05-06 (10 days ago)
dmi.bios.date: 10/11/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.0
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd10/11/2018:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9550
dmi.product.sku: 06E4
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue May 29 09:51:38 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug disco freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Every time i press the "windows" key which is by default mapped to
  "launch gnome search" the search launches but i cannot close it. The
  Escape key doesn't work at all and as far as i know the only solution
  to this problem is to log out and login again. This didnt occur when I
  was using 18.10 but after the upgrade to 19.04 this is indeed a
  problem. I'm

[Desktop-packages] [Bug 1828811]

2019-05-16 Thread Libreoffice-commits

Michael Stahl committed a patch related to this issue.
It has been pushed to "libreoffice-6-2-4":

https://git.libreoffice.org/core/+/3a93e29c601078970fb6b2b27d3d9865a93ad4ad%5E%21

tdf#125261 sw_redlinehide: fix inf. loop in SwAutoFormat::AutoCorrect()

It will be available in 6.2.4.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [Upstream] Applying autocorrect to text with URLs causes Writer to
  hang

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  When attempting to apply autocorrect to text that contains URLs to
  convert to hyperlinks (https://ask.libreoffice.org/en/question/6393
  /how-may-i-do-writer-recognize-hyperlinks-automatically/) causes
  Writer to stop responding requiring a force quit.

  Version 6.2.2.2

  Severity: Normal.

  Reproducible:
  Always

  Steps to reproduce:
  Open a new Writer document.
  Turn URL recognition on - Tools | Auto Correct | Auto correct options | 
Options tab
  Insert text containing URLs (see below)
  Set paragraph style to default
  Apply auto correct - Tools | Auto Correct | Apply

  Actual result:
  Libre Office hangs

  Expected result:
  Auto correct applied, text urls converted to hyperlinks

  Bug is evident in both deb and snap versions of LO, but not in earlier
  5.x or 6.x series.

  Sample test with URLs:
  This webpage is and example of a url that should be able to be converted to a 
hyperlink . As is this page  
and this page .

  These pages should also be able to be converted using the method
  linked to above ,
  .

  A typical use for a page like this would be a bibliography or
  reference list .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 20:38:07 2019
  InstallationDate: Installed on 2019-05-11 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1828811/+subscriptions

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

[Desktop-packages] [Bug 1828811]

2019-05-16 Thread Libreoffice-commits

Zdeněk Crhonek committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/+/9551a1ed54fc8131b52ee58114398924196313fd%5E%21

uitest for bug tdf#125261

It will be available in 6.3.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [Upstream] Applying autocorrect to text with URLs causes Writer to
  hang

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  When attempting to apply autocorrect to text that contains URLs to
  convert to hyperlinks (https://ask.libreoffice.org/en/question/6393
  /how-may-i-do-writer-recognize-hyperlinks-automatically/) causes
  Writer to stop responding requiring a force quit.

  Version 6.2.2.2

  Severity: Normal.

  Reproducible:
  Always

  Steps to reproduce:
  Open a new Writer document.
  Turn URL recognition on - Tools | Auto Correct | Auto correct options | 
Options tab
  Insert text containing URLs (see below)
  Set paragraph style to default
  Apply auto correct - Tools | Auto Correct | Apply

  Actual result:
  Libre Office hangs

  Expected result:
  Auto correct applied, text urls converted to hyperlinks

  Bug is evident in both deb and snap versions of LO, but not in earlier
  5.x or 6.x series.

  Sample test with URLs:
  This webpage is and example of a url that should be able to be converted to a 
hyperlink . As is this page  
and this page .

  These pages should also be able to be converted using the method
  linked to above ,
  .

  A typical use for a page like this would be a bibliography or
  reference list .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 20:38:07 2019
  InstallationDate: Installed on 2019-05-11 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1828811/+subscriptions

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

[Desktop-packages] [Bug 1829156] Re: Chrome multimedia keys doesn't work after screen lock 18.04

2019-05-16 Thread Basith Kunimal

The problem is with chrome only, other programs like vlc & stock video
player. Desktop environment is Gnome. It's a stock ubuntu 18.04 default
gnome version.

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

Title:
  Chrome multimedia keys doesn't work after screen lock 18.04

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

Bug description:
  So chrome introduced this multimedia key support and it works pretty
  well. I use google play music to listen to music and the play/pause
  multimedia keys are useful. but at an event where the screen is locked
  and i log back in, the multimedia keys doesn't work. i have to restart
  chrome to make it work again.

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

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

[Desktop-packages] [Bug 1829156] Re: Chrome multimedia keys doesn't work after screen lock 18.04

2019-05-16 Thread Basith Kunimal

I meant the hardware play/pause button when i said multimedia keys.

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

Title:
  Chrome multimedia keys doesn't work after screen lock 18.04

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

Bug description:
  So chrome introduced this multimedia key support and it works pretty
  well. I use google play music to listen to music and the play/pause
  multimedia keys are useful. but at an event where the screen is locked
  and i log back in, the multimedia keys doesn't work. i have to restart
  chrome to make it work again.

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

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

[Desktop-packages] [Bug 1829377] Re: Remove this package

** Changed in: vte (Debian)
   Status: Unknown => New

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

Title:
  Remove this package

Status in vte package in Ubuntu:
  New
Status in vte package in Debian:
  New

Bug description:
  Please remove the ancient GTK2-based vte aka. libvte9{,-common} from
  Eoan.

  Upstream version has been unmaintained for about 8 years, development
  continued in the GTK3 branch (vte2.91 aka. libvte-2.91-0).

  Geany is the only package referring to it, and it also does
  incorrectly since it already uses GTK3, see bug 1829375.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libvte9 1:0.28.2-6
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 16 13:41:04 2019
  InstallationDate: Installed on 2016-11-09 (917 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: vte
  UpgradeStatus: Upgraded to disco on 2019-04-10 (35 days ago)

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

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

[Desktop-packages] [Bug 1829053] Re: driver won't install of intel

2019-05-16 Thread Timo Aaltonen

you have the hwe stack installed, so install xserver-xorg-video-intel-
hwe-16.04

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  driver won't install of intel

Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  [sudo] password for sheharyar: 
  Sorry, try again.
  [sudo] password for sheharyar: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-20
  Depends: xserver-xorg-core (>= 2:1.17.99.902)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 14 22:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:143a]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Park [Mobility Radeon HD 
5430/5450/5470] [103c:143a]
  InstallationDate: Installed on 2019-04-13 (31 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP G72 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=51795b73-d359-48d5-89d1-7c6297784ee8 ro nomodeset quiet splash 
vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.48
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 143A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 60.50
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.48:bd11/09/2011:svnHewlett-Packard:pnHPG72NotebookPC:pvr058E11252710001620100:rvnHewlett-Packard:rn143A:rvr60.50:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP G72 Notebook PC
  dmi.product.version: 058E11252710001620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed May 15 03:54:01 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1829053/+subscriptions

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

[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

Upgraded libreoffice from 1:6.1.5-0ubuntu0.18.10.1 to
1:6.1.6-0ubuntu0.18.10.2 from cosmic-proposed in a clean and up-to-date
cosmic amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

** 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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1820062

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

  [Impact]

   * This effects all libreoffice-gtk3 users wishing to embed videos
  into an Impress slide.

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

  [Test Case]

   1. Insert a video into an Impress slide
   2. Play the video
   3. The video should play within the slide (not fullscreen like this: 
https://youtu.be/77E6IzVJ5jA)

  [Regression Potential]

   * The fix is one line in the control file so potential for regression
  is low.

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

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

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

[Desktop-packages] [Bug 1827451] Re: Japanese new era "Reiwa(令和)" support

Upgraded libreoffice from 1:6.1.5-0ubuntu0.18.10.1 to
1:6.1.6-0ubuntu0.18.10.2 from cosmic-proposed in a clean and up-to-date
cosmic amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

** Description changed:

  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  
  [Impact]
  
-  * This effects all users who use the Japanese era date format in
+  * This effects all users who use the Japanese era date format in
  LibreOffice.
  
-  * The fix is currently in LibreOffice 6.2.3 on eoan.
+  * The fix is currently in LibreOffice 6.2.3 on eoan.
  
  [Test Case]
  
-  1. Start Calc
-  2. Put "01/05/2019" into a cell
-  3. Right-click on the cell and select "Format Cells"
-  4. Set “Language" to "Japanese"
-  5. Set “Format" to "H11.12.31"
-  6. Cell should show "R1.05.01" (not "N1.05.01”)
+  1. Start Calc
+  2. Put "01/05/2019" into a cell
+  3. Right-click on the cell and select "Format Cells"
+  4. Set “Language" to "Japanese"
+  5. Set “Format" to "H11.12.31"
+  6. Cell should show "R1.05.01" (not "N1.05.01”)
+  7. Set “Format" to "平成11年12月31日"
+  8. Cell should show "令和1年5月1日" (not "平成31年5月1日")
  
  [Regression Potential]
  
-  * The fix is minor so potential for regression is low.
+  * The fix is minor so potential for regression is low.
  
   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

** 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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1827451

Title:
  Japanese new era "Reiwa(令和)" support

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Xenial:
  In Progress
Status in libreoffice source package in Bionic:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This effects all users who use the Japanese era date format in
  LibreOffice.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Start Calc
   2. Put "01/05/2019" into a cell
   3. Right-click on the cell and select "Format Cells"
   4. Set “Language" to "Japanese"
   5. Set “Format" to "H11.12.31"
   6. Cell should show "R1.05.01" (not "N1.05.01”)
   7. Set “Format" to "平成11年12月31日"
   8. Cell should show "令和1年5月1日" (not "平成31年5月1日")

  [Regression Potential]

   * The fix is minor so potential for regression is low.

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

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

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

[Desktop-packages] [Bug 1828210] Re: [SRU] libreoffice 6.1.6 for cosmic

Upgraded libreoffice from 1:6.1.5-0ubuntu0.18.10.1 to
1:6.1.6-0ubuntu0.18.10.2 from cosmic-proposed in a clean and up-to-date
cosmic amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

** 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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1828210

Title:
  [SRU] libreoffice 6.1.6 for cosmic

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

Bug description:
  [Impact]

   * LibreOffice 6.1.6 is the sixth bugfix release of the still 6.1 line. 
Version 6.1.5 is currently in cosmic.
     For a list of fixed bugs compared to 6.1.5 see the list of bugs fixed in 
the three release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.6/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.6/RC3#List_of_fixed_bugs
     (that's a total of 57 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 57 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1828683] Re: package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to install/upgrade: forsøger at overskrive '/usr/lib/libreoffice/program/libOGLTranslo.so', som også er

Upgraded libreoffice from 1:6.1.5-0ubuntu0.18.10.1 to
1:6.1.6-0ubuntu0.18.10.2 from cosmic-proposed in a clean and up-to-date
cosmic amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

** 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 libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1828683

Title:
  package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to
  install/upgrade: forsøger at overskrive
  '/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken
  libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1

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

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-19.20-generic 4.18.20
  Uname: Linux 4.18.0-19-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Sat May 11 11:42:06 2019
  ErrorMessage: forsøger at overskrive 
'/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken 
libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1
  InstallationDate: Installed on 2018-06-14 (331 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180613)
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: libreoffice
  Title: package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to 
install/upgrade: forsøger at overskrive 
'/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken 
libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This affects all Cosmic users attempting to upgrade LibreOffice to
  6.1.6 from any previous version.

  [Test Case]

   1. Install LibreOffice 6.1.5 on Cosmic
   2. Enable pre-released updates (cosmic-proposed)
   3. apt update && apt upgrade

  [Regression Potential]

   * This issue and its associated fix are isolated to just this upgrade
  path, so potential for further regression is low.

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

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

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

Please note that the killer wireless card is replaced by intel when
running apport-collect.


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

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] nmcli-con.txt

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264347/+files/nmcli-con.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1827879/+attachment/5264344/+files/RfKill.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1827879/+attachment/5264345/+files/UdevDb.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264346/+files/WifiSyslog.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] nmcli-dev.txt

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264348/+files/nmcli-dev.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264342/+files/ProcModules.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264343/+files/PulseList.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264340/+files/ProcEnviron.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264328/+files/CurrentDmesg.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264331/+files/IwConfig.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1827879/+attachment/5264330/+files/IpAddr.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1827879/+attachment/5264327/+files/CRDA.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264329/+files/Dependencies.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264341/+files/ProcInterrupts.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264339/+files/ProcCpuinfoMinimal.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264338/+files/PciNetwork.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] NetworkManager.conf.txt

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264337/+files/NetworkManager.conf.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] NetDevice.wlp3s0.txt

apport information

** Attachment added: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264336/+files/NetDevice.wlp3s0.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] NetDevice.lo.txt

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264335/+files/NetDevice.lo.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1827879/+attachment/5264332/+files/Lspci.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1827879/+attachment/5264333/+files/Lsusb.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1827879] NetDevice.enp2s0.txt

apport information

** Attachment added: "NetDevice.enp2s0.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264334/+files/NetDevice.enp2s0.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

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

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

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

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

apport information

** Tags added: apport-collected

** Description changed:

  Problem: 
  Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's 
stay on and FAN keeps running. Strangely this does not happen in Fedora 29 
(Kernel 4.18 & same board firmware)
  
  System:
  Ubuntu 19.04 
  Kernel 5.0.0-13-generic
  Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1)
  Wireless info:
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 20
 serial: 40:b8:9a:ca:2b:99
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 
ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:32 memory:f680-f69f
  
  
  My attempts:
  1. Tried other kernels:
  5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114
  
  2. Tried several distro's based on ubuntu -> all have the same issue
  
  3. Checked firmware from Fedora 29 (md5sum was equal) and updated
  firmware (not available, using latest)
  
  4. Created systemd scripts for disabling & enabling the driver, this causes 
the same crashes in /var/log/syslog
  See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11
  
  5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone,
  standby works perfectly
  
  Of course i want to be able to use the 1525, so please help me solve the 
issue.
  Happy to perform additional debugging if required.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  sander 1527 F pulseaudio
+  /dev/snd/controlC0:  sander 1527 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 19.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ IpRoute:
+  default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 
+  169.254.0.0/16 dev wlp3s0 scope link metric 1000 
+  192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 
600
+ MachineType: Alienware Alienware 17 R2
+ NetworkManager.state:
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: network-manager 1.16.0-0ubuntu2
+ PackageArchitecture: amd64
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-15-generic N/A
+  linux-backports-modules-5.0.0-15-generic  N/A
+  linux-firmware1.178.1
+ Tags:  disco
+ Uname: Linux 5.0.0-15-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/31/2017
+ dmi.bios.vendor: Alienware
+ dmi.bios.version: A08
+ dmi.board.name: Alienware 17 R2
+ dmi.board.vendor: Alienware
+ dmi.board.version: A00
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Alienware
+ dmi.chassis.version: A08
+ dmi.modalias: 
dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08:
+ dmi.product.family: Alienware 17 R2
+ dmi.product.name: Alienware 17 R2
+ dmi.product.sku: Alienware 15
+ dmi.product.version: A08
+ dmi.sys.vendor: Alienware
+ nmcli-nm:
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.16.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1827879/+attachment/5264326/+files/AlsaInfo.txt

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

  System:
  Ubuntu 19.04 
  Kernel 5.0.0-13-generic
  Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1)
  Wireless info:
 description: Wireless interface
 product: QCA6174

[Desktop-packages] [Bug 1829417] [NEW] When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a lot

2019-05-16 Thread El jinete sin cabeza

Public bug reported:

[Impact]
'tracker-miner-f' works a lot when I download with chrome

[Fix]
tracker-miner-f work with much less intencity

[Test Case]
1. Open Chrome
2. Download 
http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso
3. Open gnome-terminal and run top
4. While the download of OI-hipster-gui-20190511.iso occurs, 'tracker-miner-f' 
works constantly and intentionally

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: tracker 2.1.8-2
Uname: Linux 5.1.2-050102-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 16 12:47:13 2019
InstallationDate: Installed on 2018-12-02 (164 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: tracker
UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago)

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


** Tags: amd64 apport-bug eoan wayland-session

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

Title:
  When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a
  lot

Status in tracker package in Ubuntu:
  New

Bug description:
  [Impact]
  'tracker-miner-f' works a lot when I download with chrome

  [Fix]
  tracker-miner-f work with much less intencity

  [Test Case]
  1. Open Chrome
  2. Download 
http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso
  3. Open gnome-terminal and run top
  4. While the download of OI-hipster-gui-20190511.iso occurs, 
'tracker-miner-f' works constantly and intentionally

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.1.2-050102-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 16 12:47:13 2019
  InstallationDate: Installed on 2018-12-02 (164 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago)

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

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

[Desktop-packages] [Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide

2019-05-16 Thread Gunnar Hjalmarsson

On 2019-05-16 17:48, Sebastien Bacher wrote:
> Using disco the videos play fine here

Same here nowadays - but only sometimes. And my disco is anything but a
clean install; I use NVIDIA for instance.

So I tried NVIDIA on my eoan install - nope. (It does obviously not show
the same error messages as I reported in comment #6, but it rather
hangs.)

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

Title:
  Garbage occurred when Playing the video in the Ubuntu Desktop Guide

Status in Yelp:
  Confirmed
Status in gnome-getting-started-docs package in Ubuntu:
  Confirmed

Bug description:
  Garbage occurred when Playing the video in the Ubuntu Desktop Guide.

  Reproduce step
  1. Ubuntu 18.04.1.
  2. ubuntu-docs 18.04.4
  3. Playing the video(Launch applications) from Help-->Getting started with 
GNOME.
  4. Garbage occurred after the video repeat about 3 times==> issue.

  Expected results: The Video can be played normally no-matter how many
  times.

  Actual results: Garbage occurred after the video repeat about 3 times

  Note:
  1. the video will show blank but still have the voice after the issue finish.
  2. Right click the mouse and choice "save video as", this application will 
crashed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-docs 18.04.4
  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.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 23 16:46:00 2018
  InstallationDate: Installed on 2018-04-30 (206 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1829377] Re: Remove this package

2019-05-16 Thread Juhani Numminen

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

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

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

Title:
  Remove this package

Status in vte package in Ubuntu:
  New
Status in vte package in Debian:
  Unknown

Bug description:
  Please remove the ancient GTK2-based vte aka. libvte9{,-common} from
  Eoan.

  Upstream version has been unmaintained for about 8 years, development
  continued in the GTK3 branch (vte2.91 aka. libvte-2.91-0).

  Geany is the only package referring to it, and it also does
  incorrectly since it already uses GTK3, see bug 1829375.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libvte9 1:0.28.2-6
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 16 13:41:04 2019
  InstallationDate: Installed on 2016-11-09 (917 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: vte
  UpgradeStatus: Upgraded to disco on 2019-04-10 (35 days ago)

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

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

[Desktop-packages] [Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide

Using disco the videos play fine here so it's not impacting every config

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

Title:
  Garbage occurred when Playing the video in the Ubuntu Desktop Guide

Status in Yelp:
  Confirmed
Status in gnome-getting-started-docs package in Ubuntu:
  Confirmed

Bug description:
  Garbage occurred when Playing the video in the Ubuntu Desktop Guide.

  Reproduce step
  1. Ubuntu 18.04.1.
  2. ubuntu-docs 18.04.4
  3. Playing the video(Launch applications) from Help-->Getting started with 
GNOME.
  4. Garbage occurred after the video repeat about 3 times==> issue.

  Expected results: The Video can be played normally no-matter how many
  times.

  Actual results: Garbage occurred after the video repeat about 3 times

  Note:
  1. the video will show blank but still have the voice after the issue finish.
  2. Right click the mouse and choice "save video as", this application will 
crashed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-docs 18.04.4
  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.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 23 16:46:00 2018
  InstallationDate: Installed on 2018-04-30 (206 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-docs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1827751] Re: Lock screen displayed after screen blanking even when lock screen disabled

What do you call "lock screen"? Do you have to enter your password or do
you only mean the "banner" screen?

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

Title:
  Lock screen displayed after screen blanking even when lock screen
  disabled

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 Gnome

  Screen lock is set to off in Settings->Privacy.  Blank Screen is set
  to 10 minutes in Settings->Power. On returning from Screen Blank, Lock
  Screen is present.  Does not occur after manual suspend (ie closing
  laptop lid) and resuming.

  In dconf I have set org/gnome/desktop/lockdown/disable-lock-screen to true.
  org/gnome/desktop/screensaver/lock-enabled is set to false
  org/gnome/desktop/screensaver/ubuntu-lock-on-suspend is set to false

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  4 19:25:36 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-04-22 (12 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
[modified]
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2019-04-24T23:58:15.215728

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

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

[Desktop-packages] [Bug 1827879] Missing required logs.

2019-05-16 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1827879

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: disco

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

  Of course i want to be able to use the 1525, so please help me solve the 
issue.
  Happy to perform additional debugging if required.

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

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

[Desktop-packages] [Bug 1829400] [NEW] screen loop after suspension

2019-05-16 Thread Thierry Gonzalez

Public bug reported:


Hello,
I have a DELL PA-10 wtih GM965 intel graphic card. It couldn't boot with 4.15 
kernel and I have to use 4.4.0. I'm using the default driver, I didn't find an 
other.

The computer boot faster aplying this fix but I continue to have a problem with 
the suspension. After after a suspension the screen blink between two kind of 
blank screen and never start.
Is there a solution for that?
Thanks,

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
Uname: Linux 4.4.0-146-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 16 17:03:54 2019
DistUpgraded: 2019-04-27 17:06:11,246 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Latitude D630 [1028:01f9]
   Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f9]
InstallationDate: Installed on 2016-06-18 (1062 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Dell Inc. Latitude D630
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-146-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2019-04-27 (18 days ago)
dmi.bios.date: 11/24/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0KU184
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D630
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: apport-bug bionic i386 ubuntu

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

Title:
  screen loop after suspension

Status in xorg package in Ubuntu:
  New

Bug description:

  Hello,
  I have a DELL PA-10 wtih GM965 intel graphic card. It couldn't boot with 4.15 
kernel and I have to use 4.4.0. I'm using the default driver, I didn't find an 
other.

  The computer boot faster aplying this fix but I continue to have a problem 
with the suspension. After after a suspension the screen blink between two kind 
of blank screen and never start.
  Is there a solution for that?
  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  Uname: Linux 4.4.0-146-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 16 17:03:54 2019
  DistUpgraded: 2019-04-27 17:06:11,246 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Latitude D630 [1028:01f9]
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f9]
  InstallationDate: Installed on 2016-06-18 (1062 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-146-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2019-04-27 (18 days ago)

[Desktop-packages] [Bug 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning

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

** Changed in: firefox
   Importance: Wishlist => Medium

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

Title:
  Location requested by websites should be able to use GPS/mobile
  positioning

Status in Chromium Browser:
  Fix Committed
Status in Mozilla Firefox:
  Unknown
Status in GeoClue:
  Won't Fix
Status in WebKit:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-providers package in Ubuntu:
  Invalid

Bug description:
  It would be nice if location requested by websites could use location
  found from GPS or GSM/CDMA positioning.

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

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

[Desktop-packages] [Bug 1808833] Re: /usr/lib/geoclue-2.0/demos/where-am-i:* stack smashing detected *: terminated

The issue has not been reported with > 2.4.7

** Changed in: geoclue-2.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: geoclue-2.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  /usr/lib/geoclue-2.0/demos/where-am-i:*** stack smashing detected ***:
   terminated

Status in geoclue-2.0 package in Ubuntu:
  Fix Released

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

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

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

[Desktop-packages] [Bug 1799339] Re: GeoClue times out on start

The new version with the change landed in Ubuntu since

** Changed in: geoclue-2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GeoClue times out on start

Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-2.0 source package in Cosmic:
  Won't Fix
Status in geoclue-2.0 package in Debian:
  Fix Released

Bug description:
  * Impact

  On some configs registration to the geoclue service might fail because
  the agent is started too late/after the registration timeout

  * Test case

  log into an Ubuntu/GNOME session and check that the geolocation feature is 
working (used to adjust the timezone for example)
  - log into your Ubuntu/GNOME session
  - go to gnome-control-center, enable the geolocation and automatic timezone 
adjustement options
  - reboot to gdm (without login in)
  - go to a vt
  - change the timezone to be not matching the actual location
  - go back to gdm and log in

  -> verify that the timezone get adjusted automatically to match your
  real location one

  or from the original report
  - install xubuntu
  - install redshift and start it/configure it to change your screen 
profile/colors at night
  - log into your xfce session at a time configured to color the screen red

  -> the screen color should change according to the calibration

  * Regression potential

  The change is only to increase a timeout delay

  ---

  Due to an upstream bug
  (https://gitlab.freedesktop.org/geoclue/geoclue/issues/84) GeoClue
  times out upon startup and certain applications (such as Redshift) do
  not function as intended. This has already been fixed upstream
  (version 2.5.0) and that version is available in Debian. Please pull
  the latest Debian version to fix this bug.

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

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

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

2019-05-16 Thread Kai-Heng Feng

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

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

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

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

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

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

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

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

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

  Of course i want to be able to use the 1525, so please help me solve the 
issue.
  Happy to perform additional debugging if required.

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

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

[Desktop-packages] [Bug 1100326]

2019-05-16 Thread Gkeeley

Marking inactive due to the length of inactivity here, feel free to re-
open if you wish this to remain active.

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

Title:
  Location requested by websites should be able to use GPS/mobile
  positioning

Status in Chromium Browser:
  Fix Committed
Status in Mozilla Firefox:
  Unknown
Status in GeoClue:
  Won't Fix
Status in WebKit:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-providers package in Ubuntu:
  Invalid

Bug description:
  It would be nice if location requested by websites could use location
  found from GPS or GSM/CDMA positioning.

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

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

[Desktop-packages] [Bug 1100326]

2019-05-16 Thread Zeeshan Ali

FYI, it's now easier to interface with Geoclue2 if you don't mind a dep
on glib/gio:

http://zee-nix.blogspot.co.uk/2015/10/geoclue-convenience-library-just-got.html
http://www.freedesktop.org/software/geoclue/docs/libgeoclue/GClueSimple.html

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

Title:
  Location requested by websites should be able to use GPS/mobile
  positioning

Status in Chromium Browser:
  Fix Committed
Status in Mozilla Firefox:
  Unknown
Status in GeoClue:
  Won't Fix
Status in WebKit:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-providers package in Ubuntu:
  Invalid

Bug description:
  It would be nice if location requested by websites could use location
  found from GPS or GSM/CDMA positioning.

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

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

[Desktop-packages] [Bug 1465766] Re: low sound volume

2019-05-16 Thread Mathieu Desnoyers

I have a similar issue on Debian 9 (Stretch) on a Lenovo X1 Carbon 6th
Gen laptop.

DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET63W (1.38 ) 04/20/2019

The built-in speaker volume is limited to about 20% even if the volume
is set at 100%.

The sound card is a ALC285 handled by the snd_hda_intel driver.

On my kernel (4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2
(2019-05-13)), I managed to find this work-around which addresses the
low volume issue:

Edit /etc/modprobe.d/alsa-base.conf

add the following line:

options snd-hda-intel model=nofixup

After modprobe -r/modprobe of the snd_hda_intel module (or reboot), the
volume works fine.

Hopefully this can help others facing this open issue as well.

Here is the output of lspci -vvv for the sound card:

00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) (prog-if 80)
Subsystem: Lenovo Device 225c
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1465766

Title:
  low sound volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  this is a thinkpad x1 carbon 3rd gen running xubuntu 15.04

  sound volume is very low compared to windows (dual boot), even with
  alsa and pulseaudio controls set to 100% (or greater).

  this applies to all apps.

  i can get really loud sound with:
  pactl set-sink-volume 1 30
  but then it is very distorted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smwilson   1577 F pulseaudio
   /dev/snd/controlC0:  smwilson   1577 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 16 06:44:39 2015
  InstallationDate: Installed on 2015-06-04 (11 days ago)
  InstallationMedia: Xubuntu Core 15.04 - amd64 - 20150425
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Volume slider, or mixer problems
  Title: [20BSCTO1WW, Realtek ALC3232, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET25W (1.03 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1010349] Re: Evolution address book inaccessible without killing one time "e-addressbook-factory"

2019-05-16 Thread Raffi Khatchadourian

I am experiencing this on Evolution 3.30.1-1build1 and Ubuntu 18.10.

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

Title:
  Evolution address book inaccessible without killing one time "e
  -addressbook-factory"

Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  After a fresh boot of my system, Evolution is not able to access my
  work address book on LDAP and my personnal address book on Google.

  With Google address book I get the error "Cannot open book: Source
  already loaded!"

  After shutting down Evolution and killing by hand :
  /usr/lib/evolution/e-addressbook-factory. I relaunch Evolution and
  everything go right.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: evolution-data-server 3.2.3-0ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jun  8 09:07:18 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1827508] Re: LibreOffice Impress: presentation mode shows black screen instead of slides

Excellent. Thanks for the update!

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

Title:
  LibreOffice Impress: presentation mode shows black screen instead of
  slides

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  With a dual-screen setup (e.g., notebook monitor plus video projector
  on HDMI cable), when starting a presentation in LO Impress (Slide Show
  -> Start from first slide, or F5), the external monitor turns black
  with something that looks like scrollbars to the right and bottom,
  while the primary monitor only shows the slide editor instead of the
  presenter console.

  Steps to reproduce:
   - Install libreoffice 1:6.2.2-0ubuntu2 in Ubuntu 19.04.
   - Attach secondary monitor / projector.  Extend desktop to the right.
   - Start soffice, create new Impress presentation using an arbitrary template.
   - Press F5.

  Expected behavior:
   - LO Impress shows presenter console on primary and the first slide on 
secondary monitor.

  Actual behavior:
   - Slide editor on primary, black screen with scroll bars to the right and 
bottom on secondary monitor.

  Workaround:
   - Click around on the black area, the presentation (together with the 
presenter console) may show up at some point.
   - Or install LibreOffice 6.2.3.2 from libreoffice.org, works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice-impress 1:6.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  3 14:04:06 2019
  InstallationDate: Installed on 2016-11-26 (887 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1827508] Re: LibreOffice Impress: presentation mode shows black screen instead of slides

2019-05-16 Thread Horst Schirmeier

Yes, I don't have the issue with the newly released LO 6.2.3.2 in Disco
anymore.  Thanks!

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete => 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/1827508

Title:
  LibreOffice Impress: presentation mode shows black screen instead of
  slides

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  With a dual-screen setup (e.g., notebook monitor plus video projector
  on HDMI cable), when starting a presentation in LO Impress (Slide Show
  -> Start from first slide, or F5), the external monitor turns black
  with something that looks like scrollbars to the right and bottom,
  while the primary monitor only shows the slide editor instead of the
  presenter console.

  Steps to reproduce:
   - Install libreoffice 1:6.2.2-0ubuntu2 in Ubuntu 19.04.
   - Attach secondary monitor / projector.  Extend desktop to the right.
   - Start soffice, create new Impress presentation using an arbitrary template.
   - Press F5.

  Expected behavior:
   - LO Impress shows presenter console on primary and the first slide on 
secondary monitor.

  Actual behavior:
   - Slide editor on primary, black screen with scroll bars to the right and 
bottom on secondary monitor.

  Workaround:
   - Click around on the black area, the presentation (together with the 
presenter console) may show up at some point.
   - Or install LibreOffice 6.2.3.2 from libreoffice.org, works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice-impress 1:6.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  3 14:04:06 2019
  InstallationDate: Installed on 2016-11-26 (887 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

2019-05-16 Thread Mathieu Trudel-Lapierre

I don't think it's *-control-center.

At the time, that was filed there by pitti, who correctly pointed out
that something might need to depend on libnss-myhostname (from systemd)
for a fallback to resolving hostname via just /etc/hostname (since
/etc/hosts isn't changed). At this point though, it looks like this is
no longer required.

Now, AFAICT the desktop correctly calls to systemd via dbus to ask for
the change. I'll leave to you to make sure this is indeed the case
(since you had commented on the bug previously, and I can't see any
issues changing hostname as it is now, but maybe I'm not quite doing the
same tests you were).

unity-control-center is an obvious Won't Fix for Eoan or Disco, but I'll
let the Desktop Team decide whether this needs to be fixed in other
releases.

Finally, this is still assigned to systemd, low priority, because
hostnamed *doesn't* change /etc/hosts, and probably should (at the very
least for consistency, to avoid keeping a reference to an old name for
the system); but I didn't notice ill effects from not changing that
file. sudo certainly doesn't hang here trying to resolve the new or old
hostname.

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

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  New
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  New
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

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

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

2019-05-16 Thread Iain Lane

** Changed in: gst-libav1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-plugins-base1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-plugins-ugly1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-python1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-rtsp-server1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gstreamer-editing-services1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-libav1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-libav1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-plugins-base1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-plugins-base1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-plugins-good1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-plugins-good1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-python1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-python1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gstreamer-vaapi (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gstreamer-vaapi (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gstreamer1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gstreamer1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU]  Bugfix release 1.14.4

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

Bug description:
  [ Description ]

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

  [ QA and testing ]

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

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

  [ Regression potential ]

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

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

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

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

2019-05-16 Thread Iain Lane

** Description changed:

- We should update bionic with the (now quite old!) point release
+ [ Description ]
+ 
+ We should keep up with GStreamer's bugfix releases in the 1.14 series
+ that 18.04 shipped with.
+ 
+ [ QA and testing ]
+ 
+ Play a range of videos in Totem. Play a range of audio tracks in
+ Rhythmbox. Try to stream audio and/or video. Try to install a missing
+ codec.
+ 
+ In all cases, make sure that everything which worked before still works.
+ 
+ [ Regression potential ]
+ 
+ If one of the fixes is bad then it might break video or audio playback,
+ or could crash any application that tries to use gstreamer.

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  New

Bug description:
  [ Description ]

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

  [ QA and testing ]

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

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

  [ Regression potential ]

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

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

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

[Desktop-packages] [Bug 1828683] Re: package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to install/upgrade: forsøger at overskrive '/usr/lib/libreoffice/program/libOGLTranslo.so', som også er

** Changed in: libreoffice-l10n (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: libreoffice-l10n (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

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

Title:
  package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to
  install/upgrade: forsøger at overskrive
  '/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken
  libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1

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

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-19.20-generic 4.18.20
  Uname: Linux 4.18.0-19-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Sat May 11 11:42:06 2019
  ErrorMessage: forsøger at overskrive 
'/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken 
libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1
  InstallationDate: Installed on 2018-06-14 (331 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180613)
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: libreoffice
  Title: package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to 
install/upgrade: forsøger at overskrive 
'/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken 
libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This affects all Cosmic users attempting to upgrade LibreOffice to
  6.1.6 from any previous version.

  [Test Case]

   1. Install LibreOffice 6.1.5 on Cosmic
   2. Enable pre-released updates (cosmic-proposed)
   3. apt update && apt upgrade

  [Regression Potential]

   * This issue and its associated fix are isolated to just this upgrade
  path, so potential for further regression is low.

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

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

[Desktop-packages] [Bug 1827451] Re: Japanese new era "Reiwa(令和)" support

Hello Ikuya, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  Japanese new era "Reiwa(令和)" support

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Xenial:
  In Progress
Status in libreoffice source package in Bionic:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This effects all users who use the Japanese era date format in
  LibreOffice.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Start Calc
   2. Put "01/05/2019" into a cell
   3. Right-click on the cell and select "Format Cells"
   4. Set “Language" to "Japanese"
   5. Set “Format" to "H11.12.31"
   6. Cell should show "R1.05.01" (not "N1.05.01”)

  [Regression Potential]

   * The fix is minor so potential for regression is low.

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

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

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

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

Hello Ikuya, or anyone else affected,

Accepted libreoffice-l10n into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source
/libreoffice-l10n/1:6.1.6-0ubuntu0.18.10.2 in a few hours, and then in
the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Japanese new era "Reiwa(令和)" support

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Xenial:
  In Progress
Status in libreoffice source package in Bionic:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This effects all users who use the Japanese era date format in
  LibreOffice.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Start Calc
   2. Put "01/05/2019" into a cell
   3. Right-click on the cell and select "Format Cells"
   4. Set “Language" to "Japanese"
   5. Set “Format" to "H11.12.31"
   6. Cell should show "R1.05.01" (not "N1.05.01”)

  [Regression Potential]

   * The fix is minor so potential for regression is low.

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

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

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

[Desktop-packages] [Bug 1828210] Re: [SRU] libreoffice 6.1.6 for cosmic

Hello Marcus, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  [SRU] libreoffice 6.1.6 for cosmic

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

Bug description:
  [Impact]

   * LibreOffice 6.1.6 is the sixth bugfix release of the still 6.1 line. 
Version 6.1.5 is currently in cosmic.
     For a list of fixed bugs compared to 6.1.5 see the list of bugs fixed in 
the three release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.6/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.6/RC3#List_of_fixed_bugs
     (that's a total of 57 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 57 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1828683] Re: package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to install/upgrade: forsøger at overskrive '/usr/lib/libreoffice/program/libOGLTranslo.so', som også er

Hello Jimmy, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to
  install/upgrade: forsøger at overskrive
  '/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken
  libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1

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

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-19.20-generic 4.18.20
  Uname: Linux 4.18.0-19-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Sat May 11 11:42:06 2019
  ErrorMessage: forsøger at overskrive 
'/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken 
libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1
  InstallationDate: Installed on 2018-06-14 (331 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180613)
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: libreoffice
  Title: package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to 
install/upgrade: forsøger at overskrive 
'/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken 
libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This affects all Cosmic users attempting to upgrade LibreOffice to
  6.1.6 from any previous version.

  [Test Case]

   1. Install LibreOffice 6.1.5 on Cosmic
   2. Enable pre-released updates (cosmic-proposed)
   3. apt update && apt upgrade

  [Regression Potential]

   * This issue and its associated fix are isolated to just this upgrade
  path, so potential for further regression is low.

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

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

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

Hello Marcus, or anyone else affected,

Accepted libreoffice-l10n into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source
/libreoffice-l10n/1:6.1.6-0ubuntu0.18.10.2 in a few hours, and then in
the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] libreoffice 6.1.6 for cosmic

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

Bug description:
  [Impact]

   * LibreOffice 6.1.6 is the sixth bugfix release of the still 6.1 line. 
Version 6.1.5 is currently in cosmic.
     For a list of fixed bugs compared to 6.1.5 see the list of bugs fixed in 
the three release candidates:
   https://wiki.documentfoundation.org/Releases/6.1.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.6/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.1.6/RC3#List_of_fixed_bugs
     (that's a total of 57 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 57 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

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

Hello Jimmy, or anyone else affected,

Accepted libreoffice-l10n into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source
/libreoffice-l10n/1:6.1.6-0ubuntu0.18.10.2 in a few hours, and then in
the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Also affects: libreoffice-l10n (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libreoffice-l10n (Ubuntu Cosmic)
   Status: New => Fix Committed

** Changed in: libreoffice-l10n (Ubuntu)
   Status: New => 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/1828683

Title:
  package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to
  install/upgrade: forsøger at overskrive
  '/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken
  libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1

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

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-19.20-generic 4.18.20
  Uname: Linux 4.18.0-19-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Sat May 11 11:42:06 2019
  ErrorMessage: forsøger at overskrive 
'/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken 
libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1
  InstallationDate: Installed on 2018-06-14 (331 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180613)
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: libreoffice
  Title: package libreoffice-impress 1:6.1.6-0ubuntu0.18.10.1 failed to 
install/upgrade: forsøger at overskrive 
'/usr/lib/libreoffice/program/libOGLTranslo.so', som også er i pakken 
libreoffice-ogltrans 1:6.1.5-0ubuntu0.18.10.1
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This affects all Cosmic users attempting to upgrade LibreOffice to
  6.1.6 from any previous version.

  [Test Case]

   1. Install LibreOffice 6.1.5 on Cosmic
   2. Enable pre-released updates (cosmic-proposed)
   3. apt update && apt upgrade

  [Regression Potential]

   * This issue and its associated fix are isolated to just this upgrade
  path, so potential for further regression is low.

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

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

[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

Hello Gašper, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

  [Impact]

   * This effects all libreoffice-gtk3 users wishing to embed videos
  into an Impress slide.

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

  [Test Case]

   1. Insert a video into an Impress slide
   2. Play the video
   3. The video should play within the slide (not fullscreen like this: 
https://youtu.be/77E6IzVJ5jA)

  [Regression Potential]

   * The fix is one line in the control file so potential for regression
  is low.

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

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

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

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

Hello Gašper, or anyone else affected,

Accepted libreoffice-l10n into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source
/libreoffice-l10n/1:6.1.6-0ubuntu0.18.10.2 in a few hours, and then in
the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

  [Impact]

   * This effects all libreoffice-gtk3 users wishing to embed videos
  into an Impress slide.

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

  [Test Case]

   1. Insert a video into an Impress slide
   2. Play the video
   3. The video should play within the slide (not fullscreen like this: 
https://youtu.be/77E6IzVJ5jA)

  [Regression Potential]

   * The fix is one line in the control file so potential for regression
  is low.

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

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

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

[Desktop-packages] [Bug 1829377] [NEW] Remove this package

2019-05-16 Thread Egmont Koblinger

Public bug reported:

Please remove the ancient GTK2-based vte aka. libvte9{,-common} from
Eoan.

Upstream version has been unmaintained for about 8 years, development
continued in the GTK3 branch (vte2.91 aka. libvte-2.91-0).

Geany is the only package referring to it, and it also does incorrectly
since it already uses GTK3, see bug 1829375.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libvte9 1:0.28.2-6
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu May 16 13:41:04 2019
InstallationDate: Installed on 2016-11-09 (917 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: vte
UpgradeStatus: Upgraded to disco on 2019-04-10 (35 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Remove this package

Status in vte package in Ubuntu:
  New

Bug description:
  Please remove the ancient GTK2-based vte aka. libvte9{,-common} from
  Eoan.

  Upstream version has been unmaintained for about 8 years, development
  continued in the GTK3 branch (vte2.91 aka. libvte-2.91-0).

  Geany is the only package referring to it, and it also does
  incorrectly since it already uses GTK3, see bug 1829375.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libvte9 1:0.28.2-6
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 16 13:41:04 2019
  InstallationDate: Installed on 2016-11-09 (917 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: vte
  UpgradeStatus: Upgraded to disco on 2019-04-10 (35 days ago)

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

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

[Desktop-packages] [Bug 1827508] Re: LibreOffice Impress: presentation mode shows black screen instead of slides

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

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

Title:
  LibreOffice Impress: presentation mode shows black screen instead of
  slides

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  With a dual-screen setup (e.g., notebook monitor plus video projector
  on HDMI cable), when starting a presentation in LO Impress (Slide Show
  -> Start from first slide, or F5), the external monitor turns black
  with something that looks like scrollbars to the right and bottom,
  while the primary monitor only shows the slide editor instead of the
  presenter console.

  Steps to reproduce:
   - Install libreoffice 1:6.2.2-0ubuntu2 in Ubuntu 19.04.
   - Attach secondary monitor / projector.  Extend desktop to the right.
   - Start soffice, create new Impress presentation using an arbitrary template.
   - Press F5.

  Expected behavior:
   - LO Impress shows presenter console on primary and the first slide on 
secondary monitor.

  Actual behavior:
   - Slide editor on primary, black screen with scroll bars to the right and 
bottom on secondary monitor.

  Workaround:
   - Click around on the black area, the presentation (together with the 
presenter console) may show up at some point.
   - Or install LibreOffice 6.2.3.2 from libreoffice.org, works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice-impress 1:6.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  3 14:04:06 2019
  InstallationDate: Installed on 2016-11-26 (887 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to disco on 2019-05-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1829366] [NEW] [SRU] Bugfix release 1.14.4

2019-05-16 Thread Iain Lane

Public bug reported:

We should update bionic with the (now quite old!) point release

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: gstreamer1.0 (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: gstreamer1.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  New

Bug description:
  We should update bionic with the (now quite old!) point release

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

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

[Desktop-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot

This bug was fixed in the package gnome-bluetooth - 3.28.0-2ubuntu0.2

---
gnome-bluetooth (3.28.0-2ubuntu0.2) bionic; urgency=medium

  * debian/patches/git_set_trusted.patch,
debian/patches/git_pair_pointer.patch:
- backport upstream commits to fix marking of device trusted on pairing
  not always working (leading to auto-reconnect not working).
  Always try to pair pointer devices also, that's expected by most
  recent devices, removing the specific list of devices which should
  use the default PIN and do that for all devices (lp: #1779289)

 -- Sebastien Bacher   Fri, 12 Apr 2019 15:06:49
+0200

** Changed in: gnome-bluetooth (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] bluetooth mouse not reconnected on reboot

Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-bluetooth source package in Bionic:
  Fix Released

Bug description:
  * Impact
  Bluetooth pointer devices are not always correctly paired, which leads to 
have them failing to connect or not auto-reconnecting

  *  Test case
  Pair a bluetooth mouse, it should re-connect automatically after 
suspend/resume or reboot cycles

  * Regression potential
  The change makes all devices go through pairing with the standard code that 
should work fine but we should keep an eye if it confuses some devices and lead 
to prompt for a PIN when that shouldn't be needd

  --

  This affects at least 2 different bluetooth mice(both logitech)
  The behavior is that initial config when using the gui works but that the 
resulting
  "/var/lib/bluetooth///info" file does not contain 
a [LinkKey] section as the mouse does not require a pin.
  This mouse was connection on reboot under 16.04 so it's a new bug for 18.04

  When setting up the mouse using bluetoothctl the info file is
  correctly written with a [LinkKey] section and everything works,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-bluetooth 3.28.0-2
  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 Jun 29 11:27:27 2018
  InstallationDate: Installed on 2018-06-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

This bug was fixed in the package modemmanager - 1.10.0-1~ubuntu18.04.2

---
modemmanager (1.10.0-1~ubuntu18.04.2) bionic; urgency=medium

  * debian/patches/error-propagation-fix.patch: mm-broadband-modem: Fix error
propagation in CDMA service status (LP: #1819615, Upstream Issue #119).

modemmanager (1.10.0-1~ubuntu18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1819615)
  * debian/control: Update build dependencies as now libmbim >= 1.18.0 and
libqmi >= 1.22.0 are required.
  * debian/libmm-glib0.symbols: update symbols for new release.
  * debian/patches/0001-m4-compiler_warnings.m4-Let-Werror-be-disabled.patch:
Removed, included upstream.

 -- Till Kamppeter   Mon, 06 May 2019 16:09:29
+0200

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

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Released
Status in libqmi source package in Bionic:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

This bug was fixed in the package libmbim - 1.18.0-1~ubuntu18.04.1

---
libmbim (1.18.0-1~ubuntu18.04.1) bionic; urgency=medium

  * New upstream release
- Needed by ModemManager 1.10 (LP: #1819615).
  * debian/libmbim-glib4.symbols: Updated symbols for new release.
  * debian/patches/ref_cast.patch: Removed, not applicable any more on
1.18.0.

libmbim (1.16.0-1) unstable; urgency=medium

  * New upstream release 1.16.0 (Closes: #887974)
  * Adopting the package. (Closes: #888680)
  * debian/control: bump libglib-dev Depends to (>= 2.36) as required by the
new release.
  * debian/libmbim-glib4.symbols: update symbols for new release.
  * debian/rules: add DPKG_GENSYMBOLS_CHECK_LEVEL=4; it's more verbose with
added or changed symbols then.

 -- Till Kamppeter   Thu, 20 Mar 2019 20:37:29
+0100

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Released
Status in libqmi source package in Bionic:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

We should think about cosmic indeed, but it's not really blocking the
release for bionic. Currently upgrades from bionic to cosmic will very
very very rare. With disco released, there's no 'official' upgrade path
- not to mention bionic users by default should be only informed of new
LTS versions. So I'll proceed with getting this out.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Released
Status in libqmi source package in Bionic:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

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

[Desktop-packages] [Bug 1819615] Update Released

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

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Released
Status in libqmi source package in Bionic:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

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

[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

This bug was fixed in the package libqmi - 1.22.0-1.2~ubuntu18.04.1

---
libqmi (1.22.0-1.2~ubuntu18.04.1) bionic; urgency=medium

  * Build for Bionic (LP: #1819615).
  * debian/libqmi-glib5.symbols: update symbols for new release.

libqmi (1.22.0-1.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Add debian/patches/git_reset-offset-before-2nd-call.patch from upstream.
- equivalent to 1.22.2 release except the broken manpages in that release.

libqmi (1.22.0-1.1) unstable; urgency=medium

  * Non-maintainer upload
  * Bump Build-Depends on libmbim-glib-dev to 1.18.0 to fix build
(Closes: #921321)

libqmi (1.22.0-1) unstable; urgency=medium

  * New upstream release
- Needed by ModemManager 1.10.
  * 
debian/patches/0001-qmicli-remove-implicity-casts-to-GDestroyNotify-in-g.patch:
Dropped, included upstream.
  * debian/libqmi-glib5.symbols: update symbols for new release.

libqmi (1.20.0-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Add upstream fix for FTBFS with glib 2.58,
thanks to Juhani Numminen. (Closes: #908016)

libqmi (1.20.0-1) unstable; urgency=medium

  * New upstream version 1.20.0. (Closes: #887975)
  * debian/patches/0001-utils-drop-useless-g_file_test-call.patch: dropped,
included upstream.
  * debian/libqmi-glib5.symbols: update symbols for new release.
  * debian/control: changing Maintainer field to claim the package. Marius is
no longer interested in maintaining it.
  * debian/control: bump Standards-Version to 4.1.3.

 -- Till Kamppeter   Wed, 20 Mar 2019 14:28:39
+0100

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

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

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Released
Status in libqmi source package in Bionic:
  Fix Released
Status in modemmanager source package in Bionic:
  Fix Released
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

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

[Desktop-packages] [Bug 1829364] [NEW] Will not play sound via HDMI unless you run pavucontrol first

2019-05-16 Thread Jarno Suni

Public bug reported:

Does not play sound via sink output:iec958-stereo unless I start
pavucontrol before running the player such as paplay. Player does not
show any error and takes its time to play, but there is no sound.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jarnos 1283 F pulseaudio
CurrentDesktop: XFCE
Date: Thu May 16 12:39:15 2019
InstallationDate: Installed on 2019-05-08 (7 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MVD Ver. F.20
dmi.board.name: 30C5
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard

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

Title:
  Will not play sound via HDMI unless you run pavucontrol first

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Does not play sound via sink output:iec958-stereo unless I start
  pavucontrol before running the player such as paplay. Player does not
  show any error and takes its time to play, but there is no sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarnos 1283 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu May 16 12:39:15 2019
  InstallationDate: Installed on 2019-05-08 (7 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1829353] Re: Click the app icon in ubuntu dock, the app do not minimize to dock

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

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


** Tags added: bionic

** This bug has been marked a duplicate of bug 1723835
   Dock - Clicking icon doesn't minimize

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

Title:
  Click the app icon in ubuntu dock, the app do not minimize to dock

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

Bug description:
  I use ubuntu18.04
  If I click the app icon in ubuntu dock, the app will start up, then I click 
the app icon in ubuntu dock want to minimize the app window, nothing happens.

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

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

[Desktop-packages] [Bug 1723835] Re: Dock - Clicking icon doesn't minimize

** Tags removed: artful
** Tags added: bionic

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

Title:
  Dock - Clicking icon doesn't minimize

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

Bug description:
  I have open Firefox, it is maximized. Clicking on it's icon in the
  Dock does nothing, I expect it would minimize Firefox. Unity, KDE and
  Windows behave in this manor.

  Window doesn't have to be maximized to show this behavior, clicking
  the icon in the Dock will bring up a selection popup if there are
  multiple instances of that application open, but if there is only one
  it does nothing.

  Tested with Gnome Terminal, Firefox, Chromium, Files, VLC, Terminator,
  all behave the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 19:54:00 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-10-29 (717 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-15 (0 days ago)

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

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

[Desktop-packages] [Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

2019-05-16 Thread kkivi

The bug is still there 
Ubuntu 18.10 

Specific scenarios in firefox

1) open duckduckgo search page, start typing and switch layout - focus loss
2) register  wonderlist account, create task, add a note to it, start typing 
and switch layout - focus lost and textbox collapses.

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

Status in GNOME Settings Daemon:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-shell package in Fedora:
  Confirmed
Status in gnome package in openSUSE:
  Unknown

Bug description:
  When pressing any global keyboard shourtcut (configurable via System
  settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout,
  volume up/down), focus temporary switches from active text input to
  something else, then restores back shortly. Maybe even active window
  loses focus, but window frame does not shows this (window header
  remains to look active).

  For example: when I press ctrl+shift here to switch keyboard layout,
  when writing this description, yellow frame disappears from text input
  box, text caret disappears too; they appear again when releasing
  ctrl+shift. The same occurs in all other programs, i.e. terminal.

  It causes serious annoyance, for example in Twitter when losing focus
  in Reply text box, reply rolls up and I have to click it again with
  mouse and set caret to correct place each time I switch keyboard
  layouts.

  Other key combinations, not only ctrl+shift, also cause this.

  It is especially annoying when using keyboard layout switch shortcut
  handled by the same subsystem (media-keys plugin):

  case SWITCH_INPUT_SOURCE_KEY:
  case SWITCH_INPUT_SOURCE_BACKWARD_KEY:
  do_switch_input_source_action (manager, type);
  break;

  (Original gnome-settings-daemon, from which unity-settings-daemon was
  forked, does not use media-keys plugin to switch keyboard layout).

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session 3.9.90-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 24 11:42:19 2013
  InstallationDate: Installed on 2013-10-23 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1823778] Re: Unable to set Serbian as Language

This bug was fixed in the package gnome-control-center -
1:3.28.2-0ubuntu0.18.04.4

---
gnome-control-center (1:3.28.2-0ubuntu0.18.04.4) bionic; urgency=medium

  * debian/patches/ubuntu-region-langpack-install.patch:
- Dropped, which makes Serbian language items show up as selectable
  in Region & Language (LP: #1823778).
  * debian/patches/52_region_language.patch:
- Prevent that the modifier part is dropped when a language
  represented by a locale with modifier is set (LP: #1823778).

 -- Gunnar Hjalmarsson   Sat, 13 Apr 2019 03:05:00
+0200

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Unable to set Serbian as Language

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Disco:
  Fix Released

Bug description:
  [Impact]

  The Serbian language items, both the Cyrillic and the Latin, are not
  shown as selectable items in the Language widget in Region & Language.
  Furthermore, once that has been fixed, selecting the Serbian-Latin
  option results in the Serbian-Cyrillic language to be set.

  The proposed upload (via merge proposal) fixes both the issues.

  [Workaround]

  To set a Serbian language option (or Catalan - Valencia, which is also
  affected by this) you can go to Settings -> Region & Language, click
  the "Manage Installed Languages" button, and set it through that GUI.

  [Test Case]

  * Install gnome-control-center from {bionic,disco}-proposed.

  * Install the Serbian language via gnome-language-selector.

  * Open Settings -> Region & Language and open the Language widget.

  * You should see both "Serbian (Serbia)" and "Serbian (Serbia) - latin"
    in the list. Confirm that you can successfully switch to both the
    options.

  [Regression Potential]

  An explanation how the proposed fixes address the issues would be a
  bit technical, but basically we simply drop Ubuntu specific changes
  which have proved to have adverse side effects. The regression risk
  ought to be low.

  [Original description]

  Affected: 18.04.2 (did not try earlier versions of 18.04 series)
  Not affected: 16.04 - any version (UI was different)

  Preparation steps:
  1. open gnome control center
  2. open Region & Language
  3. open Manage installed languages
  4. open Install/Remove languages
  5. select Serbian, click Apply
  6. provide credentials for sudo installation
  7. wait for installation to complete
  8. click Close

  What is wrong:
  1. open gnome control center
  2. open Region & Language
  3. click Language selection
  4. Serbian is not visible

  Notes:
  - Serbian is visible for the Formats selection
  - Any other language I thought of: (Macedonian, Croatian, Bosnian, 
Russion...) simple work.

  Here is some dpkg output on installaed packages matching sr (Serbian)
  or hr (Croatian).

  ii  firefox-locale-sr  66.0.2+build1-0ubuntu0.18.04.1 
  amd64Serbian language pack for Firefox
  ii  gnome-getting-started-docs-sr  3.28.2-0ubuntu0.1  
  all  Help a new user get started in GNOME (Serbian)
  ii  gnome-user-docs-sr 3.28.2+git20180715-0ubuntu0.1  
  all  GNOME user's guide (Serbian)
  ii  hunspell-sr1:6.0.3-3  
  all  Serbian dictionary for hunspell
  ii  hyphen-sr  1:6.0.3-3  
  all  Serbian hyphenation patterns
  ii  language-pack-gnome-sr 1:18.04+20180712   
  all  GNOME translation updates for language Serbian
  ii  language-pack-gnome-sr-base1:18.04+20180712   
  all  GNOME translations for language Serbian
  ii  language-pack-sr   1:18.04+20180712   
  all  translation updates for language Serbian
  ii  language-pack-sr-base  1:18.04+20180712   
  all  translations for language Serbian
  ii  libreoffice-l10n-sr1:6.0.7-0ubuntu0.18.04.2   
  all  office productivity suite -- Serbian language package
  ii  thunderbird-locale-sr  
1:60.6.1+build2-0ubuntu0.18.04.1 amd64Serbian language pack 
for Thunderbird
  nebojsa@momcilo-desktop:~$ dpkg -l | grep -e "-hr"
  rc  language-pack-gnome-hr-base1:18.04+20180712   
  all  GNOME translations for language Croatian
  rc

[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes

@Robie, bionic/disco are coming but we wanted to include extra fixes and
we are waiting for an upstream point release for disco, do we need to
block Xenial on those?

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

Title:
  Power: Fail to set delay time when the value is 90 minutes

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in OEM Priority Project xenial series:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

  Fail to set delay time when the value is 90 minutes.

  In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not
  5400 (90*60). When setting the delay time to 90 minutes, the UI will
  show "80 minutes" after reopening "All Settings". (Please refer to the
  photo in #1 and #2)

  [Test Case]

  1) Go to [All Settings][Power][Automatic suspend]

  2) Set delay time to 90 minutes (On Battery Power or Plugged in)

  3) Close [All Settings]

  4) Reopen [All Settings][Power][Automatic suspend]

  5) Check if the value is 90 minutes.

  [Regression Potential]

  Low. The value of 90 minutes is wrong. Just correct the value to 5400.

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

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

[Desktop-packages] [Bug 1829353] [NEW] Click the app icon in ubuntu dock, the app do not minimize to dock

2019-05-16 Thread widon1104

Public bug reported:

I use ubuntu18.04
If I click the app icon in ubuntu dock, the app will start up, then I click the 
app icon in ubuntu dock want to minimize the app window, nothing happens.

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

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

Title:
  Click the app icon in ubuntu dock, the app do not minimize to dock

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

Bug description:
  I use ubuntu18.04
  If I click the app icon in ubuntu dock, the app will start up, then I click 
the app icon in ubuntu dock want to minimize the app window, nothing happens.

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

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

[Desktop-packages] [Bug 1828846] Re: ecra

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

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

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

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

Title:
  ecra

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Notebook hp elitebook 8440p com sensor de rotação da tela, ao instalar 
ubuntu19 ele reconhece a tela virada 180 graus e o ponteiro do mouse no 
sentindo certo.
  Ao tentar inverter a tela através de comandos ou configuração ela vira porem 
o mouse ainda fica invertido.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 15:54:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:172a]
  MachineType: Hewlett-Packard HP EliteBook 8440p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=3a114823-2ff8-428d-8823-ecbf3fb1e030 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.0B
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.2C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.0B:bd06/02/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.2C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8440p
  dmi.product.sku: SJ905UP#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'

Thanks

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

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

Title:
Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access
based share enumeration = yes'

Status in gvfs:
New
Status in gvfs package in Ubuntu:
Triaged

Bug description:
From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other
Locations", I see my samba/SMB server. If I double click it, it then
lists *some* of my shares. Specifically, it lists those where I didn't
use Samba's 'access based share enumeration = yes'[1] (which allows
some shares to be made completely invisible to some users). Note that
Ubuntu has *not* yet asked me to authenticate, so it makes sense that
I shouldn't yet be able to see shares I'm not entitled to.

The bug is: even after I authenticate (and let it remember my
password), then go back to Other Locations>MyServer, it *still*
doesn't show the other shares. In fact, I can't find *any* way to see
the other shares.

Contrast this with macOS Finder. If I navigate to MyServer in the
share list, it doesn't show *any* shares until I authenticate, then it
shows *all* shares that the user has access to (and none of the shares
the user doesn't have access to).

Ubuntu could either:
- adopt macOS Finder behaviour and get authentication first, or
- update the share list after authentication is performed.

Its current behaviour makes some shares totally inaccessible (the crux
of the bug).

I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest)
using ZFS, running samba 4.9.6. Other users on the FreeNAS forum see
the same behaviour[2], so it's not particular to my setup.

[1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
[2]
https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/

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

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

[Desktop-packages] [Bug 1827508] Re: LibreOffice Impress: presentation mode shows black screen instead of slides