[Touch-packages] [Bug 1872376] Re: Application menu displays on right hand side of screen

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (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/1872376

Title:
  Application menu displays on right hand side of screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Unsure if this bug should fall under xorg or Gnome.

  
  When I click the "Show Applications" button, all the applications are 
displayed over on the right hand side of the primary screen. The dots to 
indicate which application page you're viewing appear over on the second 
monitor.

  This only happens when using a second display.

  Running Ubuntu 19.10.

  Link to screenshot: https://i.stack.imgur.com/dkxgy.jpg

  Output of ls -al ~/.local/share/gnome-shell/extensions:

  total 64
  drwxr-xr-x 5 luke luke  4096 Apr 12 16:32 .
  drwx-- 3 luke luke  4096 Apr 12 16:29 ..
  -rw-r--r-- 1 luke luke  4014 Apr  5 21:38 convenience.js
  -rw-r--r-- 1 luke luke 11442 Apr  5 21:38 extension.js
  drwxr-xr-x 2 luke luke  4096 Apr  5 21:38 icons
  -rw-r--r-- 1 luke luke  4211 Apr  5 21:38 indicator.js
  drwxr-xr-x 8 luke luke  4096 Apr  5 21:38 locale
  -rw-r--r-- 1 luke luke   388 Apr  5 21:38 metadata.json
  -rw-r--r-- 1 luke luke  9559 Apr  5 21:38 prefs.js
  drwxr-xr-x 2 luke luke  4096 Apr  5 21:38 schemas
  -rw-r--r-- 1 luke luke   451 Apr  5 21:38 stylesheet.css
  Output of ls -al /usr/share/gnome-shell/extensions:

  total 20
  drwxr-xr-x 5 root root 4096 Oct 17 13:27 .
  drwxr-xr-x 6 root root 4096 Mar 28 13:33 ..
  drwxr-xr-x 2 root root 4096 Oct 17 13:27 desktop-icons@csoriano
  drwxr-xr-x 3 root root 4096 Oct 17 13:27 ubuntu-appindicat...@ubuntu.com
  drwxr-xr-x 3 root root 4096 Mar 17 13:39 ubuntu-d...@ubuntu.com
  I've also tried resetting Gnome with dconf reset -f /org/gnome/

  Issue persists after a reset.

  Cheers!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 01:17:10 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2020-01-28 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20LSCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET59W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET59W(1.36):bd10/16/2019:svnLENOVO:pn20LSCTO1WW:pvrThinkPadL480:rvnLENOVO:rn20LSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LSCTO1WW
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872376/+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 1872376] [NEW] Application menu displays on right hand side of screen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Unsure if this bug should fall under xorg or Gnome.


When I click the "Show Applications" button, all the applications are displayed 
over on the right hand side of the primary screen. The dots to indicate which 
application page you're viewing appear over on the second monitor.

This only happens when using a second display.

Running Ubuntu 19.10.

Link to screenshot: https://i.stack.imgur.com/dkxgy.jpg

Output of ls -al ~/.local/share/gnome-shell/extensions:

total 64
drwxr-xr-x 5 luke luke  4096 Apr 12 16:32 .
drwx-- 3 luke luke  4096 Apr 12 16:29 ..
-rw-r--r-- 1 luke luke  4014 Apr  5 21:38 convenience.js
-rw-r--r-- 1 luke luke 11442 Apr  5 21:38 extension.js
drwxr-xr-x 2 luke luke  4096 Apr  5 21:38 icons
-rw-r--r-- 1 luke luke  4211 Apr  5 21:38 indicator.js
drwxr-xr-x 8 luke luke  4096 Apr  5 21:38 locale
-rw-r--r-- 1 luke luke   388 Apr  5 21:38 metadata.json
-rw-r--r-- 1 luke luke  9559 Apr  5 21:38 prefs.js
drwxr-xr-x 2 luke luke  4096 Apr  5 21:38 schemas
-rw-r--r-- 1 luke luke   451 Apr  5 21:38 stylesheet.css
Output of ls -al /usr/share/gnome-shell/extensions:

total 20
drwxr-xr-x 5 root root 4096 Oct 17 13:27 .
drwxr-xr-x 6 root root 4096 Mar 28 13:33 ..
drwxr-xr-x 2 root root 4096 Oct 17 13:27 desktop-icons@csoriano
drwxr-xr-x 3 root root 4096 Oct 17 13:27 ubuntu-appindicat...@ubuntu.com
drwxr-xr-x 3 root root 4096 Mar 17 13:39 ubuntu-d...@ubuntu.com
I've also tried resetting Gnome with dconf reset -f /org/gnome/

Issue persists after a reset.

