date:20200718

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1388272

Title:
  Login screen shows different background picture such as set for
  desktop background

Status in shadow package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.10 shows a different background for login screen such as set
  for desktop background. In 14.04 it was working fine. I don't know
  what's the original behavior of 14.10, it may have change since 14.04

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

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

[Touch-packages] [Bug 1879326] Re: DNS resolution ceased to work after update

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  DNS resolution ceased to work after update

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  Hi

  I did a Focal install on 14th of May 2020, could work until in the
  night of 16th of May 2020 and in the morning of the 18th of May 2020 I
  could not resolve domain names anymore. I can ping DNS servers but the
  resolution to IP addresses fails. I have switched on automatic
  installation of security relevant updates.

  I can reproduce the behaviour with a fresh install accepting all the
  updates there are. I did not try to find out which update is the
  cause.

  See the behaviour below where I even have tried to work around by removing 
the DNS server of my router:
  thiemo @ Fujitsu-HO ~ :-( % systemd-resolve --status  
20-05-18 12:54
  Global
 LLMNR setting: no
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 2 (enp0s25)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 139.18.25.33
139.18.25.34
77.59.232.36
62.167.241.5
62.2.107.35
62.2.121.84
62.2.121.88
fd00::7eff:4dff:feaa:2528
2001:638:902:1::10
DNS Domain: ~.
  thiemo @ Fujitsu-HO ~ % host -v myworkspaceinet.post.ch   
20-05-18 12:54
  Trying "myworkspaceinet.post.ch"
  ;; connection timed out; no servers could be reached

  thiemo @ Fujitsu-HO ~ :-( % alias pong
20-05-18 12:55
  pong='ping -c3'
  thiemo @ Fujitsu-HO ~ % pong 139.18.25.33 
20-05-18 12:58
  PING 139.18.25.33 (139.18.25.33) 56(84) bytes of data.
  64 bytes from 139.18.25.33: icmp_seq=1 ttl=246 time=39.9 ms
  64 bytes from 139.18.25.33: icmp_seq=2 ttl=246 time=39.0 ms
  64 bytes from 139.18.25.33: icmp_seq=3 ttl=246 time=39.4 ms

  --- 139.18.25.33 ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2003ms
  rtt min/avg/max/mdev = 39.000/39.431/39.868/0.354 ms

  Kind regards

  Thiemo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon May 18 13:03:40 2020
  InstallationDate: Installed on 2020-05-15 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.178.1 dev enp0s25 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000 
   192.168.178.0/24 dev enp0s25 proto kernel scope link src 192.168.178.33 
metric 100
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE

[Touch-packages] [Bug 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

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

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID

[Touch-packages] [Bug 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

[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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1870442

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

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

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID  TYPE

[Touch-packages] [Bug 1888108] [NEW] Fresh install 20.04

2020-07-18 Thread sdaigle

Public bug reported:

My Graphics are like a slide show.

Its almost as if the display drivers are not installed?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sat Jul 18 22:08:11 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [17aa:30a3]
InstallationDate: Installed on 2020-07-17 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 10AB004DUS
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=cd7df6ea-b877-481a-9eee-6d5e2b5d770a ro quiet splash nomodeset 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: FBKTB9AUS
dmi.board.name: SHARKBAY
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
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:bvnLENOVO:bvrFBKTB9AUS:bd11/13/2015:svnLENOVO:pn10AB004DUS:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvrSDK0E50510WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ThinkCentre M93p
dmi.product.name: 10AB004DUS
dmi.product.sku: LENOVO_MT_10AB
dmi.product.version: ThinkCentre M93p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1888108

Title:
  Fresh install 20.04

Status in xorg package in Ubuntu:
  New

Bug description:
  My Graphics are like a slide show.

  Its almost as if the display drivers are not installed?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 22:08:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated 
Graphics Controller [17aa:30a3]
  InstallationDate: Installed on 2020-07-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 10AB004DUS
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=cd7df6ea-b877-481a-9eee-6d5e2b5d770a ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB9AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  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:bvnLENOVO:bvrFBKTB9AUS:bd11/13/2015:svnLENOVO:pn10AB004DUS:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvrSDK0E50510WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ThinkCentre M93p
  dmi.product.name: 10AB004DUS
  dmi.product.sku: LENOVO_MT_10AB
  dmi.product.version: ThinkCentre M93p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev:

[Touch-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

A pair of headphones was always plugged  at the front.
Now I  connected speakers in the connector line on the back, and it works 
effectively.
The front headphones also work with the speakers connected behind. Apparently 
it requires a connector put on the back.
Thank you very much for your contribution, it has solved my problem.
Greetings from Argentina.
This text was automatically translated by google

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1887610

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Touch-packages] [Bug 1888101] [NEW] 'unsupported protocol' error when using PyMySQL

2020-07-18 Thread Leon

Public bug reported:

1)
Description:Ubuntu 20.04 LTS
Release:20.04

2)
openssl:
  Installiert:   1.1.1f-1ubuntu2
  Installationskandidat: 1.1.1f-1ubuntu2
  Versionstabelle:
 *** 1.1.1f-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

3) + 4)
I am trying to connect to my MariaDB with python package "PyMySQL" and SSL 
enabled. On my old installation (Kubuntu 19.10) this worked. With the new 
installation (also new PC: Xubuntu 20.04) I get this error message:

ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol
(_ssl.c:1108)

Here are my installation details:
Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 28 
May 2019
New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 31 
Mar 2020

When I use python with a different SSL version...:
this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX 
this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 
this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 


It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does 
not work together with PyMySQL.

Some more details I have posted here:
https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1f-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sat Jul 18 15:42:27 2020
InstallationDate: Installed on 2020-07-13 (4 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1888101

Title:
  'unsupported protocol' error when using PyMySQL

Status in openssl package in Ubuntu:
  New

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2)
  openssl:
Installiert:   1.1.1f-1ubuntu2
Installationskandidat: 1.1.1f-1ubuntu2
Versionstabelle:
   *** 1.1.1f-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) + 4)
  I am trying to connect to my MariaDB with python package "PyMySQL" and SSL 
enabled. On my old installation (Kubuntu 19.10) this worked. With the new 
installation (also new PC: Xubuntu 20.04) I get this error message:

  ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol
  (_ssl.c:1108)

  Here are my installation details:
  Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 
28 May 2019
  New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 
31 Mar 2020

  When I use python with a different SSL version...:
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX 
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 
  this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 

  
  It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does 
not work together with PyMySQL.

  Some more details I have posted here:
  
https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1f-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Jul 18 15:42:27 2020
  InstallationDate: Installed on 2020-07-13 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

2020-07-18 Thread Hui Wang

I planned to let you run "dmesg > dmesg.txt", then upload it to
launchpad, but now no need to upload the dmesg.

Your issue has nothing to do with this SRU, this SRU will update the
pulseaudio to 1:13.99.1-1ubuntu3.5 while the version on your machine is
ubuntu3.2lp1869819.

And According to the log in the #15, there is no any problem:
The output is null or dummy because all output device are unavailable at that 
moment:
Default Sink: auto_null
analog-output-lineout: LÃnea de salida (priority: 9000, 
latency offset: 0 usec, not available)
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo
analog-output-headphones: Auriculares analÃ³gicos (priority: 
9900, latency offset: 0 usec, not available)
Properties:
device.icon_name = "audio-headphones"
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo

After you plugging in the headphone or lineout, the output device will
not be null or dummy.


