[Desktop-packages] [Bug 1856590] Re: Missing dots on Cyrillic letters

2020-03-28 Thread Jeremy Bicha
The newest version of fonts-noto will be in Ubuntu 20.04 LTS which will
be released later in April.

** Changed in: fonts-noto (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Missing dots on Cyrillic letters

Status in fonts-noto package in Ubuntu:
  Fix Released

Bug description:
  The soft-dotted Cyrillic letters U+0456 and U+0458 are missing their
  dots

  See upstream issue -- https://github.com/googlefonts/noto-fonts/issues/1051
  Fixed in latest master -- https://github.com/googlefonts/noto-source/pull/125

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

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


[Desktop-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length

2020-03-28 Thread Alkis Georgopoulos
Hi all,

final freeze is approaching, and I don't see anyone syncing Andrej's new
version from Debian...

Maybe it would be easier to just accept my patch, to have this solved
for 20.04, and do the syncing for 20.10?

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

Title:
  Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  Some wifi adapters kept asking for a password when MAC address
  randomization was enabled.

  I reported this to Realtek, and they gave me a patch for
  wpa_supplicant, which fixes the issue.

  I asked Realtek to report this upstream to wpasupplicant, and they
  did, the commit is:
  http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563

  It would be very nice to cherrypick that for Focal.

  I uploaded it as a merge request below, and I tested that it fixes the issue 
with adapters based on the following chipsets:
  ath9k, rtl8812au, rtl88x2bu and rtl8821cu

  To reproduce this:

  Ubuntu's network-manager defaults to "MAC randomization disabled", I think as 
a workaround to this specific issue. This is defined in two places:
  - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf
  - Some specific drivers in 
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.

  With these, the problem happens in around 10% of the cases.
  To be able to reproduce it in 100% of the cases, it's best to remove these 
Ubuntu workarounds. So:
  - Set "wifi.scan-rand-mac-address=yes" in 
/etc/NetworkManager/NetworkManager.conf
  - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.
  - systemctl stop network-manager
  - killall wpa_supplicant
  - systemctl start network-manager

  Then insert a USB wifi adapter that results in a big name with 15
  characters like wlx74ee2ae2436a and try to connect to a wifi network.
  It will keep asking for a password.

  Then apply the patch, run the 3 commands above to restart network-
  manager, and verify that it can now connect properly.

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

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


[Desktop-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

2020-03-28 Thread Robson Tenorio
Pain is over!

https://www.linux.org/threads/samsung-notebook-7-force-headphone-jack-
and-keyboard-lighting-issues.27304/#post-87920

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor:

[Desktop-packages] [Bug 1246677] Re: gnome shell extensions disabled

2020-03-28 Thread Launchpad Bug Tracker
[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/1246677

Title:
  gnome shell extensions disabled

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  As of the last update from the gnome3-staging PPA, all of my shell
  extensions have been disabled. Going to the gnome extensions website
  shows that none of the extensions are compatible, even those formerly
  installed and compatible with 3.10.

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

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


[Desktop-packages] [Bug 1860764] Re: Line out audio device is missing after resume-from-suspend

2020-03-28 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Line out audio device is missing after resume-from-suspend

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1860764] Re: Line out audio device is missing after resume-from-suspend

2020-03-28 Thread Launchpad Bug Tracker
[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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1860764

Title:
  Line out audio device is missing after resume-from-suspend

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1869549] [NEW] Whenever a sound needs to be played the screen blanks out

2020-03-28 Thread Abhigyan
Public bug reported:

Whenever a sound needs to be played the screen blanks out for a second,
then the screen comes back on, and the sound plays.

Examples of sounds are when I press Tab on the terminal, and there are
no possible completions, or when I press the down button on the
terminal, and there are no further lines below, then it blanks out,
comes back, and then plays the "ding" tone telling me there are no
further completions or lines.

However, after one blank-out, if I keep pressing the down button, the
sounds play normally without blanking out for a short time. After that
period, it repeats again on doing something that would cause the sound
to be played again.

I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa
(Development branch)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 29 09:05:04 2020
DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.3.0-42-generic, x86_64: installed
 nvidia, 435.21, 5.4.0-18-generic, x86_64: installed
 virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed
 virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:86e2]
   Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2]
InstallationDate: Installed on 2019-11-30 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Camera
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Laptop 15-cs3xxx
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago)
dmi.bios.date: 08/23/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.03
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 86E2
dmi.board.vendor: HP
dmi.board.version: 95.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cs3xxx
dmi.product.sku: 8LX85PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal reproducible 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/1869549

Title:
  Whenever a sound needs to be played the screen blanks out

Status in xorg package in Ubuntu:
  New

Bug description:
  Whenever a sound needs to be played the screen blanks out for a
  second, then the screen comes back on, and the sound

[Desktop-packages] [Bug 1868131] Re: [Toshiba NB250] Integrated speakers always muted

2020-03-28 Thread Pablo César Galdo Regueiro
I tried to boot Puppy Linux BionicPup64 8.0 based on Ubuntu Bionic
x86_64 64-bit and sound works out of the box.

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

Title:
  [Toshiba NB250] Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

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

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


[Desktop-packages] [Bug 1869537] [NEW] "Unable to find [Invalid UTF-8]" after installing a downloaded deb package

2020-03-28 Thread Timur Tabi
Public bug reported:

I downloaded a deb package (in this case Skype, but it's happened with
other downloaded debs) and the package installed correctly.  However,
upon completion, the gnome-software window displayed

Unable to find "[Invalid UTF-8]"

I can close the window and everything is fine.  It's just weird that it
displays this message.