Cheers!

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 01:17:10 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
InstallationDate: Installed on 2020-01-28 (75 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20LSCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET59W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LSCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET59W(1.36):bd10/16/2019:svnLENOVO:pn20LSCTO1WW:pvrThinkPadL480:rvnLENOVO:rn20LSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LSCTO1WW
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu
-- 
Application menu displays on right hand side of screen
https://bugs.launchpad.net/bugs/1872376
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 905147] Re: QPrinterDialog ignores default settings from CUPS

[Bug Watch Updater]

** Bug watch added: KDE Bug Tracking System #404510
   https://bugs.kde.org/show_bug.cgi?id=404510

** Bug watch added: KDE Bug Tracking System #383697
   https://bugs.kde.org/show_bug.cgi?id=383697

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

Title:
  QPrinterDialog ignores default settings from CUPS

Status in Qt:
  Won't Fix
Status in qt4-x11 package in Ubuntu:
  Fix Released

Bug description:
  KDE as well as many QT-Applications use QPrinterDialog as their
  printing dialog. Thing is: This dialog ignores default settings
  defined in CUPS - it doesn't even remember that last settings that
  were chosen. I know this is a QT issue but I kindly ask you not to
  close this bug as upstream and here's why:

  1. This bug has been around for years now - the first report to Nokia about 
was back in 2008 if I recall correctly. 
  2. A user doesn't know and doesn't care about whose fault it is. He just 
knows, that he set his printer settings to default to duplex in CUPS and that 
his QT applications don't print duplex. At first he might shrug and set duplex 
in the dialog. Next time the setting is back to simplex. The same is true for 
other options like collate and color settings. It's just a huge usability 
issue. 
  3. The fix below has been adopted by other major distributions for quite some 
time now. It works for duplex, collate and color settings. 
  4. It saves lots and lots of trees!

  I think it does not work for paper size and in general it doesn't fix
  the problem that QT can't remember the settings you choose in the
  print dialog. The paper size may be read from the configured defaults
  easily, too, but settings saving may be a bit harder. However, you'd
  implement this fix, you'd do something VERY good for Ubuntu -
  especially since 12.04 is meant to be an LTS release! If you could
  even improve the fix that would be huge!

  Here's the fix from the KDE bug tracker:
  https://bugs.kde.org/attachment.cgi?id=41187

  More info:
  https://bugs.kde.org/show_bug.cgi?id=180051
  https://bugreports.qt.nokia.com//browse/QTBUG-6471 (and 
https://bugreports.qt.nokia.com/browse/QTBUG-23037) and other bug reports from 
the comments there.

  For Oneiric I've made a patched version in a PPA of mine that you
  could look at. You'll see it's really a minor modification that
  doesn't take any effort at all to implement. You can find it here:
  https://launchpad.net/~dhertel/+archive/myfixes

  As a side note: I know that KDE is not the default environment in
  Ubuntu, but it's getting more important for people since Gnome2
  officially is no more and Unity isn't exactly better when one doesn't
  even like Gnome3 to begin with.

  So I hope this makes it into Precise...

  Cheers,
  Dominik

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/905147/+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 905147]

[Kevin-kofler]

The issue in this bug is already resolved in upstream Qt.

Your issue is a different issue, i.e., that there is no UI to set
default margins. Any settings you make in the print dialog are not
intended to be stored as defaults.

The place where you set default settings is using the print-manager KCM,
i.e., the Printer tab in Plasma System Settings. But there is no setting
for margins there. And of course not for "Force rasterization" which is
an Okular-specific setting.

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

Title:
  QPrinterDialog ignores default settings from CUPS

Status in Qt:
  Won't Fix
Status in qt4-x11 package in Ubuntu:
  Fix Released

Bug description:
  KDE as well as many QT-Applications use QPrinterDialog as their
  printing dialog. Thing is: This dialog ignores default settings
  defined in CUPS - it doesn't even remember that last settings that
  were chosen. I know this is a QT issue but I kindly ask you not to
  close this bug as upstream and here's why:

  1. This bug has been around for years now - the first report to Nokia about 
was back in 2008 if I recall correctly. 
  2. A user doesn't know and doesn't care about whose fault it is. He just 
knows, that he set his printer settings to default to duplex in CUPS and that 
his QT applications don't print duplex. At first he might shrug and set duplex 
in the dialog. Next time the setting is back to simplex. The same is true for 
other options like collate and color settings. It's just a huge usability 
issue. 
  3. The fix below has been adopted by other major distributions for quite some 