For input device, it is usb input, there is no problem too.


So how do you expect the audio to work?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1887610

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Touch-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

dmesg>demsg.txt

** Attachment added: "the output"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887610/+attachment/5393973/+files/demsg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1887610

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Touch-packages] [Bug 1888092] Re: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing new version: Inpu

2020-07-18 Thread Gunnar Hjalmarsson

That sounds as a hardware glitch. If you haven't already, can you please
try:

sudo apt install --reinstall ibus-data

and let us know if it helps.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1888092

Title:
  package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to
  make backup link of './usr/share/ibus/dicts/emoji-af.dict' before
  installing new version: Input/output error

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  I have problems while install ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus-data 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 18 22:43:47 2020
  DuplicateSignature:
   package:ibus-data:1.5.22-2ubuntu2
   Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

And please also upload the dmesg. BTW, how did you update, only update the 
pulseaudio or upgrade many packages? And what is the pulseaudio version now 
(checking it by running dpkg -s pulseaudio | grep Version).
jorge2@jorge-Mate-20-4:~$ dpkg -s pulseaudio | grep Version
Version: 1:13.99.1-1ubuntu3.2lp1869819
jorge2@jorge-Mate-20-4:~$ 
I update from http://ppa.launchpad.net/kaihengfeng/fix-lp1869819/ubuntu
I'm sorry, I don't understand what you mean by "upload the dmesg. BTW", I know 
the command dmesq, what do you want me to do?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1887610

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Touch-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

** Attachment added: "audio-log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887610/+attachment/5393960/+files/audio-log.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1887610

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Touch-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

audio-log.txt:


> pulseaudio_ps_do
jorge2  1831  0.0  0.2 1149508 20100 ?   S which pulseaudio
/usr/bin/pulseaudio

> pidof pulseaudio
1831

> pulseaudio --version
pulseaudio 13.99.1

> pactl info
Server String: /run/user/1002/pulse/native
Library Protocol Version: 33
Server Protocol Version: 33
Is Local: yes
Client Index: 79
Tile Size: 65472
User Name: jorge2
Host Name: jorge-Mate-20-4
Server Name: pulseaudio
Server Version: 13.99.1
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: auto_null
Default Source: alsa_input.usb-KYE_Systems_Corp._FaceCam_VGA-02.mono-fallback
Cookie: da6d:375c

> pactl list
Module #0
Name: module-device-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the volume/mute 
state of devices"
module.version = "13.99.1"

Module #1
Name: module-stream-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the 
volume/mute/device state of streams"
module.version = "13.99.1"

Module #2
Name: module-card-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore profile of cards"
module.version = "13.99.1"

Module #3
Name: module-augment-properties
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "13.99.1"

Module #4
Name: module-switch-on-port-available
Argument: 
Usage counter: n/a
Properties:
module.author = "David Henningsson"
module.description = "Switches ports and profiles when devices 
are plugged/unplugged"
module.version = "13.99.1"

Module #5
Name: module-switch-on-connect
Argument: 
Usage counter: n/a
Properties:
module.author = "Michael Terry"
module.description = "When a sink/source is added, switch to it 
or conditionally switch to it"
module.version = "13.99.1"

Module #6
Name: module-udev-detect
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Detect available audio hardware and load 
matching drivers"
module.version = "13.99.1"

Module #7
Name: module-alsa-card
Argument: device_id="1" name="usb-KYE_Systems_Corp._FaceCam_VGA-02" 
card_name="alsa_card.usb-KYE_Systems_Corp._FaceCam_VGA-02" namereg_fail=false 
tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
avoid_resampling=no card_properties="module-udev-detect.discovered=1"
Usage counter: 0
Properties:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "13.99.1"

Module #8
Name: module-alsa-card
Argument: device_id="0" name="pci-_00_1b.0" 
card_name="alsa_card.pci-_00_1b.0" namereg_fail=false tsched=yes 
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
avoid_resampling=no card_properties="module-udev-detect.discovered=1"
Usage counter: 0
Properties:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "13.99.1"

Module #9
Name: module-native-protocol-unix
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Native protocol (UNIX sockets)"
module.version = "13.99.1"

Module #10
Name: module-default-device-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the default sink 
and source"
module.version = "13.99.1"

Module #11
Name: module-always-sink
Argument: 
Usage counter: n/a
Properties:
module.author = "Colin Guthrie"
module.description = "Siempre tenga al menos un sumidero 
cargado aunque sea uno nulo"
module.version = "13.99.1"

Module #12
Name: module-null-sink
Argument: sink_name=auto_null 
sink_properties='device.description="Salida Ficticia"'