I've attached a screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software 3.30.6-2ubuntu4.19.04.2
ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
Uname: Linux 5.0.0-38-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 28 17:43:32 2020
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2019-06-02 (300 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.30.6-2ubuntu4.19.04.2
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

** Attachment added: "Screenshot from 2020-03-28 17-40-44.png"
   
https://bugs.launchpad.net/bugs/1869537/+attachment/5342738/+files/Screenshot%20from%202020-03-28%2017-40-44.png

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

Title:
  "Unable to find [Invalid UTF-8]" after installing a downloaded deb
  package

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I downloaded a deb package (in this case Skype, but it's happened with
  other downloaded debs) and the package installed correctly.  However,
  upon completion, the gnome-software window displayed

  Unable to find "[Invalid UTF-8]"

  I can close the window and everything is fine.  It's just weird that
  it displays this message.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu4.19.04.2
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 17:43:32 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-06-02 (300 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu4.19.04.2
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2020-03-28 Thread Paul
apport information

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

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

Title:
  Corrupted Model number and Serial number in gnome-disks

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

Bug description:
  When I run the disks program I frequently see the model and serial
  number of the disks I'm working with is corrupted.

  Most often this is with WD drives, but i have seen it with other
  brands

  However when i use GSmartControl theses entries are fine (they model
  number is also reported correctly in GParted).

  I' using gnome-disk-utility 3.34.0 and GSmartControl 1.1.3

  
  Screen grab attached for Disks (on the left) and GSmartControl (right)

  
  Still a very noob at reporting bugs, so apologies if this is the wrong 
forum/method/reporting style/I left information out..

  Happy to supply any other information you need
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-11-09 (505 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-disk-utility 3.34.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (183 days ago)
  UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo
  _MarkForUpload: True

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

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


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

2020-03-28 Thread Paul
apport information

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

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

Title:
  Corrupted Model number and Serial number in gnome-disks

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

Bug description:
  When I run the disks program I frequently see the model and serial
  number of the disks I'm working with is corrupted.

  Most often this is with WD drives, but i have seen it with other
  brands

  However when i use GSmartControl theses entries are fine (they model
  number is also reported correctly in GParted).

  I' using gnome-disk-utility 3.34.0 and GSmartControl 1.1.3

  
  Screen grab attached for Disks (on the left) and GSmartControl (right)

  
  Still a very noob at reporting bugs, so apologies if this is the wrong 
forum/method/reporting style/I left information out..

  Happy to supply any other information you need
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-11-09 (505 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-disk-utility 3.34.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (183 days ago)
  UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1869449] Re: Corrupted Model number and Serial number in gnome-disks

2020-03-28 Thread Paul
apport information

** Tags added: apport-collected

** Description changed:

  When I run the disks program I frequently see the model and serial
  number of the disks I'm working with is corrupted.
  
  Most often this is with WD drives, but i have seen it with other brands
  
  However when i use GSmartControl theses entries are fine (they model
  number is also reported correctly in GParted).
  
  I' using gnome-disk-utility 3.34.0 and GSmartControl 1.1.3
  
  
  Screen grab attached for Disks (on the left) and GSmartControl (right)
  
  
  Still a very noob at reporting bugs, so apologies if this is the wrong 
forum/method/reporting style/I left information out..
  
  Happy to supply any other information you need
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.7
+ Architecture: amd64
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2018-11-09 (505 days ago)
+ InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-disk-utility 3.34.0-2ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
+ Tags:  eoan
+ Uname: Linux 5.3.0-42-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-09-27 (183 days ago)
+ UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Corrupted Model number and Serial number in gnome-disks

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

Bug description:
  When I run the disks program I frequently see the model and serial
  number of the disks I'm working with is corrupted.

  Most often this is with WD drives, but i have seen it with other
  brands

  However when i use GSmartControl theses entries are fine (they model
  number is also reported correctly in GParted).

  I' using gnome-disk-utility 3.34.0 and GSmartControl 1.1.3

  
  Screen grab attached for Disks (on the left) and GSmartControl (right)

  
  Still a very noob at reporting bugs, so apologies if this is the wrong 
forum/method/reporting style/I left information out..

  Happy to supply any other information you need
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-11-09 (505 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-disk-utility 3.34.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-42-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (183 days ago)
  UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1869511] Re: package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menub

2020-03-28 Thread Rico Tzschichholz
*** This bug is a duplicate of bug 1869357 ***
https://bugs.launchpad.net/bugs/1869357

** This bug has been marked a duplicate of bug 1869357
   package libreoffice-math 1:6.4.2-0ubuntu1 failed to install/upgrade: trying 
to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.1-0ubuntu1

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

Title:
  package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade:
  trying to overwrite
  
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
  which is also in package libreoffice-common 1:6.4.0-0ubuntu7

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Unable to update base Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-math 1:6.4.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Sat Mar 28 18:58:36 2020
  DuplicateSignature:
   package:libreoffice-math:1:6.4.0-0ubuntu7
   Unpacking libreoffice-math (1:6.4.2-0ubuntu1) over (1:6.4.0-0ubuntu7) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-aD6jGo/188-libreoffice-math_1%3a6.4.2-0ubuntu1_amd64.deb 
(--unpack):
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  InstallationDate: Installed on 2020-03-18 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: libreoffice
  Title: package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-03-28 Thread Unathi
I have the tried solution from
https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Carbon_(Gen_7)
and it seems to have worked for me on Arch! You can also have a look at
https://gist.github.com/hamidzr/dd81e429dc86f4327ded7a2030e7d7d9

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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


[Desktop-packages] [Bug 211966] Re: nautilus-share report a warning about missing /var/lib/samba/usershares

2020-03-28 Thread Bib
Still affected in 16.04.6 upgraded from Trusty : the log in this machine
shows

Mar 28 17:41:43 nux gnome-session[25837]: Nautilus-Share-Message: Called "net 
usershare info" but it failed: « net usershare » returned error 255 : mkdir 
failed on directory /var/run/samba/msg.lock: Permission denied
Mar 28 17:41:43 nux gnome-session[25837]: net usershare: cannot open usershare 
directory /var/lib/samba/usershares. Error None file or directory of this kind
Mar 28 17:41:43 nux gnome-session[25837]: Please ask your system administrator 
to enable user sharing.

even after I created /var/lib/samba/usershares and touch
/var/run/samba/msg.lock (*):

~ ls -l /var/lib/samba/
total 8
drwxr-xr-x 3 root root 4096 march   4  2017 private
drwxr-xr-x 2 root root 4096 march  28 17:42 usershares

# members sambashare
me

$ ls -l /var/run/samba/msg.lock
-rw-r--r-- 1 root root 0 mars  28 18:55 /var/run/samba/msg.lock

(*)Maybe I should have mkdir msg.lock ?
Yes I should:
$ net usershare info --long
directory /var/run/samba/msg.lock isn't a directory

# rm /var/run/samba/msg.lock
# mkdir /var/run/samba/msg.lock

Wait and see

Here only nautilus-share is installed (I was prompted to install it by
Files one day when I wanted to share a folder - Samba not installed :
not prompted=no need)

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

Title:
  nautilus-share report a warning about missing
  /var/lib/samba/usershares

Status in Apache2 Web Server:
  Invalid
Status in OEM Priority Project:
  New
Status in nautilus-share package in Ubuntu:
  Fix Released
Status in samba package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: nautilus-share

  if you start nautilus from console you can see this error message:

  Nautilus-Share-Message: Called "net usershare info" but it failed: 'net 
usershare' returned error 255: net usershare: cannot open usershare directory 
/var/lib/samba/usershares. Error Aucun fichier ou dossier de ce type
  Please ask your system administrator to enable user sharing.

  I assume it needs to create /var/lib/samba/usershares in the package

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

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


[Desktop-packages] [Bug 1869511] Re: package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menub

2020-03-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade:
  trying to overwrite
  
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
  which is also in package libreoffice-common 1:6.4.0-0ubuntu7

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Unable to update base Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-math 1:6.4.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Sat Mar 28 18:58:36 2020
  DuplicateSignature:
   package:libreoffice-math:1:6.4.0-0ubuntu7
   Unpacking libreoffice-math (1:6.4.2-0ubuntu1) over (1:6.4.0-0ubuntu7) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-aD6jGo/188-libreoffice-math_1%3a6.4.2-0ubuntu1_amd64.deb 
(--unpack):
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  InstallationDate: Installed on 2020-03-18 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: libreoffice
  Title: package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869520] Re: the windows hang after shifting

2020-03-28 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1869520

Title:
  the windows hang after shifting

Status in xorg package in Ubuntu:
  New

Bug description:
  When I want to shift open windows, like files, browsers, etc. they
  freeze and hang and I can neither minimize nor close that window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 21:05:02 2020
  DistUpgraded: 2020-03-26 22:02:16,208 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon RX 560 [1043:04bc]
  InstallationDate: Installed on 2020-02-02 (55 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. AB350M-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=5909a9b7-eb21-439d-a04c-2c42bf662b3c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago)
  dmi.bios.date: 05/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F31
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350M-Gaming 3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF31:bd05/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350M-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1869520/+subscriptions

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


[Desktop-packages] [Bug 1869520] [NEW] the windows hang after shifting

2020-03-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When I want to shift open windows, like files, browsers, etc. they
freeze and hang and I can neither minimize nor close that window.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 28 21:05:02 2020
DistUpgraded: 2020-03-26 22:02:16,208 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed
 virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Radeon RX 560 [1043:04bc]
InstallationDate: Installed on 2020-02-02 (55 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Gigabyte Technology Co., Ltd. AB350M-Gaming 3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=5909a9b7-eb21-439d-a04c-2c42bf662b3c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago)
dmi.bios.date: 05/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F31
dmi.board.asset.tag: Default string
dmi.board.name: AB350M-Gaming 3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF31:bd05/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350M-Gaming 3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug false-gpu-hang focal freeze reproducible ubuntu
-- 
the windows hang after shifting
https://bugs.launchpad.net/bugs/1869520
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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


[Desktop-packages] [Bug 1869524] [NEW] Simple Scan doesn't load

2020-03-28 Thread Charles
Public bug reported:

Simple Scan version 3.28.0-0ubuntu1 fails to load in Ubuntu 18.04 LTS

simple-scan: error while loading shared libraries: libcolord.so.1:
cannot open shared object file: No such file or directory

Related to bug# 1869522
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1869522

Not sure if I should be reporting the bug against Simple Scan, Gnome, or
Ubuntu 18.04 LTS.

Gnome project said it's not a bug with Simple Scan.  Something about not having 
the latest version of Gnome bundled with Ubuntu 18.04 LTS.
https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: simple-scan 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux 4.15.0-91-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 28 15:53:47 2020
InstallationDate: Installed on 2014-08-08 (2059 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: MSI MS-7922
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=12cc7d65-8589-4aab-a77b-566ea7af9984 ro pci=assign-busses quiet 
splash vt.handoff=1
SimpleScanLog:
 
SourcePackage: simple-scan
UpgradeStatus: Upgraded to bionic on 2020-01-05 (83 days ago)
dmi.bios.date: 02/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 U3 PLUS (MS-7922)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd02/16/2016:svnMSI:pnMS-7922:pvr1.0:rvnMSI:rnZ97U3PLUS(MS-7922):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7922
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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

Title:
  Simple Scan doesn't load

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Simple Scan version 3.28.0-0ubuntu1 fails to load in Ubuntu 18.04 LTS

  simple-scan: error while loading shared libraries: libcolord.so.1:
  cannot open shared object file: No such file or directory

  Related to bug# 1869522
  https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1869522

  Not sure if I should be reporting the bug against Simple Scan, Gnome,
  or Ubuntu 18.04 LTS.

  Gnome project said it's not a bug with Simple Scan.  Something about not 
having the latest version of Gnome bundled with Ubuntu 18.04 LTS.
  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: simple-scan 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 15:53:47 2020
  InstallationDate: Installed on 2014-08-08 (2059 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: MSI MS-7922
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=12cc7d65-8589-4aab-a77b-566ea7af9984 ro pci=assign-busses quiet 
splash vt.handoff=1
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to bionic on 2020-01-05 (83 days ago)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 U3 PLUS (MS-7922)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd02/16/2016:svnMSI:pnMS-7922:pvr1.0:rvnMSI:rnZ97U3PLUS(MS-7922):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7922
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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


[Desktop-packages] [Bug 1869522] [NEW] Simple Scan doesn't work

2020-03-28 Thread Charles
Public bug reported:

The latest version of Simple Scan released for Ubuntu 18.04 LTS does not
work.  Version 3.28.0-0ubuntu1 is installed.  When I click to launch it
nothing happens.

I initially reported the bug against Simple Scan, but they said it was a
problem with the Ubuntu 18.04 LTS distribution.

https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.14
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux 4.15.0-91-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 28 15:29:05 2020
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2014-08-08 (2059 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: gnome-software
UpgradeStatus: Upgraded to bionic on 2020-01-05 (82 days ago)

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

Title:
  Simple Scan doesn't work

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The latest version of Simple Scan released for Ubuntu 18.04 LTS does
  not work.  Version 3.28.0-0ubuntu1 is installed.  When I click to
  launch it nothing happens.

  I initially reported the bug against Simple Scan, but they said it was
  a problem with the Ubuntu 18.04 LTS distribution.

  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.14
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 15:29:05 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2014-08-08 (2059 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2020-01-05 (82 days ago)

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

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


[Desktop-packages] [Bug 1869519] [NEW] nm-applet shows redundant separator line

2020-03-28 Thread iron foot
Public bug reported:

System: Ubuntu MATE 20.04 daily.

Package: network-manager-gnome 1.8.24-1ubuntu2.

Problem: Ubuntu MATE default themes were updated for 20.04 release. In
particular, separator paddings were increased to improve indicator
readability [https://ubuntu-mate.community/t/ubuntu-mate-20-04-pre-
release-testing/20881/87]. Now one can notice a redundant separator line
at the bottom of nm-applet menu (see attachment).

Expected: Redundant separator line is removed.

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

** Attachment added: "regression.png"
   
https://bugs.launchpad.net/bugs/1869519/+attachment/5342645/+files/regression.png

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

Title:
  nm-applet shows redundant separator line

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

Bug description:
  System: Ubuntu MATE 20.04 daily.

  Package: network-manager-gnome 1.8.24-1ubuntu2.

  Problem: Ubuntu MATE default themes were updated for 20.04 release. In
  particular, separator paddings were increased to improve indicator
  readability [https://ubuntu-mate.community/t/ubuntu-mate-20-04-pre-
  release-testing/20881/87]. Now one can notice a redundant separator
  line at the bottom of nm-applet menu (see attachment).

  Expected: Redundant separator line is removed.

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

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


[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

2020-03-28 Thread Simon Labrecque
This also happens in 20.04.

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

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

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  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/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

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


[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-03-28 Thread Ivan Dario Ramos Vacca
I have the same issue with an Acer Swift 3 SF314-57 58D5.

Now running ubuntu 18.04

At first neither speakers or mic were working. I managed to get the speakers 
working by modifying the file /etc/modprobe.d/alsa-base.confn adding a lines at 
the end "options snd-hda-intel dmic_detect=0" [without quotes].
/etc/
The output for "arecord -l"

is as follows:

"""
 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: Generic Analog [Generic Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
"""
Tried adding "blacklist snd_soc_skl" to the file /etc/modprobe.d/blacklist.conf


No solution still found.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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


[Desktop-packages] [Bug 1869513] Re: package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1

2020-03-28 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package openexr 2.3.0-6build1 failed to install/upgrade: installed
  openexr package post-installation script subprocess returned error
  exit status 1

Status in openexr package in Ubuntu:
  New

Bug description:
  /usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by 
/usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or 
-rpath-link)
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::ChannelList::insert(char const*, Imf_2_2::Channel const&)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::hasChromaticities(Imf_2_2::Header const&)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::InputFile::readPixels(int, int)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::InputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::channels() const'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::InputFile::InputFile(char const*, int)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::FrameBuffer::insert(char const*, Imf_2_2::Slice const&)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::chromaticities(Imf_2_2::Header const&)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::globalThreadCount()'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::InputFile::header() const'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::OutputFile::writePixels(int)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Channel::Channel(Imf_2_2::PixelType, int, int, bool)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::FrameBuffer::begin()'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Slice::Slice(Imf_2_2::PixelType, char*, unsigned long, unsigned long, 
int, int, double, bool, bool)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::OutputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::dataWindow() const'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::channels()'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::~Header()'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::OutputFile::OutputFile(char const*, Imf_2_2::Header const&, int)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::ChannelList::findChannel(char const*) const'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::FrameBuffer::end()'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::Header(int, int, float, Imath_2_2::Vec2 const&, float, 
Imf_2_2::LineOrder, Imf_2_2::Compression)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Chromaticities::Chromaticities(Imath_2_2::Vec2 const&, 
Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&, 
Imath_2_2::Vec2 const&)'
  /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::OutputFile::~OutputFile()'
  collect2: error: ld returned 1 exit status

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: openexr 2.3.0-6build1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Mar 27 15:58:19 2020
  ErrorMessage: installed openexr package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-11-27 (121 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: openexr
  Title: package openexr 2.3.0-6build1 failed to install/upgrade: installed 
openexr package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~

[Desktop-packages] [Bug 1869513] [NEW] package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1

2020-03-28 Thread Ben Fraj Salim
Public bug reported:

/usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by 
/usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or 
-rpath-link)
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::ChannelList::insert(char const*, Imf_2_2::Channel const&)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::hasChromaticities(Imf_2_2::Header const&)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::InputFile::readPixels(int, int)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::InputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::channels() const'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::InputFile::InputFile(char const*, int)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::FrameBuffer::insert(char const*, Imf_2_2::Slice const&)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::chromaticities(Imf_2_2::Header const&)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::globalThreadCount()'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::InputFile::header() const'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::OutputFile::writePixels(int)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Channel::Channel(Imf_2_2::PixelType, int, int, bool)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::FrameBuffer::begin()'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Slice::Slice(Imf_2_2::PixelType, char*, unsigned long, unsigned long, 
int, int, double, bool, bool)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::OutputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::dataWindow() const'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::channels()'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::~Header()'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::OutputFile::OutputFile(char const*, Imf_2_2::Header const&, int)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::ChannelList::findChannel(char const*) const'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::FrameBuffer::end()'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Header::Header(int, int, float, Imath_2_2::Vec2 const&, float, 
Imf_2_2::LineOrder, Imf_2_2::Compression)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::Chromaticities::Chromaticities(Imath_2_2::Vec2 const&, 
Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&, 
Imath_2_2::Vec2 const&)'
/usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to 
`Imf_2_2::OutputFile::~OutputFile()'
collect2: error: ld returned 1 exit status

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: openexr 2.3.0-6build1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Fri Mar 27 15:58:19 2020
ErrorMessage: installed openexr package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2019-11-27 (121 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  2.0.1
SourcePackage: openexr
Title: package openexr 2.3.0-6build1 failed to install/upgrade: installed 
openexr package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package openexr 2.3.0-6build1 failed to install/upgrade: installed
  openexr package post-installation script subprocess returned error
  exit status 1

Status in openexr package in Ubuntu:
  New

Bug description:
  /usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by 
/usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or 
-rpath-link)

[Desktop-packages] [Bug 1869511] Re: package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menub

2020-03-28 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade:
  trying to overwrite
  
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
  which is also in package libreoffice-common 1:6.4.0-0ubuntu7

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Unable to update base Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-math 1:6.4.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Sat Mar 28 18:58:36 2020
  DuplicateSignature:
   package:libreoffice-math:1:6.4.0-0ubuntu7
   Unpacking libreoffice-math (1:6.4.2-0ubuntu1) over (1:6.4.0-0ubuntu7) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-aD6jGo/188-libreoffice-math_1%3a6.4.2-0ubuntu1_amd64.deb 
(--unpack):
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  InstallationDate: Installed on 2020-03-18 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: libreoffice
  Title: package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869511] [NEW] package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/men

2020-03-28 Thread Hans Hinnekint
Public bug reported:

Unable to update base Ubuntu

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libreoffice-math 1:6.4.0-0ubuntu7
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
Date: Sat Mar 28 18:58:36 2020
DuplicateSignature:
 package:libreoffice-math:1:6.4.0-0ubuntu7
 Unpacking libreoffice-math (1:6.4.2-0ubuntu1) over (1:6.4.0-0ubuntu7) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-aD6jGo/188-libreoffice-math_1%3a6.4.2-0ubuntu1_amd64.deb 
(--unpack):
  trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
InstallationDate: Installed on 2020-03-18 (10 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: /usr/bin/python3.8, Python 3.8.2, unpackaged
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  2.0.1
SourcePackage: libreoffice
Title: package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal package-conflict

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

Title:
  package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade:
  trying to overwrite
  
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
  which is also in package libreoffice-common 1:6.4.0-0ubuntu7

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Unable to update base Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-math 1:6.4.0-0ubuntu7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Sat Mar 28 18:58:36 2020
  DuplicateSignature:
   package:libreoffice-math:1:6.4.0-0ubuntu7
   Unpacking libreoffice-math (1:6.4.2-0ubuntu1) over (1:6.4.0-0ubuntu7) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-aD6jGo/188-libreoffice-math_1%3a6.4.2-0ubuntu1_amd64.deb 
(--unpack):
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  ErrorMessage: trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  InstallationDate: Installed on 2020-03-18 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  2.0.1
  SourcePackage: libreoffice
  Title: package libreoffice-math 1:6.4.0-0ubuntu7 failed to install/upgrade: 
trying to overwrite 
'/usr/lib/libreoffice/share/config/soffice.cfg/modules/smath/menubar/menubar.xml',
 which is also in package libreoffice-common 1:6.4.0-0ubuntu7
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869390] Re: Minimized windows appears behind focused on clicking dropdown menu

2020-03-28 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1868990 ***
https://bugs.launchpad.net/bugs/1868990

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

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

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

Title:
  Minimized windows appears behind focused on clicking dropdown menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  It's happening to me in GNOME. I don't know if it would occur in KDE,
  Xfce, Budgie...

  When I click in a dropdown menu (example that do this: Sound device
  picker in gnome-control-center, example that don't: the hamburger menu
  in nautilus/terminal) the minimized windows un-minimize and appear
  behind the focused window, although you can't control most of the
  window (maximize and close works, clicking the icon in dock makes it
  usable).

  Steps to reproduce:

  1. Minimize all windows
  2. Open gnome-control-panel
  3. Go to Appearance, for example.
  4. Click a drop-down i.e. dock position.

  Maximizing the window makes it maximize but minimize at the same time.
  Closing the window works. Minimize and the rest of the window simply
  doesn't work.

  Using:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  I have NVIDIA proprietary drivers (440.64).

  What I expect:
  Normal behavior, not to get the minimize window behind the focused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 16:53:38 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-12 (15 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869501] Re: Bluetooth status in the Unity menu bar does not always match status in system settings

2020-03-28 Thread Khurshid Alam
That's indicator-bluetooth. So not a u-c-c bug. Also the issue could be
with gnome-bluetooth since it works fine on my machine.

Your error shows

"Failed to set mode: Blocked through rfkill (0x12) "...so the hardware
is blocking it. Try running "sudo rfkill unblock all" but you may have
to re-run it after each boot.

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

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

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

Title:
  Bluetooth status in the Unity menu bar does not always match status in
  system settings

Status in bluez package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  When no Bluetooth device is connected and I turn off Bluetooth with
  the switch in the menu of the notification icon, the Bluetooth status
  in System Settings app is still "on" however Bluetooth seems to be
  off.

  Also, when Bluetooth is turned on, the status of a paired device may
  show "connection on" in the notification icon menu when it is actually
  not connected, as System Settings do show correctly. In this case I
  have to switch off and on again if I want to activate the connection.

  Also, I can not switch the connection to a paired device on or off
  with the System Settings app. The switches are grey and I can not
  click them, however they do always show the correct status.

  Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop

  Info:

  unity: 7.5.0+19.10.20190924-0ubuntu1
  unity-control-center: 15.04.0+19.10.20190921-0ubuntu1

  service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago
   Docs: man:bluetoothd(8)
   Main PID: 1035 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 Memory: 3.5M
 CGroup: /system.slice/bluetooth.service
 └─1035 /usr/lib/bluetooth/bluetoothd

  Mär 28 14:17:39 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd0: fd(22) ready
  Mär 28 16:46:32 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
  Mär 28 16:49:02 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd1: fd(22) ready
  Mär 28 16:49:22 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
  Mär 28 16:50:05 Abook bluetoothd[1035]: Control: Refusing unexpected connect
  Mär 28 16:50:08 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd2: fd(22) ready
  Mär 28 16:53:38 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
  Mär 28 16:58:41 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
  Mär 28 16:59:23 Abook bluetoothd[1035]: Control: Refusing unexpected connect
  Mär 28 16:59:25 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd3: fd(22) ready

  Bluetooth device:
  T:  Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#=  6 Spd=12  MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0029 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Mar 28 16:53:08 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-20 (68 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869390] Re: Minimized windows appears behind focused on clicking dropdown menu

2020-03-28 Thread Ljiljan Veselinovic
*** This bug is a duplicate of bug 1868990 ***
https://bugs.launchpad.net/bugs/1868990

I am using Ubuntu 20.04 Development Branch. I have experienced something
similar. When you minimize one program's window, you cannot click on the
window that is currently showed (i.e. the window that was under the
minimized window). In order to activate it, you need to go to Activities
or click on that application's icon on Ubuntu dock. For example, you
open Files, LibreOffice and Google Chrome (in this order). You minimize
Google Chrome, and then you cannot click on LibreOffice unless you click
on the LibreOffice icon on Ubuntu dock.

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

Title:
  Minimized windows appears behind focused on clicking dropdown menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  It's happening to me in GNOME. I don't know if it would occur in KDE,
  Xfce, Budgie...

  When I click in a dropdown menu (example that do this: Sound device
  picker in gnome-control-center, example that don't: the hamburger menu
  in nautilus/terminal) the minimized windows un-minimize and appear
  behind the focused window, although you can't control most of the
  window (maximize and close works, clicking the icon in dock makes it
  usable).

  Steps to reproduce:

  1. Minimize all windows
  2. Open gnome-control-panel
  3. Go to Appearance, for example.
  4. Click a drop-down i.e. dock position.

  Maximizing the window makes it maximize but minimize at the same time.
  Closing the window works. Minimize and the rest of the window simply
  doesn't work.

  Using:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  I have NVIDIA proprietary drivers (440.64).

  What I expect:
  Normal behavior, not to get the minimize window behind the focused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 16:53:38 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-12 (15 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869288] Re: "Privacy" tab in gnome-control-center is not findable

2020-03-28 Thread Bruno Nocera Zanette
Thanks for the quick fix, Gunnar!

I installed the pkg from your ppa and i now i get as result the
categories contained in Privacy tab, just as you said.

It's not quite the same behavior as the other tabs and it may confuse a
little bit, but i think it's quite easy to get the idea. I believe it's
a great improvement of what it was.

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

Title:
  "Privacy" tab in gnome-control-center is not findable

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Searching for "Privacy" using gnome-control-center search bar returns
  the  "Search" tab instead of the "Privacy" tab. The same thing happens
  with Gnome Shell Search.

  For all the other tab names of gnome-control-center it works as
  expected, including Privacy's sub tabs. I've tested using EN and PT-BR
  languages, and it happens in both.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Uname: Linux 5.4.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 23:42:26 2020
  InstallationDate: Installed on 2020-03-08 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by sna

2020-03-28 Thread Naël
Thanks for the insight Brian. I indeed rarely use the graphical update
manager. I'm starting to suspect I should manually install the snap-
store and uninstall the gnome-{calculator,logs,characters} snaps to get
in sync with the development release.

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

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

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

Title:
  gnome-{calculator,logs,characters} snaps not removed after the
  equivalent APT packages are installed on 20.04, and gnome-software APT
  package not replaced by snap-store

Status in gnome-calculator package in Ubuntu:
  New
Status in gnome-characters package in Ubuntu:
  New
Status in gnome-logs package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  I'm trialing the development release of Ubuntu 20.04, installed in
  December and kept up-to-date by regularly running apt full-upgrade.

  I understand from [1] that 20.04 will ship
  gnome-{calculator,logs,characters} as APT packages rather than snap
  apps, and gnome-software as a snap app (called snap-store) rather than
  an APT package.

  Following an apt full-upgrade in late February, I now have:

  * both the snap and the APT versions of gnome-{calculator,logs,characters}
  * still only the APT version of gnome-software, no snap-store

  Is this normal? A user in the #ubuntu+1 IRC channel reports that a
  fresh install of the development release:

  * only features the APT versions of gnome-{calculator,logs,characters}
  * features the snap-store (but also the APT version of gnome-software)

  Are users of older installs of the development release supposed to
  manually uninstall the snap versions of
  gnome-{calculator,logs,characters} and manually install the snap-
  store?

  [1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
  remove-for-snap-snap-store/14542

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

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


[Desktop-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-03-28 Thread Gunnar Hjalmarsson
** Information type changed from Private to Public

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  New

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1869501] [NEW] Bluetooth status in the Unity menu bar does not always match status in system settings

2020-03-28 Thread w-sky
Public bug reported:

When no Bluetooth device is connected and I turn off Bluetooth with the
switch in the menu of the notification icon, the Bluetooth status in
System Settings app is still "on" however Bluetooth seems to be off.

Also, when Bluetooth is turned on, the status of a paired device may
show "connection on" in the notification icon menu when it is actually
not connected, as System Settings do show correctly. In this case I have
to switch off and on again if I want to activate the connection.

Also, I can not switch the connection to a paired device on or off with
the System Settings app. The switches are grey and I can not click them,
however they do always show the correct status.

Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop

Info:

unity: 7.5.0+19.10.20190924-0ubuntu1
unity-control-center: 15.04.0+19.10.20190921-0ubuntu1

service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago
 Docs: man:bluetoothd(8)
 Main PID: 1035 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4915)
   Memory: 3.5M
   CGroup: /system.slice/bluetooth.service
   └─1035 /usr/lib/bluetooth/bluetoothd

Mär 28 14:17:39 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd0: fd(22) ready
Mär 28 16:46:32 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
Mär 28 16:49:02 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd1: fd(22) ready
Mär 28 16:49:22 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
Mär 28 16:50:05 Abook bluetoothd[1035]: Control: Refusing unexpected connect
Mär 28 16:50:08 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd2: fd(22) ready
Mär 28 16:53:38 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
Mär 28 16:58:41 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
Mär 28 16:59:23 Abook bluetoothd[1035]: Control: Refusing unexpected connect
Mär 28 16:59:25 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd3: fd(22) ready

Bluetooth device:
T:  Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#=  6 Spd=12  MxCh= 0
D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0029 Rev=00.01
C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Mar 28 16:53:08 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-01-20 (68 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Bluetooth status in the Unity menu bar does not always match status in
  system settings

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

Bug description:
  When no Bluetooth device is connected and I turn off Bluetooth with
  the switch in the menu of the notification icon, the Bluetooth status
  in System Settings app is still "on" however Bluetooth seems to be
  off.

  Also, when Bluetooth is turned on, the status of a paired device may
  show "connection on" in the notification icon menu when it is actually
  not connected, as System Settings do show correctly. In this case I
  have to switch off and on again if I want to activate the connection.

  Also, I can not switch the connection to a paired device on or off
  with the System Settings app. The switches are grey and I can not
  click them, however they do always show the correct status.

  Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop

  Info:

  unity: 7.5.0+19.10.20190924-0ubuntu1
  unity-control-center: 15.04.0+19.10.20190921-0ubuntu1

  service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago
   Docs: man:bluetoothd(8)
   Main PID: 1035 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 Memory: 3.5M
 CGroup: /system.slice/bluetooth.service
 └─1035 /usr/lib/bluetoot

[Desktop-packages] [Bug 1869485] Re: mobile internet G4 not possible

2020-03-28 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1869485

Title:
  mobile internet G4 not possible

Status in xorg package in Ubuntu:
  New

Bug description:
  no connecting to the mobile internet G4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Mar 28 13:37:17 2020
  DistUpgraded: 2018-08-18 11:06:47,630 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1043:14e2]
 Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1043:14e2]
  InstallationDate: Installed on 2014-08-29 (2037 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: ASUSTeK Computer Inc. X51L
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=4d7525b3-75a6-483e-8dad-b34a49f9c185 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (588 days ago)
  dmi.bios.date: 02/27/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X51L
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr205:bd02/27/2008:svnASUSTeKComputerInc.:pnX51L:pvr1.0:rvnASUSTeKComputerInc.:rnX51L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: X51L
  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.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Aug 18 07:19:25 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5460 
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Desktop-packages] [Bug 1869288] Re: "Privacy" tab in gnome-control-center is not findable

2020-03-28 Thread Gunnar Hjalmarsson
Attached please find the debdiff.

One problem with this solution is that it breaks existing translations
of the affected Keywords strings. Notifying the translators may
compensate for that a bit.

Sebastien: Any thoughts on the idea?

** Patch added: "gnome-control-center_privacy-keyword.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869288/+attachment/5342534/+files/gnome-control-center_privacy-keyword.debdiff

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

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

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: patch regression-release

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

Title:
  "Privacy" tab in gnome-control-center is not findable

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Searching for "Privacy" using gnome-control-center search bar returns
  the  "Search" tab instead of the "Privacy" tab. The same thing happens
  with Gnome Shell Search.

  For all the other tab names of gnome-control-center it works as
  expected, including Privacy's sub tabs. I've tested using EN and PT-BR
  languages, and it happens in both.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Uname: Linux 5.4.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 23:42:26 2020
  InstallationDate: Installed on 2020-03-08 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869288] Re: "Privacy" tab in gnome-control-center is not findable

2020-03-28 Thread Gunnar Hjalmarsson
Thanks for your report!

If I understand it correctly, this is because "Privacy" is no longer a
panel, but just a category where privacy related panels are shown. One
possible way to improve it is to add the "privacy" keyword to the
.desktop files of the applicable panels. I prepared a debdiff which does
that, and the attached image shows the result.

For the case you want to test, I also uploaded a modified version of
gnome-control-center to this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-control-center

** Attachment added: "privacy-keyword.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869288/+attachment/5342533/+files/privacy-keyword.png

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

Title:
  "Privacy" tab in gnome-control-center is not findable

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Searching for "Privacy" using gnome-control-center search bar returns
  the  "Search" tab instead of the "Privacy" tab. The same thing happens
  with Gnome Shell Search.

  For all the other tab names of gnome-control-center it works as
  expected, including Privacy's sub tabs. I've tested using EN and PT-BR
  languages, and it happens in both.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Uname: Linux 5.4.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 23:42:26 2020
  InstallationDate: Installed on 2020-03-08 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1869485] [NEW] mobile internet G4 not possible

2020-03-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

no connecting to the mobile internet G4

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux 4.15.0-91-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Mar 28 13:37:17 2020
DistUpgraded: 2018-08-18 11:06:47,630 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1043:14e2]
   Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1043:14e2]
InstallationDate: Installed on 2014-08-29 (2037 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: ASUSTeK Computer Inc. X51L
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=4d7525b3-75a6-483e-8dad-b34a49f9c185 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-08-18 (588 days ago)
dmi.bios.date: 02/27/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X51L
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr205:bd02/27/2008:svnASUSTeKComputerInc.:pnX51L:pvr1.0:rvnASUSTeKComputerInc.:rnX51L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: X51L
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.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Aug 18 07:19:25 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5460 
 vendor CMO
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: apport-bug bionic i386 ubuntu
-- 
mobile internet G4 not possible
https://bugs.launchpad.net/bugs/1869485
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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


[Desktop-packages] [Bug 1868116] Re: QEMU monitor no longer works

2020-03-28 Thread Jakub Wilk
** Bug watch added: Debian Bug tracker #954266
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954266

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

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

Title:
  QEMU monitor no longer works

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in qemu package in Debian:
  Unknown

Bug description:
  Repro:
  VTE
  $ meson _build && ninja -C _build && ninja -C _build install

  qemu:
  $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user 
--disable-linux-user --disable-docs --disable-guest-agent --disable-sdl 
--enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt 
--disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi 
--disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir 
--disable-seccomp --disable-glusterfs --disable-tpm --disable-numa 
--disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs 
--disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma 
--disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock 
--disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user 
--disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs 
--disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat 
--disable-qed --disable-parallels --disable-sheepdog --disable-avx2 
--disable-nettle --disable-gnutls --disable-capstone --disable-tools 
--disable-libpmem --disable-iconv --disable-cap-ng
  $ make

  Test:
  $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH 
./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive 
media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso
  - switch to monitor with CTRL+ALT+2
  - try to enter something

  Affects head of both usptream git repos.

  
  --- original bug ---

  It was observed that the QEMU console (normally accessible using
  Ctrl+Alt+2) accepts no input, so it can't be used. This is being
  problematic because there are cases where it's required to send
  commands to the guest, or key combinations that the host would grab
  (as Ctrl-Alt-F1 or Alt-F4).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: qemu 1:4.2-3ubuntu2
  Uname: Linux 5.6.0-rc6+ x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 12:16:31 2020
  Dependencies:

  InstallationDate: Installed on 2017-06-13 (1009 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID PIDPPID %CPU COMMAND
   qemu-system-x86 Sl+   1000  1000   34275   25235 29.2 qemu-system-x86_64 -m 
4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel 
kvm -device nec-usb-xhci -serial vc -serial stdio -hda 
/home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio
   kvm-nx-lpage-re S0 0   34284   2  0.0 [kvm-nx-lpage-re]
   kvm-pit/34275   S0 0   34286   2  0.0 [kvm-pit/34275]
  MachineType: LENOVO 80UG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 
zswap.enabled=1 zswap.zpool=z3fold 
resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M 
usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y 
scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 
nbd.max_part=63
  SourcePackage: qemu
  UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240

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

-- 
Mailing list: https://launchpad.net/~de

[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices

2020-03-28 Thread Martin Büchler
Ok, I forgot another crucial step to mention:

after installing the libraries, you have to run

  sudo ldconfig -v

to move the new libs in /usr/local/lib to the front

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

Title:
  Need updated libimobiledevice and dependencies to access iOS 13
  devices

Status in libimobiledevice package in Ubuntu:
  Incomplete
Status in libplist package in Ubuntu:
  Confirmed
Status in libusbmuxd package in Ubuntu:
  Confirmed
Status in usbmuxd package in Ubuntu:
  Confirmed

Bug description:
  iOS 13 devices require updated libimobiledevice, libusbmuxd and
  usbmuxd to work correctly. Without the updates, the device appears to
  be accessible but it's impossible to copy files to the devices.

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

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


[Desktop-packages] [Bug 1848335] Re: xdg-open (and others) don't handle spaces in directory names properly

2020-03-28 Thread Amr Ibrahim
This is fixed in xdg-utils 1.1.3-2. A merge request has been filed LP:
#1869492.

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

Title:
  xdg-open (and others) don't handle spaces in directory names properly

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  xdg-utils: Installed: 1.1.2-1ubuntu2.3

  Environment:
  Shell: bash/fish (happens in both)
  DE: i3
  env:
  
XDG_DATA_DIRS=/home/barnex/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share/i3:/home/barnex/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
  XDG_CONFIG_DIRS=/etc/xdg/xdg-i3:/etc/xdg
   
  What I did:
  xdg-open "http://reddit.com"; # while having a specific directory structure

  What I expected to happen:
  Open a new tab/window of my browser with the correct URL.

  What happened instead:
  xdg-open froze, and eventually crashed.

  I believe this issue in upstream caused the erratic behavior:
  https://gitlab.freedesktop.org/xdg/xdg-utils/issues/131

  xdg-utils seems to recursively look through directories for the
  .desktop file. In my setup this path includes a directory:

  "/home/barnex/.local/share/applications//wine//Programs//Zone.com
  Deluxe Games/"

  Instead of correctly looking into this directory, the next
  search_desktop_file call goes into the "/home/barnex/Games" - a
  directory outside of the search path.

  /home/barnex/Games in turn has a directory "/home/barnex/Games//epic-
  games-store//dosdevices//c://users//barnex//My Music/" - which again
  has a space, and thus makes the xdg-open go to "/home/barnex/Music" -
  another directory outside of my search path.

  In /home/barnex/Music there's a directory called ' The Final Boss -
  James Harmon - [Ambient - Breakbeat - Lo-Fi -Electronica] [2011]' -
  this just causes an infinite loop of adding more slashes to the path,
  resulting in calls like:

  + search_desktop_file chromium-browser.desktop
  
Music
  The Final Boss - James Harmon - [Ambient - Breakbeat - Lo-Fi
  -Electronica] [2011]/ http://reddit.com

  This eventually leads to a crash.

  Running 'xdg-settings get default-url-scheme-handler' with no
  arguments caused a similar behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xdg-utils 1.1.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Wed Oct 16 13:45:35 2019
  InstallationDate: Installed on 2016-11-20 (1059 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to bionic on 2019-01-23 (265 days ago)

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

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


[Desktop-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264

2020-03-28 Thread Joseph Yasi
No one is asking you to send them a fix. Since you are experiencing the
issue on a stable release, you should let Mesa know that the issue
exists in stable releases, and ask them to provide the fix for the
stable 20.0.x branch.

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

Title:
  Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i
  H.264

Status in mesa package in Ubuntu:
  New

Bug description:
  uname -a
  Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

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

  inxi -G
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 
240/340 OEM]
 Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 
9.0.0) version: 4.5 Mesa 19.2.8

  For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen
  (top) compressed image.

  To solve the default, i have to revert via synaptic the package mesa-
  va-driver to 19.0.8.

  Other solution is to take nighty builds as complete mesa package via : 
  https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers   that works 
too and is at mesa 20.1 git

  Please correct the problem to the official Ubuntu repos.

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

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


[Desktop-packages] [Bug 1869492] [NEW] Merge xdg-utils 1.1.3-2 (main) from Debian unstable (main)

2020-03-28 Thread Amr Ibrahim
Public bug reported:

Please merge xdg-utils 1.1.3-2 (main) from Debian unstable (main)

Sorry, I cannot work on this merge myself. It fixes LP: #1848335.

These Ubuntu changes are now in Debian, or not needed anymore, and can be 
dropped:
  * Use perl's decode() to ensure we don't pass invalid UTF-8 to D-Bus,
as doing so triggers an assertion from libdbus which makes us crash.
LP: #1743216 (Debian #910070, Upstream #108121)
  * Drop lp779156-lubuntu.diff:
- Lubuntu no longer uses LXDE and Sylpheed.
  * Drop CVE-2017-18266*.patch:
- The fixes were applied upstream.
  * Drop proper-lxqt-handling.patch:
- Proper LXQt support was merged upstream.

Except this change, which is not in Debian:
  - Add debian/xdg-utils.links:
+ Symlink /usr/bin/xdg-open to /usr/bin/browse (LP: #1624022)

Changelog entries since current focal version 1.1.3-1ubuntu2:

xdg-utils (1.1.3-2) unstable; urgency=medium

  [ Debian Janitor ]
  * Bump debhelper from old 10 to 12.
  * Set debhelper-compat version in Build-Depends.
  * Add upstream metadata info.

  [ Nicholas Guriev ]
  * Shift debian/NEWS content to the left.
  * Set Rules-Requires-Root: no in debian/control.
  * Obey the nocheck build option.
  * Bump Standards-Version to 4.5.0.
  * Add machine readable debian/copyright file.
  * Now uscan(1) watches FreeDesktop GitLab.
  * Add trailing new line into auto-generated patch header.
  * Drop redundant invocation dh_installchangelogs in debian/rules.
  * Install release notes as NEWS file in according P. 12.7 of the Debian
policy.
  * xdg-mime: Create config directory if it does not exist yet.
Closes: #652038.

  [ Rex Dieter ]
  * xdg-open: Do better pcmanfm check, fix AND operator. Closes: #908760,
Upstream: BR106636, BR106161.

  [ Alberto Salvia Novella ]
  * xdg-email: Support for Deepin.

  [ Mario van der Linde ]
  * Enable Cinnamon screensaver for XDG aware desktop environments (e.g. LXQt).

  [ Iain Lane ]
  * xdg-screensaver: Sanitise window name before sending it over the bus.
Closes: #910070, LP: #1743216, Upstream: BR108121.

  [ Andrea Tarocchi ]
  * xdg-open: correct handling directories with spaces in the name.
LP: #1848335, Upstream: #166.

 -- Nicholas Guriev   Fri, 13 Mar 2020 19:17:44 +0300

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Merge xdg-utils 1.1.3-2 (main) from Debian unstable (main)

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Please merge xdg-utils 1.1.3-2 (main) from Debian unstable (main)

  Sorry, I cannot work on this merge myself. It fixes LP: #1848335.

  These Ubuntu changes are now in Debian, or not needed anymore, and can be 
dropped:
* Use perl's decode() to ensure we don't pass invalid UTF-8 to D-Bus,
  as doing so triggers an assertion from libdbus which makes us crash.
  LP: #1743216 (Debian #910070, Upstream #108121)
* Drop lp779156-lubuntu.diff:
  - Lubuntu no longer uses LXDE and Sylpheed.
* Drop CVE-2017-18266*.patch:
  - The fixes were applied upstream.
* Drop proper-lxqt-handling.patch:
  - Proper LXQt support was merged upstream.

  Except this change, which is not in Debian:
- Add debian/xdg-utils.links:
  + Symlink /usr/bin/xdg-open to /usr/bin/browse (LP: #1624022)

  Changelog entries since current focal version 1.1.3-1ubuntu2:

  xdg-utils (1.1.3-2) unstable; urgency=medium

[ Debian Janitor ]
* Bump debhelper from old 10 to 12.
* Set debhelper-compat version in Build-Depends.
* Add upstream metadata info.

[ Nicholas Guriev ]
* Shift debian/NEWS content to the left.
* Set Rules-Requires-Root: no in debian/control.
* Obey the nocheck build option.
* Bump Standards-Version to 4.5.0.
* Add machine readable debian/copyright file.
* Now uscan(1) watches FreeDesktop GitLab.
* Add trailing new line into auto-generated patch header.
* Drop redundant invocation dh_installchangelogs in debian/rules.
* Install release notes as NEWS file in according P. 12.7 of the Debian
  policy.
* xdg-mime: Create config directory if it does not exist yet.
  Closes: #652038.

[ Rex Dieter ]
* xdg-open: Do better pcmanfm check, fix AND operator. Closes: #908760,
  Upstream: BR106636, BR106161.

[ Alberto Salvia Novella ]
* xdg-email: Support for Deepin.

[ Mario van der Linde ]
* Enable Cinnamon screensaver for XDG aware desktop environments (e.g. 
LXQt).

[ Iain Lane ]
* xdg-screensaver: Sanitise window name before sending it over the bus.
  Closes: #910070, LP: #1743216, Upstream: BR108121.

[ Andrea Tarocchi ]
* xdg-open: correct handling directories with spaces in the name.
  LP: #1848335, Upstream: #166.

   -- Nicholas Guriev   Fri, 13 Mar 2020 19:17:44 +03

[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices

2020-03-28 Thread Martin Büchler
In previous comment

  sudo apt-get install

should read

  sudo apt-get install libusb-1.0-0-dev

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

Title:
  Need updated libimobiledevice and dependencies to access iOS 13
  devices

Status in libimobiledevice package in Ubuntu:
  Incomplete
Status in libplist package in Ubuntu:
  Confirmed
Status in libusbmuxd package in Ubuntu:
  Confirmed
Status in usbmuxd package in Ubuntu:
  Confirmed

Bug description:
  iOS 13 devices require updated libimobiledevice, libusbmuxd and
  usbmuxd to work correctly. Without the updates, the device appears to
  be accessible but it's impossible to copy files to the devices.

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

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


[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices

2020-03-28 Thread Martin Büchler
Followed the advice of Jackfritt at
https://github.com/libimobiledevice/libimobiledevice/issues/903

I had to additionally do the same for usbmuxd:

sudo apt-get install

git clone https://github.com/libimobiledevice/usbmuxd.git
./autogen.sh
make
sudo make install

then reboot.

Verified for Ubuntu 18.04.4 LTS

** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #903
   https://github.com/libimobiledevice/libimobiledevice/issues/903

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

Title:
  Need updated libimobiledevice and dependencies to access iOS 13
  devices

Status in libimobiledevice package in Ubuntu:
  Incomplete
Status in libplist package in Ubuntu:
  Confirmed
Status in libusbmuxd package in Ubuntu:
  Confirmed
Status in usbmuxd package in Ubuntu:
  Confirmed

Bug description:
  iOS 13 devices require updated libimobiledevice, libusbmuxd and
  usbmuxd to work correctly. Without the updates, the device appears to
  be accessible but it's impossible to copy files to the devices.

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

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


[Desktop-packages] [Bug 1869488] Re: when launching new app all windows of opened apps appear but are not controllable

2020-03-28 Thread db429
** Package changed: ubuntu => mutter (Ubuntu)

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

Title:
  when launching new app all windows of opened apps appear but are not
  controllable

Status in mutter package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  all available updates installed at time of reporting

   every now and then when I open an Application, all (minimized)
  windows of other running applications appear on the screen and the
  interaction with them is impossible.

   neither the window control buttons nor the window content is reacting
  on mouse interaction - the whole window is in non-focus mode. only
  after clicking on the panel icon of said window to minimize and reopen
  an interaction is possible.

   i have no direct clue where to start further investigation, yet I
  would guess it be an bug in mutter/clutter, x.org or the nvidia-driver

   this is clearly a show stopper!

   i will try to see if this annoyance appears with wayland and/or
  noveau too, yet I'd appreciate any guidance in helping to fix this bug

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

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


[Desktop-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264

2020-03-28 Thread knossos456
Ok for Mesa 20.1
Concerning Gitlab, I can't send them a fix, I'm not a developer.
I'm still available for testing.
I will tell them for the bug with 20.0.2-1ubuntu1 and my hardware

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

Title:
  Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i
  H.264

Status in mesa package in Ubuntu:
  New

Bug description:
  uname -a
  Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

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

  inxi -G
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 
240/340 OEM]
 Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 
9.0.0) version: 4.5 Mesa 19.2.8

  For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen
  (top) compressed image.

  To solve the default, i have to revert via synaptic the package mesa-
  va-driver to 19.0.8.

  Other solution is to take nighty builds as complete mesa package via : 
  https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers   that works 
too and is at mesa 20.1 git

  Please correct the problem to the official Ubuntu repos.

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

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


[Desktop-packages] [Bug 1869481] Re: [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

2020-03-28 Thread Reshad Dernjani
Also see:

$ dmesg | grep -i "error\|fail\|warn"

[0.525533] Initramfs unpacking failed: Decoding failed
[0.602518] i8042: Warning: Keylock active
[0.638992] RAS: Correctable Errors collector initialized.
[2.213839] EXT4-fs (nvme0n1p5): re-mounted. Opts: errors=remount-ro
[2.612061] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-cc-a0-52.ucode failed with error -2
[2.612082] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-cc-a0-51.ucode failed with error -2
[2.612097] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-cc-a0-50.ucode failed with error -2
[2.612112] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-cc-a0-49.ucode failed with error -2
[2.868491] thermal thermal_zone8: failed to read out thermal zone (-61)
[   13.807541] psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
[   14.291742] psmouse serio1: Failed to enable mouse on isa0060/serio1
[   18.795556] psmouse serio1: Failed to enable mouse on isa0060/serio1

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

Title:
  [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi everyone!

  I have Samsung Q90R (7.1 Atmos) soundbar connected to my secondary display.
  The display is connected to my notebook though the soundbar and all sound 
options are displayed in the audio settings.
  Sound through hdmi/displayport was working few days ago. All other sound 
options (internal, headset) are still working.

  (Ubuntu does a great job converting everything to Dolby Atmos 7.1!)

  Kind regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.5.13-050513-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reshadde   2381 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 11:53:23 2020
  InstallationDate: Installed on 2020-03-21 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Only some of outputs are working
  Title: [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1869488] [NEW] when launching new app all windows of opened apps appear but are not controllable

2020-03-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Description:Ubuntu Focal Fossa (development branch)
Release:20.04

all available updates installed at time of reporting

 every now and then when I open an Application, all (minimized) windows
of other running applications appear on the screen and the interaction
with them is impossible.

 neither the window control buttons nor the window content is reacting
on mouse interaction - the whole window is in non-focus mode. only after
clicking on the panel icon of said window to minimize and reopen an
interaction is possible.

 i have no direct clue where to start further investigation, yet I would
guess it be an bug in mutter/clutter, x.org or the nvidia-driver

 this is clearly a show stopper!

 i will try to see if this annoyance appears with wayland and/or noveau
too, yet I'd appreciate any guidance in helping to fix this bug

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

-- 
when launching new app all windows of opened apps appear but are not 
controllable
https://bugs.launchpad.net/bugs/1869488
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mutter in Ubuntu.

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


[Desktop-packages] [Bug 1869481] Re: [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

2020-03-28 Thread Reshad Dernjani
Switching kernel to Linux 5.4.28-050428-generic does not resolve the
issue.

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

Title:
  [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi everyone!

  I have Samsung Q90R (7.1 Atmos) soundbar connected to my secondary display.
  The display is connected to my notebook though the soundbar and all sound 
options are displayed in the audio settings.
  Sound through hdmi/displayport was working few days ago. All other sound 
options (internal, headset) are still working.

  (Ubuntu does a great job converting everything to Dolby Atmos 7.1!)

  Kind regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.5.13-050513-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reshadde   2381 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 11:53:23 2020
  InstallationDate: Installed on 2020-03-21 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Only some of outputs are working
  Title: [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1869481] Re: [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

2020-03-28 Thread Reshad Dernjani
Found following error messages in the logs:

1. Unable to load libkmod resources: error -12
2. snd_hda_codec_hdmi hdaudioC0D2: HDMI: audio coding xtype 11 not expected

I am running 20.04 on a separate partition. Grub menu still allows me to switch 
between 20.04 and 19.10. 
The /boot partition is mounted.

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

Title:
  [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi everyone!

  I have Samsung Q90R (7.1 Atmos) soundbar connected to my secondary display.
  The display is connected to my notebook though the soundbar and all sound 
options are displayed in the audio settings.
  Sound through hdmi/displayport was working few days ago. All other sound 
options (internal, headset) are still working.

  (Ubuntu does a great job converting everything to Dolby Atmos 7.1!)

  Kind regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.5.13-050513-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reshadde   2381 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 11:53:23 2020
  InstallationDate: Installed on 2020-03-21 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Only some of outputs are working
  Title: [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1869481] [NEW] [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

2020-03-28 Thread Reshad Dernjani
Public bug reported:

Hi everyone!

I have Samsung Q90R (7.1 Atmos) soundbar connected to my secondary display.
The display is connected to my notebook though the soundbar and all sound 
options are displayed in the audio settings.
Sound through hdmi/displayport was working few days ago. All other sound 
options (internal, headset) are still working.

(Ubuntu does a great job converting everything to Dolby Atmos 7.1!)

Kind regards!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.5.13-050513-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  reshadde   2381 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 28 11:53:23 2020
InstallationDate: Installed on 2020-03-21 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Only some of outputs are working
Title: [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0G2D0W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi everyone!

  I have Samsung Q90R (7.1 Atmos) soundbar connected to my secondary display.
  The display is connected to my notebook though the soundbar and all sound 
options are displayed in the audio settings.
  Sound through hdmi/displayport was working few days ago. All other sound 
options (internal, headset) are still working.

  (Ubuntu does a great job converting everything to Dolby Atmos 7.1!)

  Kind regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.5.13-050513-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reshadde   2381 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 11:53:23 2020
  InstallationDate: Installed on 2020-03-21 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Only some of outputs are working
  Title: [XPS 13 7390, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1868780] Re: [virtio] Xubuntu 20.04 - Blank screen after login

2020-03-28 Thread Mike Glover
Another prevboot file. I left the machine running with the black screen
for longer.

** Attachment added: "prevboot2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868780/+attachment/5342442/+files/prevboot2.txt

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

Title:
  [virtio] Xubuntu 20.04 - Blank screen after login

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Both on Xubuntu 20.04 23rd March and 24th March daily build.
  Using Martin Wimpress QuickEMU setup.
  Installation part of xubuntu is working fine.
  But after install and reboot, you get the login box. I type in the password 
for the user and then just get a black screen and mouse cursor, no other error 
boxes or gui.
  Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only 
on Xubuntu daily builds do I see this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Mar 24 16:40:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
  InstallationDate: Installed on 2020-03-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-03-28 Thread Unathi
I have the same issues on an HP ENVY x360 Convertible 15-dr0xxx. I have
tried about everything I could find online about this issue but the
internal mic still isn't working. :(

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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


[Desktop-packages] [Bug 1869449] Re: Corrupted Model number and Serial number in gnome-disks

2020-03-28 Thread lotuspsychje
Thank you for reporting this bug and make ubuntu better!

Please when filing bugs in ubuntu use ubuntu-bug packagename from terminal
so relavant info gets pulled into the bug and developers can debug a better
way.
You can still pull the info at this stage with: apport-collect 1869449

Thank you!

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

Title:
  Corrupted Model number and Serial number in gnome-disks

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

Bug description:
  When I run the disks program I frequently see the model and serial
  number of the disks I'm working with is corrupted.

  Most often this is with WD drives, but i have seen it with other
  brands

  However when i use GSmartControl theses entries are fine (they model
  number is also reported correctly in GParted).

  I' using gnome-disk-utility 3.34.0 and GSmartControl 1.1.3

  
  Screen grab attached for Disks (on the left) and GSmartControl (right)

  
  Still a very noob at reporting bugs, so apologies if this is the wrong 
forum/method/reporting style/I left information out..

  Happy to supply any other information you need

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

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


[Desktop-packages] [Bug 1869449] Re: Corrupted Model number and Serial number in gnome-disks

2020-03-28 Thread Norbert
** Also affects: gnome-disk-utility (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-mate

** Tags added: eoan

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

Title:
  Corrupted Model number and Serial number in gnome-disks

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

Bug description:
  When I run the disks program I frequently see the model and serial
  number of the disks I'm working with is corrupted.

  Most often this is with WD drives, but i have seen it with other
  brands

  However when i use GSmartControl theses entries are fine (they model
  number is also reported correctly in GParted).

  I' using gnome-disk-utility 3.34.0 and GSmartControl 1.1.3

  
  Screen grab attached for Disks (on the left) and GSmartControl (right)

  
  Still a very noob at reporting bugs, so apologies if this is the wrong 
forum/method/reporting style/I left information out..

  Happy to supply any other information you need

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

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


[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

2020-03-28 Thread Ro$k0
This happen with me in PhpStorm, also snap installed.

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

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

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

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


[Desktop-packages] [Bug 1869470] [NEW] Can't minimize Thunderbird Lightning reminder window

2020-03-28 Thread Dominik
Public bug reported:

Ever since Ubuntu moved back to Gnome from Unity, it's impossible to
minimize the Thunderbird Lightning reminder window. It's really
annoying, the window is always on top of Thunderbird and has to be
constantly moved around to use the program.

Closing the window makes no sense as a) it tends to start syncing the
events with reminders, which can show conflict prompts requiring even
more work from the user and b) the window comes back very quickly. So,
minimize makes the most sense.

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

** Project changed: qlbr => mutter (Ubuntu)

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

Title:
  Can't minimize Thunderbird Lightning reminder window

Status in mutter package in Ubuntu:
  New

Bug description:
  Ever since Ubuntu moved back to Gnome from Unity, it's impossible to
  minimize the Thunderbird Lightning reminder window. It's really
  annoying, the window is always on top of Thunderbird and has to be
  constantly moved around to use the program.

  Closing the window makes no sense as a) it tends to start syncing the
  events with reminders, which can show conflict prompts requiring even
  more work from the user and b) the window comes back very quickly. So,
  minimize makes the most sense.

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

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


[Desktop-packages] [Bug 1869470] [NEW] Can't minimize Thunderbird Lightning reminder window

2020-03-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Ever since Ubuntu moved back to Gnome from Unity, it's impossible to
minimize the Thunderbird Lightning reminder window. It's really
annoying, the window is always on top of Thunderbird and has to be
constantly moved around to use the program.

Closing the window makes no sense as a) it tends to start syncing the
events with reminders, which can show conflict prompts requiring even
more work from the user and b) the window comes back very quickly. So,
minimize makes the most sense.

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

-- 
Can't minimize Thunderbird Lightning reminder window
https://bugs.launchpad.net/bugs/1869470
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mutter in Ubuntu.

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