time now. It works for duplex, collate and color settings. 
  4. It saves lots and lots of trees!

  I think it does not work for paper size and in general it doesn't fix
  the problem that QT can't remember the settings you choose in the
  print dialog. The paper size may be read from the configured defaults
  easily, too, but settings saving may be a bit harder. However, you'd
  implement this fix, you'd do something VERY good for Ubuntu -
  especially since 12.04 is meant to be an LTS release! If you could
  even improve the fix that would be huge!

  Here's the fix from the KDE bug tracker:
  https://bugs.kde.org/attachment.cgi?id=41187

  More info:
  https://bugs.kde.org/show_bug.cgi?id=180051
  https://bugreports.qt.nokia.com//browse/QTBUG-6471 (and 
https://bugreports.qt.nokia.com/browse/QTBUG-23037) and other bug reports from 
the comments there.

  For Oneiric I've made a patched version in a PPA of mine that you
  could look at. You'll see it's really a minor modification that
  doesn't take any effort at all to implement. You can find it here:
  https://launchpad.net/~dhertel/+archive/myfixes

  As a side note: I know that KDE is not the default environment in
  Ubuntu, but it's getting more important for people since Gnome2
  officially is no more and Unity isn't exactly better when one doesn't
  even like Gnome3 to begin with.

  So I hope this makes it into Precise...

  Cheers,
  Dominik

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/905147/+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 905147]

[4-a-g]

Sorry, it seems that the issue isn't resolved.
Okular doesn't save the margins values nor the "Force rasterization" checkbox.
If I try to set the values as default, the print tool ignores them while a 
command-line lp works :
lpoptions -p Zebra -o page-bottom=0 -o page-left=0 -o page-right=0 -o 
page-top=0 -o fitplot

Kubuntu 19.04
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4

Quite the same as https://bugs.kde.org/show_bug.cgi?id=404510 or 
https://bugs.kde.org/show_bug.cgi?id=383697
So I tried with Kate and the values are saved in katerc : 
[Kate Print Settings][Margins]
bottom=0
left=0
right=0
top=0

Strangely I just migrated from Kubuntu 14.04 (KDE 4.13) to Kubuntu 19.04
(KDE 5.62) and I didn't face this issue on the previous computer.

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

Title:
  QPrinterDialog ignores default settings from CUPS

Status in Qt:
  Won't Fix
Status in qt4-x11 package in Ubuntu:
  Fix Released

Bug description:
  KDE as well as many QT-Applications use QPrinterDialog as their
  printing dialog. Thing is: This dialog ignores default settings
  defined in CUPS - it doesn't even remember that last settings that
  were chosen. I know this is a QT issue but I kindly ask you not to
  close this bug as upstream and here's why:

  1. This bug has been around for years now - the first report to Nokia about 
was back in 2008 if I recall correctly. 
  2. A user doesn't know and doesn't care about whose fault it is. He just 
knows, that he set his printer settings to default to duplex in CUPS and that 
his QT applications don't print duplex. At first he might shrug and set duplex 
in the dialog. Next time the setting is back to simplex. The same is true for 
other options like collate and color settings. It's just a huge usability 
issue. 
  3. The fix below has been adopted by other major distributions for quite some 
time now. It works for duplex, collate and color settings. 
  4. It saves lots and lots of trees!

  I think it does not work for paper size and in general it doesn't fix
  the problem that QT can't remember the settings you choose in the
  print dialog. The paper size may be read from the configured defaults
  easily, too, but settings saving may be a bit harder. However, you'd
  implement this fix, you'd do something VERY good for Ubuntu -
  especially since 12.04 is meant to be an LTS release! If you could
  even improve the fix that would be huge!

  Here's the fix from the KDE bug tracker:
  https://bugs.kde.org/attachment.cgi?id=41187

  More info:
  https://bugs.kde.org/show_bug.cgi?id=180051
  https://bugreports.qt.nokia.com//browse/QTBUG-6471 (and 
https://bugreports.qt.nokia.com/browse/QTBUG-23037) and other bug reports from 
the comments there.

  For Oneiric I've made a patched version in a PPA of mine that you
  could look at. You'll see it's really a minor modification that
  doesn't take any effort at all to implement. You can find it here:
  https://launchpad.net/~dhertel/+archive/myfixes

  As a side note: I know that KDE is not the default environment in
  Ubuntu, but it's getting more important for people since Gnome2
  officially is no more and Unity isn't exactly better when one doesn't
  even like Gnome3 to begin with.

  So I hope this makes it into Precise...

  Cheers,
  Dominik

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/905147/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Bug Watch Updater]

** Changed in: pango1.0 (Debian)
   Status: Unknown => New

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Debian:
  New

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport

[You-Sheng Yang]

Resent as https://lists.ubuntu.com/archives/kernel-
team/2020-April/108993.html

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  New
Status in apport source package in Focal:
  New