[Touch-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

** Description changed:

  Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
  Similarly, selecting Fractional Scaling and then picking a scale factor has 
no effect.
  
  This is a recently installed Ubuntu 20.04, fully updated, on a recently
  released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU.
  It is possible that the GPU is not being detected by Ubuntu and that is
  the root cause of the problem.  I couldn't find an easy explanation
  online about how to tell whether a GPU was detected or is in use.  I did
  try running "tlp-stat -g" to get graphics status, but it returns without
  printing anything except its version number (1.3.1).
  
  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings window.
  When I press it, up pops up a dialog asking whether I want to "Keep
  these display settings?" with two options, keep or revert.  The rest of
  the screen goes grey behind the dialog box, but I can already see that
  the "Orientation" setting back in the Settings->Display window has been
  reverted to "Landscape" without me doing anything.  Whether I choose
  keep or revert, or merely let it time out after 20 seconds, the result
  remains the same -- the display stays in Landscape mode and the setting
  that I had made is reverted.
  
  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  When I turn on the "Fractional Scaling" slider, the
  graphics around the edge of the screen increase in size (the icons in
  the left-hand dock, the text in the top bar), but the Scale settings do
  not change (they remain "100%" and "200%").  However, if I switch to a
  different setting (for example, "Mouse & Touchpad") and then back to
  "Displays", the Scale settings have changed.  I have included three
  screenshots (original screen, Fractional Scaling on, and after switching
  to and from Displays.
  
  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not scale, a pop-up asks if I want to keep or revert the
  setting, but looking back at the Displays settings, the Scale has
  already reverted to 100% (as above with the Orientation).
  
- The display has been rock-solid before this, but now it started showing 
artifacts, such as 
+ The display has been rock-solid before this, but now it started showing 
artifacts, such as
  previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:
-  
+ 
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
-Subsystem: Lenovo Renoir [17aa:3f1a]
+  Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
+    Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:
  dmi.product.family: IdeaPad Flex 5 14ARE05
  dmi.product.name: 81X2
  dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
  dmi.product.version: IdeaPad Flex 5 14ARE05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A

[Touch-packages] [Bug 1887407] Re: Distribution upgrade uninstalled TortoiseHG without asking me

2020-07-18 Thread Daniel Letzeisen

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1887407

Title:
  Distribution upgrade uninstalled TortoiseHG without asking me

Status in apt package in Ubuntu:
  New

Bug description:
  I had TortoiseHG installed on my computer
  https://tortoisehg.bitbucket.io/download/linux.html

  After upgrading from Ubuntu 16.04 to 18.04, then 19.10 and then 20.04
  (I can't tell at what stage), it's GONE.

  Never was I asked if I was fine with that.

  I don't care if there's a conflict of packages or whatever, you don't
  just uninstall software like that without asking me for confirmation.

  And yes, at some point I guess I clicked Yes to something like "2387
  packages will be installed, 8793 will be removed" or whatever. But if
  you are going to uninstall an application that I installed manually
  (as opposed to some library that I never chose to install), you have
  to give a very specific warning and prompt, one that I can't easily
  miss.

  This is OUTRAGEOUS. Now I wonder how many other programs, that I don't
  use that often (unlike THG with which I work on a daily basis) may be
  gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 13 17:55:51 2020
  InstallationDate: Installed on 2013-10-11 (2466 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)

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

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

[Touch-packages] [Bug 1888092] Re: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing new version: Inpu

2020-07-18 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1888092

Title:
  package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to
  make backup link of './usr/share/ibus/dicts/emoji-af.dict' before
  installing new version: Input/output error

Status in ibus package in Ubuntu:
  New

Bug description:
  I have problems while install ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus-data 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 18 22:43:47 2020
  DuplicateSignature:
   package:ibus-data:1.5.22-2ubuntu2
   Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1883054] Re: Built-in audio device not available until alsa is reloaded

2020-07-18 Thread Stephen Warren

For me, this issue has now been resolved; I assume due to the pulseaudio
package updates that I installed yesterday, but it might have been fixed
for a few days longer.

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

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

Title:
  Built-in audio device not available until alsa is reloaded

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and
  audio worked fine, using either the built-in speakers/mic on the
  laptop or via a USB headset when that was plugged in.

  However, after upgrading to 20.04, the built-in audio device is no
  longer available until I run "sudo alsa force-reload". Wthhout that
  WAR, all I see is a dummy audio device. Luckily the USB headset works
  fine, if plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  swarren7664 F pulseaudio
   /dev/snd/controlC0:  swarren7664 F pulseaudio
   /dev/snd/pcmC0D0c:   swarren7664 F...m pulseaudio
   /dev/snd/pcmC0D0p:   swarren7664 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Jun 10 23:57:08 2020
  InstallationDate: Installed on 2016-03-03 (1561 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1DETA6W (2.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ERCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P70
  dmi.product.name: 20ERCTO1WW
  dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70
  dmi.product.version: ThinkPad P70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

** Attachment added: "This is my screen just after I slide the Fractional 
Scaling slider.  The icons in the left margin, and the text at the top of the 
screen, have changed size (despite me not picking any new scale) and nothing 
else has scaled."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393947/+files/Screenshot%20from%202020-07-18%2014-21-41%20-%20fractional%20scaling%20with%20large%20dock%20and%20top%20bar%20but%20nothing%20else%20scaled.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1888088

Title:
  [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do
  fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
  Similarly, selecting Fractional Scaling and then picking a scale factor has 
no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see that the "Orientation" setting back in the Settings->Display
  window has been reverted to "Landscape" without me doing anything.
  Whether I choose keep or revert, or merely let it time out after 20
  seconds, the result remains the same -- the display stays in Landscape
  mode and the setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  When I turn on the "Fractional Scaling" slider,
  the graphics around the edge of the screen increase in size (the icons
  in the left-hand dock, the text in the top bar), but the Scale
  settings do not change (they remain "100%" and "200%").  However, if I
  switch to a different setting (for example, "Mouse & Touchpad") and
  then back to "Displays", the Scale settings have changed.  I have
  included three screenshots (original screen, Fractional Scaling on,
  and after switching to and from Displays.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not scale, a pop-up asks if I want to keep or revert the
  setting, but looking back at the Displays settings, the Scale has
  already reverted to 100% (as above with the Orientation).

  The display has been rock-solid before this, but now it started showing 
artifacts, such as
  previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias:

[Touch-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

** Attachment added: "This is my screen after I chose "125%" as a fractional 
scale, then pressed Apply.  The pop-up has dimmed the underlying windows, but 
you can see that the Scale setting in the underlying Displays window has 
reverted to "100%", and nothing on the screen has changed its scale to 125%."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393948/+files/Screenshot%20from%202020-07-18%2014-27-40%20-%20attempted%20125%25%20with%20popup.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1888088

Title:
  [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do
  fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
  Similarly, selecting Fractional Scaling and then picking a scale factor has 
no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see that the "Orientation" setting back in the Settings->Display
  window has been reverted to "Landscape" without me doing anything.
  Whether I choose keep or revert, or merely let it time out after 20
  seconds, the result remains the same -- the display stays in Landscape
  mode and the setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  When I turn on the "Fractional Scaling" slider,
  the graphics around the edge of the screen increase in size (the icons
  in the left-hand dock, the text in the top bar), but the Scale
  settings do not change (they remain "100%" and "200%").  However, if I
  switch to a different setting (for example, "Mouse & Touchpad") and
  then back to "Displays", the Scale settings have changed.  I have
  included three screenshots (original screen, Fractional Scaling on,
  and after switching to and from Displays.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not scale, a pop-up asks if I want to keep or revert the
  setting, but looking back at the Displays settings, the Scale has
  already reverted to 100% (as above with the Orientation).

  The display has been rock-solid before this, but now it started showing 
artifacts, such as
  previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias:

[Touch-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

** Attachment added: "This is my screen before I slide the "Fractional Scaling" 
slider."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393945/+files/Screenshot%20from%202020-07-18%2014-21-25%20-%20before%20fractional%20scaling.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1888088

Title:
  [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do
  fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
  Similarly, selecting Fractional Scaling and then picking a scale factor has 
no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see that the "Orientation" setting back in the Settings->Display
  window has been reverted to "Landscape" without me doing anything.
  Whether I choose keep or revert, or merely let it time out after 20
  seconds, the result remains the same -- the display stays in Landscape
  mode and the setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  When I turn on the "Fractional Scaling" slider,
  the graphics around the edge of the screen increase in size (the icons
  in the left-hand dock, the text in the top bar), but the Scale
  settings do not change (they remain "100%" and "200%").  However, if I
  switch to a different setting (for example, "Mouse & Touchpad") and
  then back to "Displays", the Scale settings have changed.  I have
  included three screenshots (original screen, Fractional Scaling on,
  and after switching to and from Displays.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not scale, a pop-up asks if I want to keep or revert the
  setting, but looking back at the Displays settings, the Scale has
  already reverted to 100% (as above with the Orientation).

  The display has been rock-solid before this, but now it started showing 
artifacts, such as
  previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:
  dmi.product.family: IdeaPad Flex 5 14ARE05
  dmi.product.name: 81X2
  dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
  dmi.product.version:

[Touch-packages] [Bug 1888092] [NEW] package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing new version: In

2020-07-18 Thread Edson Canganjo

Public bug reported:

I have problems while install ubuntu 20.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ibus-data 1.5.22-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jul 18 22:43:47 2020
DuplicateSignature:
 package:ibus-data:1.5.22-2ubuntu2
 Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
  unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: ibus
Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1888092

Title:
  package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to
  make backup link of './usr/share/ibus/dicts/emoji-af.dict' before
  installing new version: Input/output error

Status in ibus package in Ubuntu:
  New

Bug description:
  I have problems while install ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus-data 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 18 22:43:47 2020
  DuplicateSignature:
   package:ibus-data:1.5.22-2ubuntu2
   Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1888091] [NEW] Deform switch in the Livepatch tab

2020-07-18 Thread MadsRH

Public bug reported:

When the user isn't signed in, the switch looks deform / squeezed. See
the attached screenshot.

Maybe the blue spinner is somehow calculated into the padding and when
the spinner is gone (after "Checking availability"), the padding does
not match and the switch gets squeezed.

This is only a visual bug, non critical, but should be low hanging
fruit.

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

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1888091/+attachment/5393946/+files/screenshot.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1888091

Title:
  Deform switch in the Livepatch tab

Status in software-properties package in Ubuntu:
  New

Bug description:
  When the user isn't signed in, the switch looks deform / squeezed. See
  the attached screenshot.

  Maybe the blue spinner is somehow calculated into the padding and when
  the spinner is gone (after "Checking availability"), the padding does
  not match and the switch gets squeezed.

  This is only a visual bug, non critical, but should be low hanging
  fruit.

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

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

[Touch-packages] [Bug 1888088] [NEW] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

Public bug reported:

Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
Similarly, selecting Fractional Scaling and then picking a scale factor has no 
effect.

This is a recently installed Ubuntu 20.04, fully updated, on a recently
released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU.
It is possible that the GPU is not being detected by Ubuntu and that is
the root cause of the problem.  I couldn't find an easy explanation
online about how to tell whether a GPU was detected or is in use.  I did
try running "tlp-stat -g" to get graphics status, but it returns without
printing anything except its version number (1.3.1).

When I choose an orientation, such as Portrait Right, the setting
changes and an "Apply" button appears in the top of the Settings window.
When I press it, up pops up a dialog asking whether I want to "Keep
these display settings?" with two options, keep or revert.  The rest of
the screen goes grey behind the dialog box, but I can already see that
the "Orientation" setting back in the Settings->Display window has been
reverted to "Landscape" without me doing anything.  Whether I choose
keep or revert, or merely let it time out after 20 seconds, the result
remains the same -- the display stays in Landscape mode and the setting
that I had made is reverted.

Regarding scaling, I can set the display scale to 100% (default) or
200%, successfully.  When I turn on the "Fractional Scaling" slider, the
graphics around the edge of the screen increase in size (the icons in
the left-hand dock, the text in the top bar), but the Scale settings do
not change (they remain "100%" and "200%").  However, if I switch to a
different setting (for example, "Mouse & Touchpad") and then back to
"Displays", the Scale settings have changed.  I have included three
screenshots (original screen, Fractional Scaling on, and after switching
to and from Displays.

When I attempt to set a fractional scale such as 125%, the "Apply"
button appears in the upper right corner.  When I press that, the
display does not scale, a pop-up asks if I want to keep or revert the
setting, but looking back at the Displays settings, the Scale has
already reverted to 100% (as above with the Orientation).

The display has been rock-solid before this, but now it started showing 
artifacts, such as 
previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sat Jul 18 14:00:38 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Renoir [17aa:3f1a]
InstallationDate: Installed on 2020-07-16 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81X2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: EECN20WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Flex 5 14ARE05
dmi.modalias: 
dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:
dmi.product.family: IdeaPad Flex 5 14ARE05
dmi.product.name: 81X2
dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
dmi.product.version: IdeaPad Flex 5 14ARE05
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
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+git20200226-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 ubuntu

-- 
You received this bug notification because you

[Touch-packages] [Bug 1662357] Re: Can't use lsb_release on Ubuntu Core 16

2020-07-18 Thread Oliver Grawert

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

first of all the bug is a duplicate, secondly you can not install deb
packages on Ubuntu Core, snap packages (of which Ubuntu Core is built)
do use /etc/os-release. Additionally Ubuntu Core only ships the most
minimal set of python ...

If you see an issue on a Classic Ubuntu installation newer than Ubuntu
Core 16, you should open a new bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1662357

Title:
  Can't use lsb_release on Ubuntu Core 16

Status in lsb:
  Invalid
Status in Snappy:
  New
Status in Snappy Ubuntu Core:
  New
Status in lsb package in Ubuntu:
  Invalid

Bug description:
  brian-murray@localhost:~$ snap list   

  
  Name Version Rev  Developer  Notes
  core 16.04.1 888  canonical  -

  
  brian-murray@localhost:~$ lsb_release
  Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in 
  main()
File "/usr/bin/lsb_release", line 59, in main
  distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
  distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
  get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  ValueError: could not convert string to float: '16.04 LTS'

  brian-murray@localhost:~$ lsb_release -a
  Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in 
  main()
File "/usr/bin/lsb_release", line 59, in main
  distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
  distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
  get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  ValueError: could not convert string to float: '6.06 LTS'

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

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

[Touch-packages] [Bug 1872474] Re: Missing gpgme-json prevents use of popular Mailvelope browser extension

2020-07-18 Thread Dimitri John Ledkov

** Changed in: gpgme1.0 (Ubuntu)
   Importance: Undecided => Critical

** Also affects: gpgme1.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1872474

Title:
  Missing gpgme-json prevents use of popular Mailvelope browser
  extension

Status in gpgme1.0 package in Ubuntu:
  Confirmed
Status in gpgme1.0 source package in Focal:
  New
Status in gpgme1.0 package in Debian:
  New

Bug description:
  As described at the Mailvelope GitHub repository wiki here
   users are able to use their local GPG keyring via gpgme-
  json (rather than the included Openpgp.js library) with several
  popular webmail services, provided that the gpgme-json binary is
  available to the browser process. I reviewed the file lists for the
  binary packages produced from this source package and found no mention
  of it. Upon closer inspection of the packaging files, the d/rules has
  an override for dh_missing for the file and a note in the changelog
  from 2018, but there was no mention of what the circumstances were
  that necessitated that decision.

  If it's possible to correct the conditions that led to the file's
  exclusion I think it would be well worth pursuing as e-mail becomes
  evermore commercialized on top of an infrastructure that never did
  place much of a premium on privacy.

  I'm running the dev release of Kubuntu 20.04 LTS "Focal Fossa" with
  version 1.13.1-7ubuntu2 of the libgpgme11 package.

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

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

[Touch-packages] [Bug 1662357] Re: Can't use lsb_release on Ubuntu Core 16

2020-07-18 Thread Alan AZZERA

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

Hi, why this bug is invalid ? I just ran into it after upgrading from Ubuntu 
18.04 to 20.04. After finding and applying with success the fix of @shiina, I 
downloaded the package lsb-release_11.0.1ubuntu1_all.deb, wich still contains 
the line RELEASES_ORDER.sort(key=lambda n: float(n[0])) in the file 
/usr/share/pyshared/lsb_release.py. So, it seems there's only 2 possibilities :
- the bug is still here and nobody relies anymore on lsb_release ;
- there is another problem somewhere in my system.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1662357

Title:
  Can't use lsb_release on Ubuntu Core 16

Status in lsb:
  Invalid
Status in Snappy:
  New
Status in Snappy Ubuntu Core:
  New
Status in lsb package in Ubuntu:
  Invalid

Bug description:
  brian-murray@localhost:~$ snap list   

  
  Name Version Rev  Developer  Notes
  core 16.04.1 888  canonical  -

  
  brian-murray@localhost:~$ lsb_release
  Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in 
  main()
File "/usr/bin/lsb_release", line 59, in main
  distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
  distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
  get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  ValueError: could not convert string to float: '16.04 LTS'

  brian-murray@localhost:~$ lsb_release -a
  Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in 
  main()
File "/usr/bin/lsb_release", line 59, in main
  distinfo = lsb_release.get_distro_information()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in 
get_distro_information
  distinfo = guess_debian_release()
File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in 
guess_debian_release
  get_distro_info(distinfo['ID'])
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
get_distro_info
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in 
  RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  ValueError: could not convert string to float: '6.06 LTS'

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

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

[Touch-packages] [Bug 1887407] Re: Distribution upgrade uninstalled TortoiseHG without asking me

2020-07-18 Thread teo1978

> the upgrade gives you a chance to see the details you want. You were
prompted with these screens, including the obsolete software screen,
correct?


Correct. As I said, not good enough.


> Please be more specific about the exact changes you would like to see.

Again as I said: for every individual application that you are going to
remove that I installed manually (as opposed to it being installed as a
dependency), you have to show an individual popup screen with a very
scary warning.

THEN, if you want, there you can add a checkbox like "apply to all" or
whatever, where I can choose to accept in bulk after reviewing a list.


OR simply change the "remove obsolete packages" prompt to make it more scary, 
so I get the impression that I seriously need to review the list. 

However, if the number is actually in the order of 86, you need to make
it smaller to begin with, one way or another. Otherwise, even if I start
to look at the list seriously, chances are I'll end up missing something
or saying "well, whatever".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1887407

Title:
  Distribution upgrade uninstalled TortoiseHG without asking me

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  I had TortoiseHG installed on my computer
  https://tortoisehg.bitbucket.io/download/linux.html

  After upgrading from Ubuntu 16.04 to 18.04, then 19.10 and then 20.04
  (I can't tell at what stage), it's GONE.

  Never was I asked if I was fine with that.

  I don't care if there's a conflict of packages or whatever, you don't
  just uninstall software like that without asking me for confirmation.

  And yes, at some point I guess I clicked Yes to something like "2387
  packages will be installed, 8793 will be removed" or whatever. But if
  you are going to uninstall an application that I installed manually
  (as opposed to some library that I never chose to install), you have
  to give a very specific warning and prompt, one that I can't easily
  miss.

  This is OUTRAGEOUS. Now I wonder how many other programs, that I don't
  use that often (unlike THG with which I work on a daily basis) may be
  gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 13 17:55:51 2020
  InstallationDate: Installed on 2013-10-11 (2466 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)

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

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

[Touch-packages] [Bug 1879019] Re: bad mime type for bmp

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1879019

Title:
  bad mime type for bmp

Status in Ristretto:
  New
Status in file package in Ubuntu:
  Confirmed
Status in ristretto package in Ubuntu:
  Confirmed

Bug description:
  Sample BMP file attached to this related bug:
  https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1762242

  Note the attached screenshot here, this is a regression

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libmagic1 1:5.38-4
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May 15 23:28:26 2020
  InstallationDate: Installed on 2018-04-29 (747 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1888077] [NEW] No startup sound played with gnome-session-canberra

2020-07-18 Thread Yousuf 'Jay' Philips

Public bug reported:

Tested on Xubuntu 20.04 with gnome-session-canberra and yaru-theme-sound
packages installed

The gnome-session-canberra package has a /usr/share/gnome/autostart
/libcanberra-login-sound.desktop but it will not run. I disabled all of
the below entries in the file and it still wouldn't run.

OnlyShowIn=GNOME;Unity;
AutostartCondition=GSettings org.gnome.desktop.sound event-sounds
X-GNOME-Autostart-Phase=Application
X-GNOME-Provides=login-sound
X-GNOME-Autostart-enabled=false
NoDisplay=true

The shutdown script /usr/share/gnome/shutdown/libcanberra-logout-
sound.sh in the same package worked fine.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1888077

Title:
  No startup sound played with gnome-session-canberra

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Tested on Xubuntu 20.04 with gnome-session-canberra and yaru-theme-
  sound packages installed

  The gnome-session-canberra package has a /usr/share/gnome/autostart
  /libcanberra-login-sound.desktop but it will not run. I disabled all
  of the below entries in the file and it still wouldn't run.

  OnlyShowIn=GNOME;Unity;
  AutostartCondition=GSettings org.gnome.desktop.sound event-sounds
  X-GNOME-Autostart-Phase=Application
  X-GNOME-Provides=login-sound
  X-GNOME-Autostart-enabled=false
  NoDisplay=true

  The shutdown script /usr/share/gnome/shutdown/libcanberra-logout-
  sound.sh in the same package worked fine.

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

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

[Touch-packages] [Bug 1838329] Re: Cryptswap periodically fails to mount at boot due to missing a udev notification

This bug was fixed in the package systemd - 245.6-3ubuntu3

---
systemd (245.6-3ubuntu3) groovy; urgency=medium

  * Rebuild against libselinux 3.0

systemd (245.6-3ubuntu2) groovy; urgency=medium

  * basic/cap-list: Print unknown capabilities in hexadecimal.
This fixes autopkgtest running on 5.8 kernels
(when systemd was built on an earlier one) (LP: #1885755)
File: debian/patches/basic-cap-list-parse-print-numerical-capabilities.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ef46ec8289df815d42c9a3fdbf9fb347226d6be4

systemd (245.6-3ubuntu1) groovy; urgency=medium

  * Merge to Ubuntu from Debian unstable
- Dropped changes:
  * Enable EFI/bootctl on armhf.

systemd (245.6-3) unstable; urgency=medium

  [ Dan Streetman ]
  * d/t/upstream: capture new merged 'system.journal' from tests.
https://github.com/systemd/systemd/pull/15281
  * d/t/upstream: use --directory or --file param for journalctl.
Properly tell journalctl if the journal to parse is a dir or file.
  * d/t/storage: check for ext2 or ext4 fs when using crypttab 'tmp' option.
https://github.com/systemd/systemd/pull/15853

  [ Martin Pitt ]
  * debian/tests/localed-locale: Fix for environments without en_US.UTF-8.
Unconditionally back up/restore locale configuration files and generate
en_US.UTF-8. Previously the test failed in environments which have some
locale other than en_US.UTF-8 in /etc/default/locale.
Also fix the assertion of /etc/locale.conf not being present after
localectl. This only applies to Debian/Ubuntu tests, not upstream ones.

  [ Dimitri John Ledkov ]
  * Enable EFI/bootctl on armhf.

systemd (245.6-2ubuntu2) groovy; urgency=medium

  [ Balint Reczey ]
  * debian/tests/tests-in-lxd: Work around snapd.seeded.service hanging
File: debian/tests/tests-in-lxd

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=04a3342ff533b234ccb1a1020f6d854ab0acd053

  [ Dimitri John Ledkov ]
  * ubuntu: enable CET on amd64.
File: debian/rules

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cc42a377e7e8c372124bcf43d9f4fb9c169f4292

  [ Dan Streetman ]
  * Lock swap blockdevice while calling mkswap (LP: #1838329)
Files:
- 
debian/patches/lp1838329/0001-blockdev-propagate-one-more-unexpected-error.patch
- 
debian/patches/lp1838329/0003-dissect-use-log_debug_errno-where-appropriate.patch
- 
debian/patches/lp1838329/0004-blockdev-add-helper-for-locking-whole-block-device.patch
- debian/patches/lp1838329/0005-makefs-lock-device-while-we-operate.patch
- debian/patches/lp1838329/0006-makefs-normalize-logging-a-bit.patch
- 
debian/patches/lp1838329/0007-cryptsetup-generator-use-systemd-makefs-for-implemen.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=652a148cf1d3ecfa93cfee288c152c90caee3ac6

systemd (245.6-2ubuntu1) groovy; urgency=medium

  * Merge to Ubuntu from Debian unstable
- Dropped changes:
  * dhclient-exit-hooks.d/timesyncd: Act only when systemd-timesyncd is 
enabled
  * hwdb: Mask rfkill event from intel-hid on HP platforms (LP: #1883846)
File: 
debian/patches/hwdb-Mask-rfkill-event-from-intel-hid-on-HP-platforms.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c705323d61b9cd4e36ceb92e236cd6e9ba4c1b1a
  * debian/tests/tests-in-lxd: Show debugging info about reason of skipping test
File: debian/tests/tests-in-lxd

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1c835ca2d4f6d09977525d781d224a87ba7cde24
  * debian/tests/tests-in-lxd: Drop workaround removing fstab from the container
(LP: #1886430)
File: debian/tests/tests-in-lxd

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f13213af98fa4c27c5f7e58c511b9691bb56065a

systemd (245.6-2) unstable; urgency=medium

  [ Dan Streetman ]
  * 40-vm-hotadd.rules: check offline before onlining memory/cpus.
The kernel will return EINVAL if the memory or cpu is already online,
which is harmless, but adds a confusing error to the log. Avoid the error
message by only onlining if the memory or cpu is currently offline.
(LP: #1876018)

  [ Michael Biebl ]
  * d/t/boot-and-services: use canonical name for NetworkManager service
  * Fix build with libmicrohttpd 0.9.71.
The return type of callbacks was changed from int to an enum.

  [ Youfu Zhang ]
  * fsckd: avoid useless CR displayed on console (LP: #1692353)

  [ Balint Reczey ]
  * dhclient-exit-hooks.d/timesyncd: Act only when systemd-timesyncd is 
available.
Otherwise the hook script might trigger an error if the
systemd-timesyncd package is uninstalled but not purged. (LP: #1873031)

 -- Balint Reczey   Thu, 16 Jul 2020 16:54:53 +0200

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

-- 
You received this bug notification because you

[Touch-packages] [Bug 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities

This bug was fixed in the package systemd - 245.6-3ubuntu3

---
systemd (245.6-3ubuntu3) groovy; urgency=medium

  * Rebuild against libselinux 3.0

systemd (245.6-3ubuntu2) groovy; urgency=medium

  * basic/cap-list: Print unknown capabilities in hexadecimal.
This fixes autopkgtest running on 5.8 kernels
(when systemd was built on an earlier one) (LP: #1885755)
File: debian/patches/basic-cap-list-parse-print-numerical-capabilities.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ef46ec8289df815d42c9a3fdbf9fb347226d6be4

systemd (245.6-3ubuntu1) groovy; urgency=medium

  * Merge to Ubuntu from Debian unstable
- Dropped changes:
  * Enable EFI/bootctl on armhf.

systemd (245.6-3) unstable; urgency=medium

  [ Dan Streetman ]
  * d/t/upstream: capture new merged 'system.journal' from tests.
https://github.com/systemd/systemd/pull/15281
  * d/t/upstream: use --directory or --file param for journalctl.
Properly tell journalctl if the journal to parse is a dir or file.
  * d/t/storage: check for ext2 or ext4 fs when using crypttab 'tmp' option.
https://github.com/systemd/systemd/pull/15853

  [ Martin Pitt ]
  * debian/tests/localed-locale: Fix for environments without en_US.UTF-8.
Unconditionally back up/restore locale configuration files and generate
en_US.UTF-8. Previously the test failed in environments which have some
locale other than en_US.UTF-8 in /etc/default/locale.
Also fix the assertion of /etc/locale.conf not being present after
localectl. This only applies to Debian/Ubuntu tests, not upstream ones.

  [ Dimitri John Ledkov ]
  * Enable EFI/bootctl on armhf.

systemd (245.6-2ubuntu2) groovy; urgency=medium

  [ Balint Reczey ]
  * debian/tests/tests-in-lxd: Work around snapd.seeded.service hanging
File: debian/tests/tests-in-lxd

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=04a3342ff533b234ccb1a1020f6d854ab0acd053

  [ Dimitri John Ledkov ]
  * ubuntu: enable CET on amd64.
File: debian/rules

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cc42a377e7e8c372124bcf43d9f4fb9c169f4292

  [ Dan Streetman ]
  * Lock swap blockdevice while calling mkswap (LP: #1838329)
Files:
- 
debian/patches/lp1838329/0001-blockdev-propagate-one-more-unexpected-error.patch
- 
debian/patches/lp1838329/0003-dissect-use-log_debug_errno-where-appropriate.patch
- 
debian/patches/lp1838329/0004-blockdev-add-helper-for-locking-whole-block-device.patch
- debian/patches/lp1838329/0005-makefs-lock-device-while-we-operate.patch
- debian/patches/lp1838329/0006-makefs-normalize-logging-a-bit.patch
- 
debian/patches/lp1838329/0007-cryptsetup-generator-use-systemd-makefs-for-implemen.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=652a148cf1d3ecfa93cfee288c152c90caee3ac6

systemd (245.6-2ubuntu1) groovy; urgency=medium

  * Merge to Ubuntu from Debian unstable
- Dropped changes:
  * dhclient-exit-hooks.d/timesyncd: Act only when systemd-timesyncd is 
enabled
  * hwdb: Mask rfkill event from intel-hid on HP platforms (LP: #1883846)
File: 
debian/patches/hwdb-Mask-rfkill-event-from-intel-hid-on-HP-platforms.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c705323d61b9cd4e36ceb92e236cd6e9ba4c1b1a
  * debian/tests/tests-in-lxd: Show debugging info about reason of skipping test
File: debian/tests/tests-in-lxd

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1c835ca2d4f6d09977525d781d224a87ba7cde24
  * debian/tests/tests-in-lxd: Drop workaround removing fstab from the container
(LP: #1886430)
File: debian/tests/tests-in-lxd

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f13213af98fa4c27c5f7e58c511b9691bb56065a

systemd (245.6-2) unstable; urgency=medium

  [ Dan Streetman ]
  * 40-vm-hotadd.rules: check offline before onlining memory/cpus.
The kernel will return EINVAL if the memory or cpu is already online,
which is harmless, but adds a confusing error to the log. Avoid the error
message by only onlining if the memory or cpu is currently offline.
(LP: #1876018)

  [ Michael Biebl ]
  * d/t/boot-and-services: use canonical name for NetworkManager service
  * Fix build with libmicrohttpd 0.9.71.
The return type of callbacks was changed from int to an enum.

  [ Youfu Zhang ]
  * fsckd: avoid useless CR displayed on console (LP: #1692353)

  [ Balint Reczey ]
  * dhclient-exit-hooks.d/timesyncd: Act only when systemd-timesyncd is 
available.
Otherwise the hook script might trigger an error if the
systemd-timesyncd package is uninstalled but not purged. (LP: #1873031)

 -- Balint Reczey   Thu, 16 Jul 2020 16:54:53 +0200

** Changed in: systemd (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because

[Touch-packages] [Bug 1888065] Re: Screen dies/black after changing display orientation or enabling fractional scaling

2020-07-18 Thread Jonathan Watt

The issue seems gone after a reboot. Theming and colors are back to
normal.

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1888065

Title:
Screen dies/black after changing display orientation or enabling
fractional scaling

Status in xorg package in Ubuntu:
New

Bug description:
I upgraded to 20.04 over a month ago and it's been working fine. I
have one monitor (external). I tried turning on fractional scaling in
the display settings and the screen immediately turned black. I
waited, expecting the "confirm changes" prompt to timeout and restore
the display. It never did.

Next I hard rebooted, but as soon as I'd entered my password to login,
the screen went black again. Tried this a few more times. I then
booted to a root console and `apt update/upgrade` to get all updates.
Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1
to get a virtual console, then back to F2, and a few other things. At
some point I was able to log back in.

Foolishly I assumed the issue was just with fractional scaling, and
back in Display settings I for some reason decided to experiment
further and flipped the display orientation to portrate. Immediately I
got a black screen and ended back in the same reboot loop, always
getting a black screen as soon as I tried to log back in. Searching
online I couldn't seem to find a way to revert the display
orientation. From another virtual console I was unable to run xrandr
or start a wayland session to get to the settings panel. To do that I
was trying to run:

dbus-run-session -- gnome-shell --display-server --wayland

But that's just something I found on the Web, I have no idea what I'm
doing there. It just gave the error:

(gnome-shell:) mutter-warning: **: Failed to
open gpu 'dev/dri/card0 Failed to activate universal planes: Operation not
permitted
(gnome-shell:) mutter-warning: **: Failed to
create backend: No GPUs found

Eventually I found a suggestion on the Web to unplug the cable to the
display, and after experimenting with that a bit and switching between
virtual consoles, at some point it was logged in with a working
display ... well, sort of. The colors and icons are weird like it's
lost theming or something. Going into the Display settings it seems
that the orientation has also been reset to landscape.

I'm filing this bug before restarting the machine so I can report the
system scan it has taken. At this point I've no idea whether I'll be
able to log back in again after a reboot. I'll try that now.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:21: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-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Jul 18 17:21:56 2020
DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
nvidia, 435.21, 5.4.0-37-generic, x86_64: installed
nvidia, 435.21, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
InstallationDate: Installed on 2019-11-03 (257 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP Z4 G4 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic
root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago)
dmi.bios.date: 03/21/2019
dmi.bios.vendor: HP
dmi.bios.version: P62 v01.75
dmi.board.name: 81C5
dmi.board.vendor: HP
dmi.board.version: MVB
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrP62v01.75:bd03/21/2019:svnHP:pnHPZ4G4Workstation:pvr:rvnHP:rn81C5:rvrMVB:cvnHP:ct3:cvr:
dmi.product.family: 103C_53335X HP Workstation
dmi.product.name: HP Z4 G4 Workstation
dmi.product.sku: 5FN34US#ABA
dmi.sys.vendor: HP
version.compiz:

[Touch-packages] [Bug 1888065] [NEW] Screen dies/black after changing display orientation or enabling fractional scaling

2020-07-18 Thread Jonathan Watt

Public bug reported:

I upgraded to 20.04 over a month ago and it's been working fine. I have
one monitor (external). I tried turning on fractional scaling in the
display settings and the screen immediately turned black. I waited,
expecting the "confirm changes" prompt to timeout and restore the
display. It never did.

Next I hard rebooted, but as soon as I'd entered my password to login,
the screen went black again. Tried this a few more times. I then booted
to a root console and `apt update/upgrade` to get all updates.
Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1
to get a virtual console, then back to F2, and a few other things. At
some point I was able to log back in.

Foolishly I assumed the issue was just with fractional scaling, and back
in Display settings I for some reason decided to experiment further and
flipped the display orientation to portrate. Immediately I got a black
screen and ended back in the same reboot loop, always getting a black
screen as soon as I tried to log back in. Searching online I couldn't
seem to find a way to revert the display orientation. From another
virtual console I was unable to run xrandr or start a wayland session to
get to the settings panel. To do that I was trying to run:

  dbus-run-session -- gnome-shell --display-server --wayland

But that's just something I found on the Web, I have no idea what I'm
doing there. It just gave the error:

(gnome-shell:) mutter-warning: **:  Failed to open 
gpu 'dev/dri/card0 Failed to activate universal planes: Operation not permitted
(gnome-shell:) mutter-warning: **:  Failed to 
create backend: No GPUs found

Eventually I found a suggestion on the Web to unplug the cable to the
display, and after experimenting with that a bit and switching between
virtual consoles, at some point it was logged in with a working display
... well, sort of. The colors and icons are weird like it's lost theming
or something. Going into the Display settings it seems that the
orientation has also been reset to landscape.

I'm filing this bug before restarting the machine so I can report the
system scan it has taken. At this point I've no idea whether I'll be
able to log back in again after a reboot. I'll try that now.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:21: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-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Jul 18 17:21:56 2020
DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.4.0-37-generic, x86_64: installed
 nvidia, 435.21, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
InstallationDate: Installed on 2019-11-03 (257 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP Z4 G4 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago)
dmi.bios.date: 03/21/2019
dmi.bios.vendor: HP
dmi.bios.version: P62 v01.75
dmi.board.name: 81C5
dmi.board.vendor: HP
dmi.board.version: MVB
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrP62v01.75:bd03/21/2019:svnHP:pnHPZ4G4Workstation:pvr:rvnHP:rn81C5:rvrMVB:cvnHP:ct3:cvr:
dmi.product.family: 103C_53335X HP Workstation
dmi.product.name: HP Z4 G4 Workstation
dmi.product.sku: 5FN34US#ABA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
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.8-2ubuntu2.2
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+git20200226-1
version.xserver-xorg-video-nouveau:

[Touch-packages] [Bug 1888061] [NEW] "Line by line difference" of config files during release upgrade is an unreadable mess

2020-07-18 Thread teo1978

Public bug reported:

I upgraded from 16.04 to 18.04, then to 19.10, then to 20.04.

I'm not sure ini whih of the upgrades I noticed the issue but I'm pretty
sure it applies to all of them.

As usual, the upgrade had to install some configuration files which
would replace some files I had modified, and so I got the prompt to
choose what to do: whether to keep my modified version, or overwrite it
with the packager's version.

I don't remember the exact interface, but when you are prompted to
choose that, you have a few options to see the differences between the
two files. I think by default it shows a classical diff (with "+++"s and
"---"s) but there is an option to show "line by line differences".

I chose that for one file, and I expected to see a side-by-side diff
similar to those I've seen in dozens of tools, where you see the two
entire files side by side and the differences are highlighted in both
sides in colors, such as lines that are added or removed and lines that
are modified.

Short of that, the very least that I would have expected was to show the
two files side by side.


Instead, this PATHETIC CRAP showed up which can be seen in the sceenshot.
And don't remind me of the code of conduct. I'm not insulting anybody. It's a 
FACT that this is crap and that it is pathetic.


Not only are DIFFERENCES not shown (line by line or otherwise). The two files 
are shown as one single text file, where each line of the second file is just 
appended to the corresponding line of the first file.
You can't even tell where the line of one file begins and the line of the other 
ends.

It's a completely useless way to show "differences" between two files.
It's less useful than just showing the two files next to each other in
two independent text boxes. Way less useful. Let alone compared to an
actual side-by-side diff tool (and there are plenty to chose from).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apt 2.0.2ubuntu0.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sat Jul 18 17:30:36 2020
InstallationDate: Installed on 2013-10-11 (2471 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: apt
UpgradeStatus: Upgraded to focal on 2020-07-12 (5 days ago)

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


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

** Attachment added: "Screenshot from 2020-07-11 17-25-59.png"
   
https://bugs.launchpad.net/bugs/1888061/+attachment/5393794/+files/Screenshot%20from%202020-07-11%2017-25-59.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1888061

Title:
  "Line by line difference" of config files during release upgrade is an
  unreadable mess

Status in apt package in Ubuntu:
  New

Bug description:
  I upgraded from 16.04 to 18.04, then to 19.10, then to 20.04.

  I'm not sure ini whih of the upgrades I noticed the issue but I'm
  pretty sure it applies to all of them.

  As usual, the upgrade had to install some configuration files which
  would replace some files I had modified, and so I got the prompt to
  choose what to do: whether to keep my modified version, or overwrite
  it with the packager's version.

  I don't remember the exact interface, but when you are prompted to
  choose that, you have a few options to see the differences between the
  two files. I think by default it shows a classical diff (with "+++"s
  and "---"s) but there is an option to show "line by line differences".

  I chose that for one file, and I expected to see a side-by-side diff
  similar to those I've seen in dozens of tools, where you see the two
  entire files side by side and the differences are highlighted in both
  sides in colors, such as lines that are added or removed and lines
  that are modified.

  Short of that, the very least that I would have expected was to show
  the two files side by side.

  
  Instead, this PATHETIC CRAP showed up which can be seen in the sceenshot.
  And don't remind me of the code of conduct. I'm not insulting anybody. It's a 
FACT that this is crap and that it is pathetic.

  
  Not only are DIFFERENCES not shown (line by line or otherwise). The two files 
are shown as one single text file, where each line of the second file is just 
appended to the corresponding line of the first file.
  You can't even tell where the line of one file begins and the line of the 
other ends.

  It's a completely useless way to show "differences" between two files.
  It's less useful than just showing the two files next to each other in
  two independent text boxes. Way less useful. Let alone compared to an
  actual side-by-side diff tool (and there are plenty to chose from).

[Touch-packages] [Bug 1887271] Re: Square rectangles instead of system fonts after upgrade (LANG=de_AT.UTF-8)

2020-07-18 Thread Marcello Bassani

I feel so sorry, but I did NOT continue with 20.04 - Focal Fossa, yet 
downgraded to 18.04 via backup.
I couldn't even find out, where GnomeTweaks > Fonts is because EVERY SYSTEM 
FONT was unreadable. I won't try to upgrade this machine furthermore. Please, 
mark this thread as solved / unsolved. 
Best Regards

P.S.: "  'journalctl -b 0'  " might have been possible, yet my efforts
had been overdue, in my eyes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1887271

Title:
  Square rectangles instead of system fonts after upgrade
  (LANG=de_AT.UTF-8)

Status in pango1.0 package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my room mate's Fujitsu Esprimo Desktop PC  to 20.04
  Focal Fossa (from Bionic 18.04):

  Any system font line is being displayed distorted / erroneous / in
  sort of placeholder blocks or SQUARE RECTANGLES, as if the fonts set
  wouldn't be installed at all... Tthe 'gsettings'-procedure from some
  link mentioned on askubuntu-com wouldn't help either (with copy
  into unreadable terminal display font output) Gnome-tweak didn't help,
  BUT I can copy text from terminal into libreoffice document and thus
  make it readable afterwards. I cannot find any information about
  "system font output/printing" on the whole internet leaving me with a
  mysrltery about how that stuff works from xserver to gnome, Wayland-
  session login IMPOSSIBLE in order to print the correct display font
  ... I will attach some screenshots later on if possible.

  P.S.: firefox/libreoffice fonts are being displayed correctly inside
  any homepage

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 10:55:08 2020
  DistUpgraded: 2020-06-29 10:31:32,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.3.0-51-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-39-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed
   rtlwifi-new, 0.10: added
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:0801]
  InstallationDate: Installed on 2017-08-28 (1048 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  LightdmLog:
   [+6033.49s] DEBUG: Seat seat0 changes active session to 
   [+6033.53s] DEBUG: Seat seat0 changes active session to c5
   [+6033.53s] DEBUG: Session c5 is already active
  MachineType: FUJITSU SIEMENS ESPRIMO P
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb4
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-29 (13 days ago)
  dmi.bios.date: 10/11/2007
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.12.2312.A3
  dmi.board.name: D2312-A3
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D2312-A3
  dmi.chassis.type: 2
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: ESPP
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.12.2312.A3:bd10/11/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2312-A3:rvrS26361-D2312-A3:cvnFUJITSUSIEMENS:ct2:cvrESPP:
  dmi.product.name: ESPRIMO P
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  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.8-2ubuntu2.1
  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+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Jul 11 20:24:02 2020

[Touch-packages] [Bug 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec

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

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

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

Title:
  after login to gnome with snd_hda_intel :00:1f.3: No response from
  codec

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After login to gnome, login takes an unsual amount of time.
  Goes back to login screen.
  On second login, works normally but audio sliders are not showing correctly. 
After a while, it operates normally.
  Logs are showing a lot of
  snd_hda_intel :00:1f.3: No response from codec, resetting bus:last 
cmd0x20a70500
  +pci::00:1f.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-1063.68-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1063-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  killian68   1816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 08:56:11 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  InstallationDate: Installed on 2020-04-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.11
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1837318] Re: Cannot store password. Password prompt never ends

2020-07-18 Thread Gernot Leitgab

It is working on my actual workstation:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS (beaver-three-eyed-raven X92)
Release:18.04
Codename:   bionic

$ apt-cache policy libsecret-tools
libsecret-tools:
  Installiert:   0.18.6-1
  Installationskandidat: 0.18.6-1
  Versionstabelle:
 *** 0.18.6-1 500
500 http://at.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

But I have the same problem on my fresh installed workstation:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal

$ apt-cache policy libsecret-tools
libsecret-tools:
  Installiert:   0.20.3-0ubuntu1
  Installationskandidat: 0.20.3-0ubuntu1
  Versionstabelle:
 *** 0.20.3-0ubuntu1 500
500 http://at.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 0.20.2-1 500
500 http://at.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

So maybe it has to do with a (missing) setting or it is the result of an
incomplete setup?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsecret in Ubuntu.
https://bugs.launchpad.net/bugs/1837318

Title:
  Cannot store password. Password prompt never ends

Status in libsecret package in Ubuntu:
  Confirmed

Bug description:
  Cannot store password using secret-tool.

  I do the following:

  $ secret-tool store --label='MyService' service myservice
  Password: 
  sf
  ^C

  The thing is when I hit ENTER and inserting the password, the password
  prompt never end. So I have to hit Ctrl+C to quit the program, and
  hence the password is not saved.

  Here are my system details:

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

  $ apt-cache policy libsecret-tools
  libsecret-tools:
Installed: 0.18.6-1
Candidate: 0.18.6-1
Version table:
   *** 0.18.6-1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

2020-07-18 Thread teo1978

I'm having this issue. I googled for the name of the process that was
eating up 100% of CPU and, surprise! A bug reported in 20-fucking-12 and
still not fixed!

Great job, Ubuntu!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/911981

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 eclipse eclipse   4653056 2012-01-04 21:26 meta.db-shm
  -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal
  -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 
miner-applications-locale.txt
  -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb

  and this is  how much space I have left on my home partition after I KILLED 
the tracker-store process:
  /dev/sda8  31G   30G  418M  99% /home
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: tracker 0.10.24-1build2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago)
  UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser 
pulse-access sambashare src video

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

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

[Touch-packages] [Bug 1837318] Re: Cannot store password. Password prompt never ends