Status in linux-firmware source package in Focal:
  In Progress

Bug description:
  linux-firmware doesn't install any package hooks for apport, so it
  will only carry some default items leaving hardware list, kernel
  messages unattached. Suggest symlink /usr/share/apport/package-hooks
  /source_linux-firmware.py to source_linux.py as other linux image debs
  do in bug 1847967.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:
   
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1871695] Re: Bluetoothd uses 100% of a CPU thread

[Isaac Cohen]

Hi,

Here is what I got:


isaac@isaac-Inspiron-3583:~$ sudo gdb
GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) attach 794
Attaching to process 794
Reading symbols from target:/usr/local/libexec/bluetooth/bluetoothd...
Reading symbols from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libglib-2.0.so.0)
Reading symbols from target:/lib/x86_64-linux-gnu/libdbus-1.so.3...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libdbus-1.so.3)
Reading symbols from target:/lib/x86_64-linux-gnu/libdl.so.2...
Reading symbols from 
target:/usr/lib/debug//lib/x86_64-linux-gnu/libdl-2.30.so...
Reading symbols from target:/lib/x86_64-linux-gnu/libc.so.6...
Reading symbols from target:/usr/lib/debug//lib/x86_64-linux-gnu/libc-2.30.so...
Reading symbols from target:/lib/x86_64-linux-gnu/libpcre.so.3...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libpcre.so.3)
Reading symbols from target:/lib/x86_64-linux-gnu/libpthread.so.0...
Reading symbols from 
/usr/lib/debug/.build-id/7f/4107df84da625f1b445ade877e1e0ab6ba823d.debug...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Reading symbols from target:/lib/x86_64-linux-gnu/libsystemd.so.0...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libsystemd.so.0)
Reading symbols from target:/lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in target:/lib64/ld-linux-x86-64.so.2)
Reading symbols from target:/lib/x86_64-linux-gnu/librt.so.1...
Reading symbols from 
target:/usr/lib/debug//lib/x86_64-linux-gnu/librt-2.30.so...
Reading symbols from target:/lib/x86_64-linux-gnu/liblzma.so.5...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/liblzma.so.5)
Reading symbols from target:/lib/x86_64-linux-gnu/liblz4.so.1...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/liblz4.so.1)
Reading symbols from target:/lib/x86_64-linux-gnu/libgcrypt.so.20...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libgcrypt.so.20)
Reading symbols from target:/lib/x86_64-linux-gnu/libgpg-error.so.0...
(No debugging symbols found in target:/lib/x86_64-linux-gnu/libgpg-error.so.0)
--Type  for more, q to quit, c to continue without paging--
0x7f5bd69fbbf7 in __GI___poll (fds=0x55e26e5504c0, nfds=29, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) bt
#0  0x7f5bd69fbbf7 in __GI___poll (fds=0x55e26e5504c0, nfds=29, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5bd6b7daae in ?? () from 
target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5bd6b7de33 in g_main_loop_run () from 
target:/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x55e26e1a2959 in mainloop_run () at src/shared/mainloop-glib.c:79
#4  0x55e26e1a2dc0 in mainloop_run_with_signal (func=, 
user_data=0x0)
at src/shared/mainloop-notify.c:201
#5  0x55e26e10c5fe in main (argc=, argv=) at 
src/main.c:770
(gdb)

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

Title:
  Bluetoothd uses 100% of a CPU thread

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a bluetooth keyboard that I use for my laptop, which runs
  Kubuntu 19.04. I noticed though, that a short while after connecting
  the keyboard, the CPU fan goes on and one of the threads is at 100%.
  If I open a terminal and type "top", it shows that a process called
  bluetoothd is taking 12% of the CPU power which is a full thread
  (100/8=12.5). I'm not sure what it's doing, but it doesn't require
  that much CPU power to work. If I end the process and restart it, the
  keyboard works fine and the CPU is calm until it happens again (about
  20 minutes later). I reinstalled bluez and even tried recompiling from
  source, but the problem persists.

  My specs:

  Version of bluetoothd: 5.50
  Linux Kernel: 5.3.0-46-generic
  KDE Plasma Version 5.16.5


  Thank you,
  Isaac Cohen
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: 

[Touch-packages] [Bug 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

[Sameh Hashy]

Same issue here with vpnbook

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

Title:
  OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  After upgrading openssl on my Focal-install this morning (upgrade
  openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log),
  my OpenVPN tunnel refuses to connect to our corporate VPN (from
  /var/log/syslog):

  corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature 
digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, 
emailAddress=XX
  corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL 
routines:tls_process_server_certificate:certificate verify failed

  I'm told we're running a SHA1-signed CA, which we're guessing has been
  deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog
  for -2ubuntu4 mentions importing some upstream changes, but isn't more
  specific than that:
  https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1
  .1d-2ubuntu4/changelog

  As a work-around, the internet suggests two work-arounds (neither of
  which has worked for me):

  1) Adding the following to /etc/defaults/openssl:

  OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0"

  2) Adding the following to /etc/ssl/openssl.conf:

  CipherString= :@SECLEVEL=1

  I also tried rolling back the package, but the old version doesn't
  seem to be available:

  $ sudo apt install openssl=1.1.1d-2ubuntu3
  ...
  E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found

  
  I am no SSL-expert and would appreciate any pointers to get around this. (Our 
network-dept. does not have the bandwidth to roll over our CA on short notice, 
so I will need some other way to move ahead).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1872327] Re: OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

[Daniel Blatter]

That describes a work around:
https://wiki.archlinux.org/index.php/HP_Spectre_x360_13-4231ng#Brightness_/_backlight

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

Title:
  OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
  The hotkeys to adjust the OLED brightness do not work.

  Adjusting the display brightness editing the file brightness in
  /sys/class/backlight/intel_backlight doesn't work either. At
  /etc/default/grub I already added "acpi_backlight=vendor"

  I found an article, that fits to the topic:
  
http://reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux

  Regards Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8KZ06EA#UUZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872327/+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 1872327] Re: OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

[Daniel Blatter]

** Summary changed:

- Backlight brightness control on Intel Iris Plus Graphics G7 on 20.4 beta
+ OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

** Description changed:

  Hi
  
  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
- The hotkeys to adjust the backlight brightness do not work.
- It's no bug in KDE, as adjusting the brightness editing the file brightness 
in /sys/class/backlight/intel_backlight doesn't work either.
- At /etc/default/grub I already added "acpi_backlight=vendor"
+ The hotkeys to adjust the OLED brightness do not work.
+ 
+ Adjusting the display brightness editing the file brightness in
+ /sys/class/backlight/intel_backlight doesn't work either. At
+ /etc/default/grub I already added "acpi_backlight=vendor"
+ 
+ I found an article, that fits to the topic:
+ 
http://reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux
  
  Regards Daniel
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
-Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
+  Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
+    Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcEnviron:
-  LANGUAGE=de_CH:de
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=de_CH.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=de_CH:de
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=de_CH.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8KZ06EA#UUZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
  The hotkeys to adjust the OLED brightness do not work.

  Adjusting the display brightness editing the file brightness in
  /sys/class/backlight/intel_backlight doesn't work either. At
  /etc/default/grub I already added "acpi_backlight=vendor"

  I found an article, that fits to the topic:
  
http://reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux

  Regards Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: 

[Touch-packages] [Bug 1872336] Re: Text on Snap Store is garbled

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (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/1872336

Title:
  Text on Snap Store is garbled

Status in xorg package in Ubuntu:
  New

Bug description:
  Details:
  lsb_release -rd:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Steps:
  1. Launch Snap Store

  Expect:
  All the text to be in human-readable format/font.

  Actual:
  The text is garbled (Screenshot attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Apr 12 10:48:55 2020
  DistUpgraded: 2020-04-05 11:46:42,999 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:063e]
  InstallationDate: Installed on 2019-12-14 (119 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5547
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=6ab1d432-fbe5-4e12-98f6-886bc4101897 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-05 (6 days ago)
  dmi.bios.date: 11/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/05/2014:svnDellInc.:pnInspiron5547:pvrA06:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.sku: Inspiron 5547
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872336/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

[Joseph Yasi]

I currently have the package patched in my PPA to resolve the bug. It is
a difficult to debug problem that has been sending users upstream to
kodi with bug reports and confusing stack traces. This will get more
exposure when focal is released due to the LTS status.

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in alsa-plugins package in Ubuntu:
  New
Status in jackd2 package in Ubuntu:
  Confirmed
Status in jackd2 package in Debian:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

[Joseph Yasi]

Is this going to make it for focal? This bug causes kodi to crash when
turning my TV screen off.

** Tags added: focal

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in alsa-plugins package in Ubuntu:
  New
Status in jackd2 package in Ubuntu:
  Confirmed
Status in jackd2 package in Debian:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+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 1872336] [NEW] Text on Snap Store is garbled

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Details:
lsb_release -rd:
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

Steps:
1. Launch Snap Store

Expect:
All the text to be in human-readable format/font.

Actual:
The text is garbled (Screenshot attached)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Apr 12 10:48:55 2020
DistUpgraded: 2020-04-05 11:46:42,999 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:063e]
InstallationDate: Installed on 2019-12-14 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. Inspiron 5547
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=6ab1d432-fbe5-4e12-98f6-886bc4101897 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-05 (6 days ago)
dmi.bios.date: 11/05/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0598GM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/05/2014:svnDellInc.:pnInspiron5547:pvrA06:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA06:
dmi.product.family: 00
dmi.product.name: Inspiron 5547
dmi.product.sku: Inspiron 5547
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal third-party-packages ubuntu 
wayland-session
-- 
Text on Snap Store is garbled
https://bugs.launchpad.net/bugs/1872336
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 16700] Re: visudo: please use /tmp or other location for temporary file

[Bug Watch Updater]

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

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

Title:
  visudo: please use /tmp or other location for temporary file

Status in sudo package in Ubuntu:
  Won't Fix
Status in sudo package in Debian:
  Fix Released

Bug description:
  Automatically imported from Debian bug report #283161
  http://bugs.debian.org/283161

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/16700/+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 1872327] [NEW] Backlight brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

[Daniel Blatter]

Public bug reported:

Hi

I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
The hotkeys to adjust the backlight brightness do not work.
It's no bug in KDE, as adjusting the brightness editing the file brightness in 
/sys/class/backlight/intel_backlight doesn't work either.
At /etc/default/grub I already added "acpi_backlight=vendor"

Regards Daniel

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sun Apr 12 18:42:36 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
InstallationDate: Installed on 2020-04-03 (8 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
ProcEnviron:
 LANGUAGE=de_CH:de
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/02/2020
dmi.bios.vendor: AMI
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86FA
dmi.board.vendor: HP
dmi.board.version: 87.46
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
dmi.product.sku: 8KZ06EA#UUZ
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  Backlight brightness control on Intel Iris Plus Graphics G7 on 20.4
  beta

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
  The hotkeys to adjust the backlight brightness do not work.
  It's no bug in KDE, as adjusting the brightness editing the file brightness 
in /sys/class/backlight/intel_backlight doesn't work either.
  At /etc/default/grub I already added "acpi_backlight=vendor"

  Regards Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  

[Touch-packages] [Bug 1872318] Re: During Focal Beta install: nm-online crashed with SIGSEGV in g_source_set_ready_time()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1866783, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352637/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352639/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352648/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352649/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352650/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352652/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352653/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1866783

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  During Focal Beta install: nm-online crashed with SIGSEGV in
  g_source_set_ready_time()

Status in network-manager package in Ubuntu:
  New

Bug description:
  Apport pops up with this error during a clean installation of the
  Focal beta on my Dell XPS 9360 DE.

  The error popped up during the step after connecting with the wifi.
  Setup and installation proceed normally.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CasperVersion: 1.443
  Date: Sun Apr 12 16:29:55 2020
  ExecutablePath: /usr/bin/nm-online
  IpRoute:
   default via 192.168.178.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.178.0/24 dev wlp58s0 proto kernel scope link src 192.168.178.28 
metric 600
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcCmdline: /usr/bin/nm-online -s -q --timeout=30
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f55981eabf3 :   cmp
0x10(%rax),%rbp
   PC (0x7f55981eabf3) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-online crashed with SIGSEGV in g_source_set_ready_time()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE  
ACTIVE-PATH SLAVE  FILENAME 
 
   HEINZ!Box  3e2eb0c4-8e64-4703-bbe0-81e8492c21f3  wifi  1586709045  Sun Apr 
12 16:30:45 2020  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp58s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/HEINZ!Box.nmconnection
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp58s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  HEINZ!Box   
3e2eb0c4-8e64-4703-bbe0-81e8492c21f3  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp58s0  

[Touch-packages] [Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

[Klaus Bielke]

Sorry for bad handling. #4 is attachment belonging to #5

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

[Klaus Bielke]

Suggested workaround:

1. Copy file /lib/NetworkManager/conf.d/no-mac-addr-change.conf to dir
/etc/NetworkManager/conf.d/

2. Edit file /etc/NetworkManager/conf.d/no-mac-addr-change.conf: Move 2
lines with cloned-mac-address to new chapter [connection-mac-addr-
change-wifi], cf. attachment.

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

[Klaus Bielke]

** Attachment added: "no-mac-addr-change.conf"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+attachment/5352633/+files/no-mac-addr-change.conf

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1872303] Re: A print screen button doesn't work

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (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/1872303

Title:
  A print screen button doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  When I push a print screen button - nothing happens, instead of taking
  a screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 12 14:03:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Acer Aspire 5734Z
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5734Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.01
  dmi.modalias: 
dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5734Z
  dmi.product.sku: Montevina_Fab
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872303/+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 1872303] [NEW] A print screen button doesn't work

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I push a print screen button - nothing happens, instead of taking a
screenshot

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CasperVersion: 1.445
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sun Apr 12 14:03:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
MachineType: Acer Aspire 5734Z
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 5734Z
dmi.board.vendor: Acer
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.01
dmi.modalias: 
dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01:
dmi.product.family: Intel_Mobile
dmi.product.name: Aspire 5734Z
dmi.product.sku: Montevina_Fab
dmi.product.version: V1.01
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
A print screen button doesn't work
https://bugs.launchpad.net/bugs/1872303
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 1871417] Re: kernel update to 5.3.0-46.38 broke wifi

[Michael]

I was able to solve the problem.

1. 5.3.0-42 wifi worked
2. 5.3.0-46 wifi didn't work
3. booted into 5.3.0-42 with working wifi system
4. I used sudo lshw > lshw-42.txt to capture data
5. booted into 5.3.0-46 without working wifi
6. use sudo lshw > lshw-46.txt to capture data
7. I used diff command to compare the two .txt files
8. I determined that my hardware uses rtl8821ce driver but it wasn't working in 
5.3.0-46
9. stopping and starting network-manager didn't work
10. I used cd rtl8821ce/ then sudo ./dkms-remove.sh to change directories and 
remove the driver
11. when I attempted to reinstall the rtl8821ce drivers in 5.3.0-46, I 
discovered that the kernel update hadn't installed the 5.3.0-46 headers which 
prevented the wifi drivers from working.
11a. I was able to connect using bluetooth and my samsung G8 phone as hotspot.
12. I have Synaptic Program Manager so I was able to see the kernel headers 
weren't installed with the kernel update to 5.3.0-46.
13. After installing the 5.3.0-46 headers, the "paused" rtl8821ce driver 
install continued and "magically" the wifi started working!
14. performed restart and cold boot to verify wifi works again!

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

Title:
  kernel update to 5.3.0-46.38 broke wifi

Status in network-manager package in Ubuntu:
  New

Bug description:
  my system updated to 5.3.0-46.38 and now I no longer have wifi. The
  driver doesn't seem to be installed since when I go to setup, wifi
  isn't an available option.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 11:00:53 2020
  InstallationDate: Installed on 2019-10-29 (160 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
   enp2s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  ----   
   lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   disconnected  started  none  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871417/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Jeremy Bicha]

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

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

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Debian:
  Unknown

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1832057] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow

[XA Hydra]

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

Re-activated some PPAs, same as the others.

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

Title:
  software-properties-gtk crashed with TypeError in new_init(): could
  not convert value for property `transient_for' from
  DialogCacheOutdated to GtkWindow

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Falló actualización de repositorios

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.98.4
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 21:32:02 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-06-02 (5 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 
--toplevel 75497475
  ProcEnviron:
   LANGUAGE=es_SV:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_SV.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', 
'--toplevel', '75497475']
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with TypeError in new_init(): could 
not convert value for property `transient_for' from DialogCacheOutdated to 
GtkWindow
  UpgradeStatus: Upgraded to eoan on 2019-06-02 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1832057/+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 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

[Tim Richardson]

I installed 20.04 beta on a usb drive on the same machine, and reinstalled 
packages to resemble my main install as closely as possible. The bug does not 
occur when booting from the usb drive. 
The most significant difference I can think of is that the main install is on 
an lvm partition (unencrypted).

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

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

Status in plymouth package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

[Marcos R. Tosetti]

I have the same issue. Everything was working fine on 18.04, it only
stopped working after upgrading to 20.04. My phone (Android) can see the
wifi network (hotspot), it connects to it, it says it is connected but
there is no internet. I tried many different configurations, different
software, but nothing worked.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1872289] [NEW] Printer is Rady and has a job in queue but does not print

[Aleksandar]

Public bug reported:

.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.7
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 13:05:24 2020
InstallationDate: Installed on 2019-12-08 (125 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lpstat: device for HP-LaserJet-Pro-MFP-M125a: 
usb://HP/LaserJet%20Pro%20MFP%20M125a?serial=CNB6H97FLN=1
MachineType: HP HP Laptop 15-db1xxx
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-LaserJet-Pro-MFP-M125a.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-LaserJet-Pro-MFP-M125a.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=3bc8529f-571b-4178-b2b7-86c77fd3128f ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 85EA
dmi.board.vendor: HP
dmi.board.version: 51.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/27/2019:svnHP:pnHPLaptop15-db1xxx:pvrType1ProductConfigId:rvnHP:rn85EA:rvr51.16:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-db1xxx
dmi.product.sku: 8KP03EA#BED
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  Printer is Rady and has a job in queue but does not print

Status in cups package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 13:05:24 2020
  InstallationDate: Installed on 2019-12-08 (125 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lpstat: device for HP-LaserJet-Pro-MFP-M125a: 
usb://HP/LaserJet%20Pro%20MFP%20M125a?serial=CNB6H97FLN=1
  MachineType: HP HP Laptop 15-db1xxx
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-LaserJet-Pro-MFP-M125a.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-LaserJet-Pro-MFP-M125a.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=3bc8529f-571b-4178-b2b7-86c77fd3128f ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 85EA
  dmi.board.vendor: HP
  dmi.board.version: 51.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/27/2019:svnHP:pnHPLaptop15-db1xxx:pvrType1ProductConfigId:rvnHP:rn85EA:rvr51.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-db1xxx
  dmi.product.sku: 8KP03EA#BED
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1872289/+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 1872287] [NEW] I'm getting CPU freezing issues.

[vivek gangwar]

Public bug reported:

The bugs are related to CSGO, getting fps drops after few minutes of
usage.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
 GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 16:23:27 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed
 nvidia, 430.50, 5.3.0-46-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0]
InstallationDate: Installed on 2020-04-10 (1 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: ASUSTeK COMPUTER INC. GL553VD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=e042896c-2375-42c9-9d7d-2af9ed9e2121 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/02/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL553VD.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL553VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL553VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

Title:
  I'm getting CPU freezing issues.

Status in xorg package in Ubuntu:
  New

Bug description:
  The bugs are related to CSGO, getting fps drops after few minutes of
  usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:23:27 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed
   nvidia, 430.50, 5.3.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:15e0]
  

[Touch-packages] [Bug 1872286] [NEW] gio - cifs mount smb not possible "Location is not mountable"

[Dirk Heumann]

Public bug reported:

1) Release
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

2) Package
$ apt-cache policy libglib2.0-bin
libglib2.0-bin:
  Installed: 2.64.1-1
  Candidate: 2.64.1-1
  Version table:
 *** 2.64.1-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

3) Expected to happen
The path should be mounted at
/run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

4) What happened instead:
Error Message:
gio: smb://192.168.178.1/PathName/: Location is not mountable

5) Long description / explanation
Since some years, I mount a Windows drive with

gio mount smb://192.168.178.1/PathName

After upgrading from 19.04 to 20.04 beta, this does not work any more, I
get the error message

gio: smb://192.168.178.1/PathName/: Location is not mountable

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libglib2.0-bin 2.64.1-1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Apr 12 12:43:53 2020
InstallationDate: Installed on 2019-02-17 (420 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: glib2.0
UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1872286/+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 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

[Vikas Gill]

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

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
  https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  ---

  Happened during normal use of the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865300/+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 1872282] [NEW] Failed to get user record: Invalid argument

[Josef Hopfgartner]

Public bug reported:

system is ubuntu focal with pam_winbind and nss_winbind enabled.

unix users are not affected.
this bug won't happen with systemd version 2.44.3

beginning with version 245 (including 245.4-2) no user session will be created 
after login.
login itself works e.g. on tty2.
but loginctl does not show a corresponding user session.
gdm login needs a user session, so it fails.

this bug already seems to be handled here:
https://github.com/systemd/systemd/issues/15149

this bug only affects user sessions directly on a samba domain controller.
users can log in with pam_systemd version 245 on winbind client workstations in 
the same domain.

journalctl reports:
Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: 
pam_systemd(login:session): Failed to get user record: Invalid argument

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libpam-systemd:amd64 244.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Apr 12 11:44:41 2020
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Failed to get user record: Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  system is ubuntu focal with pam_winbind and nss_winbind enabled.

  unix users are not affected.
  this bug won't happen with systemd version 2.44.3

  beginning with version 245 (including 245.4-2) no user session will be 
created after login.
  login itself works e.g. on tty2.
  but loginctl does not show a corresponding user session.
  gdm login needs a user session, so it fails.

  this bug already seems to be handled here:
  https://github.com/systemd/systemd/issues/15149

  this bug only affects user sessions directly on a samba domain controller.
  users can log in with pam_systemd version 245 on winbind client workstations 
in the same domain.

  journalctl reports:
  Apr 10 14:11:23 joebook.netzagentur.localdomain login[21975]: 
pam_systemd(login:session): Failed to get user record: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-systemd:amd64 244.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Apr 12 11:44:41 2020
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872282/+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 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Ori Avtalion]

I'm seeing the "Could not install 'gconf2'" error during upgrade from
19.10 to the 20.04 beta.

The crash reports says the error is "dependency problems - leaving
triggers unprocessed"

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+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