[Touch-packages] [Bug 1973760] Re: Crash when using DIGEST-MD5 with SSF>=128

2022-05-22 Thread Bug Watch Updater
** Changed in: cyrus-sasl2 (Debian)
   Status: New => Fix Released

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

Title:
  Crash when using DIGEST-MD5 with SSF>=128

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I'm still troubleshooting this, but at the moment apps negotiating a
  DIGEST-MD5 authentication and requesting some form of transport
  encryption (ssf != 0) are crashing. The only example I have so far is
  the openldap client tools (so just one app really).

  ssf=0 works:
  $ ldapwhoami  -U ubuntu@lxd -w ubuntusecret -O maxssf=0
  SASL/DIGEST-MD5 authentication started
  SASL username: ubuntu@lxd
  SASL SSF: 0
  dn:uid=ubuntu@lxd,cn=vms,cn=digest-md5,cn=auth

  
  ssf=128 crashes:
  $ ldapwhoami  -U ubuntu@lxd -w ubuntusecret -O maxssf=128
  SASL/DIGEST-MD5 authentication started
  SASL username: ubuntu@lxd
  SASL SSF: 128
  SASL data security layer installed.
  Segmentation fault (core dumped)

  The crash seems to be inside openssl. I'll get a proper stack trace.

  2.1.27, also built with openssl3, does not crash. So far only 2.1.28
  (in kinetic-proposed).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1973760/+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 1971901] Re: dlltool uses non-unique temp filenames

2022-05-21 Thread Bug Watch Updater
Launchpad has imported 16 comments from the remote bug at
https://bugs.winehq.org/show_bug.cgi?id=52770.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2022-04-04T17:19:02+00:00 Bernhard Rosenkraenzer wrote:

Building wine 7.5 (with wine-staging patches, but they shouldn't be
relevant to this) with "make -j64" fails with

tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/rpcrt4/librpcrt4.delay.a --export \
  /home/bero/abf/wine/BUILD/wine-7.5/dlls/rpcrt4/rpcrt4.spec
/usr/bin/x86_64-w64-mingw32-dlltool: bfd_open failed reopen stub file: 
rpcrt4_dll_s00176.o: No such file or directory
winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
make: *** [Makefile:297034: dlls/rpcrt4/librpcrt4.delay.a] Error 1

Probably the library is assembled before all object files belonging to
it are built.

Building with make (without SMP) works.

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/11


On 2022-04-04T19:28:51+00:00 Cybermax wrote:

Is there a change if you build with lesser threads? Eg. make -j8 or
something assuming you have a threadripper with 32 cores/64 threads?

And possibly also interesting - distro, gcc and mingw-w64 version.

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/12


On 2022-04-04T19:36:49+00:00 Alexandre Julliard wrote:

These objects file are not created from the makefile. It sounds more
like it's running into some kind of resource limit.

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/13


On 2022-04-04T19:50:11+00:00 Cybermax wrote:

(In reply to Alexandre Julliard from comment #2)
> These objects file are not created from the makefile. It sounds more like
> it's running into some kind of resource limit.

tmpfs maybe? Just wondering since i got that exact error when building
wine on OBS.. Also got a couple of other very strange errors that failed
building on OBS with files that was not found, but could not find a
error message from the actual compile..

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/14


On 2022-04-08T13:04:47+00:00 Eric-pouech wrote:

I've run into a similar issue

looking at the compile traces lets me believe that the issue arises when two 
instances of mingw dlltool run at the same time, and thrashing each other 
temporary files

indeed, this ugly hack lets the compilation succeeds (it was failing almost 
always; sometimes on a different DLL)
---
diff --git a/tools/winebuild/import.c b/tools/winebuild/import.c
index c876d51f8e6..8049530a7e5 100644
--- a/tools/winebuild/import.c
+++ b/tools/winebuild/import.c
@@ -1595,7 +1595,11 @@ static void build_windows_import_lib( const char *lib_na>
 strarray_add( , lib_name );
 strarray_add( , "-d" );
 strarray_add( , def_file );
-
+strarray_add( , "-t" );
+{
+   char tmp[128]; sprintf(tmp, "%u\n", getpid());
+   strarray_add( , tmp );
+}
 switch (target.cpu)
 {
 case CPU_i386:
--
Bernhard, can you test this on your side?

I don't see a simple way to fix it...

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/15


On 2022-04-08T15:03:19+00:00 Eric-pouech wrote:

hmmm thinking about it, doesn't look quite right (or sufficient)

in the dlltool source code, if no -t prefix is given, will generate its own 
prefix based on pid...
need more investigation

Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils-
mingw-w64/+bug/1971901/comments/16


On 2022-04-08T15:31:06+00:00 Eric-pouech wrote:

I'm testing on two environments:
E1) with dlltool 2.38-1
E2) with dlltool 2.37-3

I see the error in E1 only 

on all env, I run 
> strace winebuild...  -v -v >& log
> grep exec log

results:

E2) 
pid 12272] execve("/usr/bin/x86_64-w64-mingw32-dlltool", 
["/usr/bin/x86_64-w64-mingw32-dllt"..., "-k", "-y", 
"dlls/iphlpapi/libiphlpapi.delay."..., "-d", "libiphlpapi.delay-625082dd.def", 
"-m", "i386:x86-64", "--as-flags=--64"], 0x7ffc19487b48 /* 56 vars */) = 0
[pid 12273] execve("/usr/bin/x86_64-w64-mingw32-as", 
["/usr/bin/x86_64-w64-mingw32-as", "--64", "-o", "daesh.o", "daesh.s"], 
0x7fffa1e12cf8 /* 56 vars */ 
[pid 

[Touch-packages] [Bug 1956603] Re: > Internal error: Could not resolve keysym ...

2022-05-21 Thread Bug Watch Updater
** Changed in: libx11-xcb-perl (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  > Internal error:   Could not resolve keysym ...

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11-xcb-perl package in Ubuntu:
  Fix Released
Status in x11-xkb-utils package in Ubuntu:
  Invalid

Bug description:
  Get lot of such warnings into Jammy logged;
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  

[Touch-packages] [Bug 1967626] Re: 22.04 beta Network Manager still sets wrong IPv6 routing

2022-05-20 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => Fix Released

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

Title:
  22.04 beta Network Manager still sets wrong IPv6 routing

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  that's a bug I've already reported earlier both to ubuntu and network-
  manager upstream, and nobody seems to care about.

  I'm using an AVM FritzBox, a router family very common in Germany and
  Europe for DSL and DOCSIS, but saw reports of people confirming the
  problem with other routers.

  The router sends ICMPv6 router advertisements, which contain for both
  the configured site-local address and the provider-assigned world-
  routable address range both a

  * prefix information 
  * router advertisement on itself

  All other OS and machines I have, including

  * Debian
  * Ubuntu Server
  * Ubuntu Core
  * Raspberry Pi OS
  * Other Linuxes
  * MacOS
  *...

  correctly set a link route on the network device for both the official
  and the site local address.

  Only Ubuntu Desktop machines with that damned Network Manager set a
  route to the router instead of a link route.

  The consequence is, that IPv6 still works, but significantly to slow,
  since packages are not switched on the network switch, but routed on
  the router, which dramatically decreases speed.

  
  I've reported this upstream to Network Manager, see the discussion on 

  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/840

  but they do not even seem to understand the issue (Network Manager
  written by people not really understanding routing...)

  Their point of view is that the router will fix things by sending
  redirects. However, ICMPv6 redirects are considered a security problem
  and usually recommended to be turned off.

  The answer from NetworkManager developers is to fix the router, not
  the Network Manager to stop sending router advertisings, but can't
  explain why all other OS and other Linux distributions, including
  Ubuntu server and Ubuntu core do it correctly, and just NM doing it
  wrong.

  So Ubuntu/NetworkManagers unability to fix or even notice this
  essential problem forces people to either accept terribly slow IPv6
  traffic in local networks, or to leave the machine open for ICMPv6
  redirects, which, in general, is a security flaw and vulnerable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1967626/+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 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning

2022-05-20 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Fix Released

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

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

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

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

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


-- 
Mailing list: https://launchpad.net/~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 1045790] Re: Rendering error on OCAL website

2022-05-20 Thread Bug Watch Updater
** Changed in: librsvg
   Status: Unknown => Fix Released

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

Title:
  Rendering error on OCAL website

Status in librsvg:
  Fix Released
Status in openclipart:
  Invalid
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  I uploaded an SVG that is a map of the UK and Ireland
  http://openclipart.org/detail/171939/uk-and-ireland-by-
  hellocatfood-171939 It was generated in Inkscape and then cleaned up
  using SVG Cleaner

  In Inkscape, GIMP and the Firefox SVG preview it displays correctly,
  but on OCAL it looks very weird!

  Steps to reproduce:
  Download the original SVG 
https://bugs.launchpad.net/librsvg/+bug/1045790/+attachment/3302221/+files/uk-ireland-vector_original.svg
  Download and install SVG Cleaner https://github.com/RazrFalcon/SVGCleaner/
  Run SVG Cleaner on the folder containing the SVG
  Look at the thumbnail preview on programs that use librsvg (Open Clip Art 
Library, Nautilus)

To manage notifications about this bug go to:
https://bugs.launchpad.net/librsvg/+bug/1045790/+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 1879417] Re: with default font, empty lines have different height to non-empty lines

2022-05-20 Thread Bug Watch Updater
** Changed in: pango
   Status: Unknown => Fix Released

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

Title:
  with default font, empty lines have different height to non-empty
  lines

Status in gedit:
  Fix Released
Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  I suspect this bug is not a gedit bug, but a font bug, however I'm not
  sure.

  Steps to reproduce:

  1) Ensure font is the default "Use the system fixed width font (Ubuntu
  Mono 13)" is checked.

  2) Create two tabs, in one tab write:

  1
  2
  3
  4

  In the other tab, write:

  
  
  
  4

  Switch between the tabs and observer that line 4 is in a different
  location in each tab.

  Using a different font "Monospace Regular 12" makes the problem go
  away, hence I suspect the problem is the font.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1879417/+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 1876518] Re: Gtk.Clipboard set_text() not working

2022-05-20 Thread Bug Watch Updater
** Changed in: pygobject
   Status: Unknown => New

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

Title:
  Gtk.Clipboard set_text() not working

Status in pygobject:
  New
Status in pygobject package in Ubuntu:
  Triaged

Bug description:
  Writing to Gtk.Clipboard doesn't work (reading works).

  Example code:

  #!/usr/bin/python3
  import gi
  gi.require_version('Gtk', '3.0')
  from gi.repository import Gtk, Gdk
  clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
  clipboard.set_text("Does a text of all texts contain itself?", -1)
  clipboard.store()

  Ubuntu 20.04 with Gtk 3.36.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1876518/+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 1892643] Re: [SRU] Update libgweather to 3.36.1

2022-05-20 Thread Bug Watch Updater
** Changed in: libgweather
   Status: Unknown => Fix Released

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  Fix Released
Status in libgweather package in Debian:
  Fix Released

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1892643/+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 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

2022-05-20 Thread Bug Watch Updater
** Changed in: libgweather
   Status: Unknown => Fix Released

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

Status in libgweather:
  Fix Released
Status in gnome-weather package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-weather source package in Focal:
  Confirmed
Status in libgweather source package in Focal:
  Confirmed
Status in gnome-weather package in Fedora:
  New

Bug description:
  [Impact]

  The weather forecast is not available since one week now. Also, the
  weather info is gone from gnome-shell.

  The weather service provider retired their old API.
  
https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  ==
  Version 3.36.2
  ==

  This version switches the yr.no backend to use met.no instead. Please note
  that this backport is only meant as a compatibility layer. Where at all
  possible, the newer libgweather 40 should be used as applications cannot
  fully comply with the met.no ToS otherwise.

  
  [Test case]

  - gnome-weather shows the weather forecast
  - gnome-shell shows the weather forecast in the calendar menu

  
  [Regression potential]

  - Weather forecast is totally broken now and can't be more broken.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  7 09:54:52 2021
  InstallationDate: Installed on 2020-04-26 (314 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder

2022-05-20 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Unknown => New

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

Title:
  File moved with Cut-Paste from a search filter still appears on
  original screen and if deleted disappears from new folder

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Confirmed
Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  Affected version
  Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and 
versions ago)

  I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 
1.5 month ago on Gitlab Gnome without any answer nor review:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723

  Resume: File moved with "Cut" from a window with an active search
  filter, and pasted in another folder on a second Nautilus window (not
  a subfolder), still appears on the first original screen (list is not
  automatically updated) - and if deleted from here, actually they
  disappear from the new folder !

  It can occur to loose important documents  - I often make direct
  shift-deletes, without recycler storage...

  Steps to reproduce
  I open a Nautilus window, go to a folder and make a search filter, for 
example 20 files appear on the window which name contains my search filter.

  If I select one of them, make Cut / Ctrl-X, open a new Nautilus
  window, go to another folder (which is not a subfolder of the first)
  and make Paste / Ctrl-V, it wells copy the file in the new folder.

  If I switch to the first Nautilus window with the original folder and
  search filter active, the moved file still appears on the list and I
  can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so
  I shift-delete it, it disappears from the list and only 19 files
  remain.

  Current behavior
  But… If I go to the second Nautilus window and the 2nd folder, the file has 
also disappeared from it ! File in the first window was "transformed" to a link 
instead of being removed, and suppressing it also deletes the file in its new 
folder - in my case, I lost several documents like this because of Shift-Delete 
and not trash use.

  Expected behavior
  After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) 
moved from the first one should not be still visible in the search list, there 
should be an automatic refresh.

  If I do a Copy-Paste instead of a Cut-Paste, problem does not occur:
  delete only removes file in the fist original folder, not on the
  second. If I close the search filter, it's also OK, file(s) moved no
  more visible. And of course, if after Cut I stay in the same Nautilus
  window and go to another folder to paste, no problem: bug only occurs
  in case of a second window opened.

  Thanks in advance and best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1917152/+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 1627564] Re: Various apps crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493/494]

2022-05-20 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  Various apps crash due to assertion failure in
  ensure_surface_for_gicon [gtkiconhelper.c:493/494]

Status in GTK+:
  Fix Released
Status in debconf package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in debconf source package in Focal:
  Confirmed
Status in gtk+3.0 source package in Focal:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
  https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383
  https://errors.ubuntu.com/problem/519aee3ed0c68efc5b754ee3e783103e59361d46

  ---

  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1627564/+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 1635803] Re: dragging file with middle mouse button doesn't show "Copy/Move/Link" context menu

2022-05-20 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => New

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

Title:
  dragging file with middle mouse button doesn't show "Copy/Move/Link"
  context menu

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  middle mouse a file, drag and drop it used to bring out a copy, move, etc 
dialog. This is now missing in 16.10.
  Can we please have this back, and an option to make the shortcut using 
rightclick + drag would be an improvement also.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 22 19:14:18 2016
  InstallationDate: Installed on 2016-10-14 (8 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1635803/+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 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click

2022-05-20 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  Maximize vertically/horizontally doesn't work (in some apps) if
  configured via middle-click

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1698083/+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 1864307] Re: Many apps have no icon in Software on Focal

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-software
   Status: Unknown => Fix Released

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Fix Released
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

  
  [Impact] 

   * Some apt packages do not include an icon in snap-store

  [Test Case]

   * Open snap-store, search for GCompris and confirm there is an
  appropriate icon

  [Regression Potential]

   * Very low.  Previous Ubuntu releases including apt-config-icons
  based on the depends in gnome-software.  This just adds an apt config
  that can be used to fetch icons for apt packages via apt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1703377] Re: Gnome online account login prevents paste or autotype

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => New

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

Title:
  Gnome online account login prevents paste or autotype

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  On entering Login data to an online account such as google.

  Using keepass as password manager I now can not enter my password via
  paste nor via autotype. Trying any of them results in an invalid
  password.

  Ubuntu 16.10 - GNOME Shell 3.20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1703377/+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 1756006] Re: Support suspend-then-hibernate

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-settings-daemon
   Status: Unknown => New

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

Title:
  Support suspend-then-hibernate

Status in GNOME Settings Daemon:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Triaged

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1756006/+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 1733002] Re: Google Online Account Two Factor with hardware key fails immediately

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => New

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

Title:
  Google Online Account Two Factor with hardware key fails immediately

Status in gnome-online-accounts:
  New
Status in Webkit:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  The hardware key authentication two factor fails immediately with a
  web based retry dialogue when connecting a Google account to the
  online accounts in settings using a hardware key second factor.

  Steps to reproduce:
  1. Set Google Account to default to a hardware security key like a Yubikey or 
other FIDO standard key after having two factor authentication enabled on your 
Google Account.
  2. Open Online accounts
  3. Add a Google Account
  4. Enter google email address
  5. Enter google password
  6. (this is the login flow of two factor, if default is the hardware key the 
error should appear).

  Work around:
  Choose use another method to authenticate: enter the authentication code and 
you will proceed.

  Expectations were:
  The ability to use the hardware key to authenticate as the second factor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 17 16:01:11 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+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 1877219] Re: dozens of empty grilo-plugin-cache folders polluting /tmp

2022-05-20 Thread Bug Watch Updater
** Changed in: grilo-plugins
   Status: Unknown => Fix Released

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

Title:
  dozens of empty grilo-plugin-cache folders polluting /tmp

Status in Grilo Plugins:
  Fix Released
Status in grilo-plugins package in Ubuntu:
  New

Bug description:
  My /tmp folder has dozens of empty folders with names like grilo-
  plugin-cache-ABCDEF. I don't know anything about grilo-plugins, but
  surely they can do their job without leaving endless garbage
  directories behind when they're done?

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  $ dpkg-query --show grilo-plugins-0.3-base
  grilo-plugins-0.3-base:amd64  0.3.9-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/grilo-plugins/+bug/1877219/+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 1882092] Re: goa-daemon Error resolving “autodiscover.outlook.office365.com”

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => New

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

Title:
  goa-daemon Error resolving “autodiscover.outlook.office365.com”

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Evolution is no longer receiving able to refresh Inbox from Exchange Web 
Services.
  `journalctl` provides the following clues

  systemd-resolved: Server returned error NXDOMAIN, mitigating potential DNS 
violation DVE-2018-0001, retrying transaction with reduced feature level UDP
  goa-daemon: goa_ews_client_autodiscover() failed: 2 — Error resolving 
“autodiscover.outlook.office365.com”: Name or service not known

  This may be upstream issue https://gitlab.gnome.org/GNOME/gnome-
  online-accounts/-/issues/57

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  $ apt-cache policy gnome-online-accounts
  gnome-online-accounts:
Installed: 3.28.0-0ubuntu2.1
Candidate: 3.28.0-0ubuntu2.1
Version table:
   *** 3.28.0-0ubuntu2.1 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.0-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-online-accounts 3.28.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  4 17:11:45 2020
  InstallationDate: Installed on 2018-01-10 (875 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to bionic on 2019-02-12 (478 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1882092/+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 1911036] Re: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_f

2022-05-20 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  GDK/GTK app crash in XFCE when performing drag operation (in
  gdk_window_cache_new <- gdk_window_cache_get <-
  drag_context_find_window_cache <- gdk_x11_drag_context_find_window)

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Released

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 

[Touch-packages] [Bug 1922047] Re: Touchpad scrolling is too fast

2022-05-20 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1922047/+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 1877754] Re: GTKFileChooser: deselect highlighted directory

2022-05-20 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  GTKFileChooser: deselect highlighted directory

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Open a random file save form (gedit, LibreOffice doesn't matter).

  Sometimes the first entry in the file list gets highlighted
  automatically which may be a folder (especially when it is not the
  first time you save a file). So the user may click on another entry to
  change the selection, but clicking on the background *does not cause*
  a deselection to take place. In my opinion that would be an expected
  usage pattern as it is the case on common other platforms.

  Why is that important? Sometimes the user just needs to choose the
  current working directory and not a particular folder/file (he doesn't
  want to have the file stored in a subfolder). The only valid (and
  nasty) workaround is to go one hierarchy upwards and then double-click
  the directory folder. The folder gets opened and the user finally
  finds him/her-self with no entry highlighted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1877754/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => New

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

Title:
  Nextcloud account added to Online Accounts does not populate Calendar
  apps (WebDAV file sharing does work)

Status in gnome-online-accounts:
  New
Status in evolution-data-server package in Ubuntu:
  Fix Released

Bug description:
  My Nextcloud server was working fine with previous versions of Ubuntu,
  but on the 20.04 daily when I add my Nextcloud account it does not
  populate my Calendars or todo lists. It does give me file access via
  WebDAV. Server is working fine as far as I'm aware. Going to Settings
  -> Administration - Overview shows me any configuration issues it can
  detect, currently the only error there is related to background job
  execution (which is only relevant to the News app if I'm not
  mistaken).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-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-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 23:59:55 2020
  InstallationDate: Installed on 2020-04-03 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+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 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

2022-05-20 Thread Bug Watch Updater
** Changed in: glib
   Status: Unknown => Fix Released

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Released

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every time. The unwritten bytes if you do a bindiff from before
  and after will be all set to zero.

  [Where problems can occur]

  I am doubtful that any programs are relying on buggy non-deterministic
  behaviour from random bytes found in 

[Touch-packages] [Bug 1901603] Re: Couldn't connect to my nextcloud account (GOA)

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => New

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

Title:
  Couldn't connect to my nextcloud account (GOA)

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Connection to my nextcloud account with Gnome-Online-Accounts is not possible
  This happened after upgrading Ubuntu to 20.10.
  It worked fine with 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 26 20:37:07 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-10-15 (10 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1901603/+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 1872980] Re: Add field for PresentationIdentity in Online Accounts GUI

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => New

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

Title:
  Add field for PresentationIdentity in Online Accounts GUI

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Version: focal,now 3.36.0-1ubuntu1 amd64

  ~/.config/goa-1.0/accounts.conf has a field called
  PresentationIdentity. When setting up a Google Account for example,
  that field gets set to the email address. This field is used in places
  like Nautilus to show which accounts something is connected to. If the
  addresses are similar (and long) this can be a bit confusing.

  Example:

  johnjacobjingleheilmerschm...@gmail.com
  johnjacob...@school.edu

  If there were an option in the GUI to set the name (to Gmail and
  School in this example), there would be less confusion in places like
  Nautilus.

  Visual Example:

  __|
  johnjacobj|
  johnjacobj|
  __|

  Becomes:

  __|
  Gmail |
 School |
  __|

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1872980/+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 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

2022-05-20 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Fix Released

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Impish:
  Fix Released

Bug description:
  * Impact

  The clipboard copies from GTK based software sometime stop working
  under wayland

  * Test Case

  - in a wayland session try to copy text between software, from firefox
  to gedit for example, it should work in a consistent manner

  alternative testcase inspired from the gitlab ticket
  - install wl-clipboard
  - use evince to open a pdf
  - select and copy some content
  - on a cmdline do 
  $ wl-paste -t TEXT
  - try to paste then in another software, gedit for example

  the copied text should be pasted

  
  * Regression potential

  The changes are in the wayland selection source so the impact should
  only be for wayland users and limited to clipboard interactions

  
  --

  
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on 
Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1913775/+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 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

2022-05-20 Thread Bug Watch Updater
** Changed in: gobject-introspection
   Status: Unknown => New

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

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in GObject Introspection:
  New
Status in appstream package in Ubuntu:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Confirmed
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Fix Released

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests/test-
  command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1903574/+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 1884126] Re: Trying to add google account fails with AUTH-1140

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => New

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

Title:
  Trying to add google account fails with AUTH-1140

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Trying to add a google account that redirects to another site for sign
  in results in a window with the following error:

  {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
  an invalid header value that can't be parsed."}]}

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:41:17 2020
  InstallationDate: Installed on 2019-08-17 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1884126/+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 1966529] Re: xdg-desktop-portal-gnome crashed with SIGSEGV in gtk_tree_view_update_rubber_band_selection_range.constprop.0()

2022-05-20 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => New

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

Title:
  xdg-desktop-portal-gnome crashed with SIGSEGV in
  gtk_tree_view_update_rubber_band_selection_range.constprop.0()

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/44bd0ca893055a3c496a03038023a8d0d4860802

  ---

  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  xdg-desktop-portal-gnome:
    Instalado: 42.0.1-1
    Candidato: 42.0.1-1
    Tabela de versão:
   *** 42.0.1-1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal-gnome 42.0.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Mar 25 20:29:58 2022
  ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome
  ProcCmdline: /usr/libexec/xdg-desktop-portal-gnome
  SegvAnalysis:
   Segfault happened at: 0x7fe18cf2c03f:movzwl (%rsi),%edx
   PC (0x7fe18cf2c03f) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal-gnome
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: xdg-desktop-portal-gnome crashed with SIGSEGV in g_signal_emit_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1966529/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM

2022-05-20 Thread Bug Watch Updater
** Changed in: gsettings-desktop-schemas
   Status: Unknown => New

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

Title:
  Time for the US is shown in 24h format. It should be 12h with AM/PM

Status in GSettings Desktop Schemas:
  New
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  Source- https://time.gov/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1872153] Re: SIGSEGV in g_source_set_ready_time()

2022-05-20 Thread Bug Watch Updater
** Changed in: glib
   Status: Unknown => Fix Released

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

Title:
  SIGSEGV in g_source_set_ready_time()

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  cuando abro software ubuntu ma  aparece tramsparente sin fondo iconos
  solos

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.0-1ubuntu1
  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: GNOME-Greeter:GNOME
  Date: Fri Apr 10 19:48:54 2020
  ExecutablePath: /usr/libexec/gsd-usb-protection
  InstallationDate: Installed on 2020-04-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/gsd-usb-protection
  ProcEnviron:
   LANG=es_AR.UTF-8
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7faa5f4a2bf3 :   cmp
0x10(%rax),%rbp
   PC (0x7faa5f4a2bf3) 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: gnome-settings-daemon
  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: gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1872153/+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 1879417] Re: with default font, empty lines have different height to non-empty lines

2022-05-20 Thread Bug Watch Updater
** Changed in: gedit
   Status: Unknown => Fix Released

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

Title:
  with default font, empty lines have different height to non-empty
  lines

Status in gedit:
  Fix Released
Status in Pango:
  Unknown
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  I suspect this bug is not a gedit bug, but a font bug, however I'm not
  sure.

  Steps to reproduce:

  1) Ensure font is the default "Use the system fixed width font (Ubuntu
  Mono 13)" is checked.

  2) Create two tabs, in one tab write:

  1
  2
  3
  4

  In the other tab, write:

  
  
  
  4

  Switch between the tabs and observer that line 4 is in a different
  location in each tab.

  Using a different font "Monospace Regular 12" makes the problem go
  away, hence I suspect the problem is the font.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1879417/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2022-05-20 Thread Bug Watch Updater
** Changed in: glib
   Status: Unknown => Fix Released

-- 
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 GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Triaged

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/glib/+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 1881812] Re: gdm can't open session for ldap users with usernames that begin with a number

2022-05-20 Thread Bug Watch Updater
** Changed in: gdm
   Status: Unknown => Fix Released

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

Title:
  gdm can't open session for ldap users with usernames that begin with a
  number

Status in gdm:
  Fix Released
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Description:Ubuntu 20.04 LTS

  with ubuntu-desktop and libnss-ldapd

  Trying to log in to the desktop environment when the username (e.g
  9912345) begins with a number results in a black screen, and then
  quits back to the log in screen.

  Here is the error:
  `...gdm-password][5010]: pam_systemd(gdm-password:session): Failed to get 
user record: Invalid argument`

  However, these users can log-in via ssh, and via TTY without issue.

  This error does not occur if I log in with other users, without a
  number (e.g. test.user)

  Also, the error does not occur if I switch to LightDM.  With LightDM,
  a username such as 9912345 can login to the desktop desktop
  environment.

  $ apt-cache policy gdm3
  gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
   *** 3.34.1-1ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1881812/+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 1870508] Re: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

2022-05-20 Thread Bug Watch Updater
** Changed in: atk
   Status: Unknown => Fix Released

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

Title:
  ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

Status in ATK:
  Fix Released
Status in atk1.0 package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. Boot to ubiquity-dm
  2. Enable the screenreader (Alt+Super+S)
  3. Select "Install Ubuntu"
  4. Proceed with all the steps of the installer

  = Actual Result = 
  During installation, when the slideshow is running, this crash occurs.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  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-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 10:55:58 2020
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  ExecutableTimestamp: 1585729537
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcCwd: /
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7fbd15f8f16a :   
mov%rax,-0x20(%rsp)
   PC (0x7fbd15f8f16a) ok
   source "%rax" ok
   destination "-0x20(%rsp)" (0x7ffe329d3ff0) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   g_type_check_instance_is_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
  Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/atk/+bug/1870508/+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 1864215] Re: Please add webp loader to gdk-pixbuf

2022-05-20 Thread Bug Watch Updater
** Changed in: gdk-pixbuf
   Status: Unknown => Fix Released

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

Title:
  Please add webp loader to gdk-pixbuf

Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Baltix:
  Triaged
Status in Debian:
  New

Bug description:
  Attempting to load a webp image -- for instance, 

https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp
  or

https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg
  -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file 
format" error.

  Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in
  libwebp, but isn't this really a gdk-pixbuf issue? If it really does
  belong to libwebp, my apologies, please dup this bug to 1407644 (I'm
  confident it doesn't belong to eog since I don't use that program; I
  have other programs that use libgdk-pixbuf).

  You can probably use eog to test this, or run
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i 
webp
  (I assume the loader would mention webp if there was a loader for it).

  I have these packages installed in addition to libgdk-pixbuf2.0-0:
  libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes
  the format:

  $ file /tmp/FKK78W.jpg.webp
  /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 
1200x533, Scaling: [none]x[none], YUV color, decoders should clamp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  Date: Fri Feb 21 08:48:36 2020
  InstallationDate: Installed on 2019-10-10 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

2022-05-20 Thread Bug Watch Updater
** Changed in: glib
   Status: Unknown => Fix Released

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1916701/+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 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

2022-05-20 Thread Bug Watch Updater
** Changed in: evolution-data-server
   Status: Unknown => New

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

Status in evolution-data-server:
  New
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  I use google calendar.  Events are created and updated via the
  browser. The calendar feed is configured through settings/online
  accounts. I can see upcoming events in the calendar drop down. The
  calendar and desktop are configured for the same timezone, and alerts
  normally appear simultaneously on my phone and desktop.

  I know sometimes stale calendar entries can be a factor, but I don't
  *think* that's an issue at this time (the change was made almost 24
  hours ago, I don't see the API limit errors I used to see in logs).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 15:02:11 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (666 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   linux-image-5.8.0-49-generic
   linux-base
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1923893/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-bluetooth
   Status: Unknown => Fix Released

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1926062/+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 1952107] Re: Google Contacts API Deprecated

2022-05-20 Thread Bug Watch Updater
** Changed in: evolution-data-server
   Status: Unknown => Fix Released

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Triaged
Status in evolution-data-server source package in Focal:
  Triaged
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

2022-05-20 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Unknown => Fix Released

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

Title:
  pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from
  pa_x11_wrapper_unref()

Status in X.Org X server:
  Fix Released
Status in libx11 package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584

  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  Uname: Linux 5.13.13-xanmod1-cacule x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anasc  1719 F pulseaudio
   /dev/snd/pcmC0D0p:   anasc  1719 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Aug 28 21:00:59 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-08-26 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  SegvAnalysis:
   Segfault happened at: 0x7fbcc9d6a8a4 :  mov%edx,0x4(%rax)
   PC (0x7fbcc9d6a8a4) ok
   source "%edx" ok
   destination "0x4(%rax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6
   XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
   pa_x11_wrapper_unref () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
   module_x11_publish_LTX_pa__done () from 
/usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
  Title: pulseaudio crashed with SIGSEGV in XFreeGC()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/05/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.36
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 5SU52EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1941962/+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 1497593] Re: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed.

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
  [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data:
  Assertion `kref' failed.

Status in Mesa:
  New
Status in libdrm package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref'
  failed. Because nouveau is not thread safe(?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1497593/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
  Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref()
  especially with multiple monitors, webbrowser-app or system settings

Status in Canonical System Image:
  Triaged
Status in Mesa:
  New
Status in Mir:
  Triaged
Status in Nouveau Xorg driver:
  Unknown
Status in Unity System Compositor:
  Triaged
Status in libdrm package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  Unit8 froze up while I was trying to open system settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 19:12:54 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-05-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8
  SegvAnalysis:
   Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx
   PC (0x7f58d568706c) ok
   source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: unity8 crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1654839] Re: shared-mime-info detects all binary files as shared libraries

2022-05-20 Thread Bug Watch Updater
** Changed in: shared-mime-info
   Status: Unknown => Fix Released

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

Title:
  shared-mime-info detects all binary files as shared libraries

Status in shared-mime-info:
  Fix Released
Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Initially I reported bug to KDE but it's a shared-mime-info issue.
  https://bugs.kde.org/show_bug.cgi?id=373220

  All binary files are detected as application/x-sharedlib but should be
  application/x-executable.

  This started to happen in Kubuntu 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1654839/+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 1824260] Re: wrong kerning in SS-5 PDF form fields

2022-05-20 Thread Bug Watch Updater
** Changed in: fontconfig
   Status: Unknown => Fix Released

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Fix Released

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1824260/+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 1794033] Re: i965: Failed to submit batchbuffer: Bad address

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1794033/+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 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - distorted audio

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  [Asus GX531GX] Internal speakers are sometimes noisy - distorted audio

Status in PulseAudio:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB
  headphones. When the headphones are plugged in during boot the
  internal speakers won't work. There is only crackling sound coming
  from them. It doesn't help in I unplug the headphones. There is no
  problem if they are not plugged in during boot. I'm using Ubuntu
  19.10.

  Please let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Jan 26 19:26:35 2020
  InstallationDate: Installed on 2019-12-19 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GX531GXR.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GX531GXR
  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.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Zephyrus S
  dmi.product.name: Zephyrus S GX531GXR_GX531GXR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1860930/+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 1865411] Re: Need to restart Network Manager frequently

2022-05-20 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => Fix Released

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

Title:
  Need to restart Network Manager frequently

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My WiFi connection keeps stopping to work every once in a while
  (sometimes as often as every 10 minutes).

  Restarting NetworkManager usually resolves this problem. But I am not
  sure why that is the case. I do not think there is a connectivity
  issue as it happens even when I am right next to the access point.

  I have a standard Intel Wireless chip and use GNOME shell with some
  extensions. Nothing exotic.

  Note this happened on eoan as well as focal (and maybe even before
  that).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.8-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  1 19:56:11 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-07-09 (236 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.24 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/fish
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.8   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1865411/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  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/mesa/+bug/1871959/+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 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  PulseAudio doesn't see analog output on Dell Inspiron 6400 with
  STAC9200

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio currently doesn't see the analog audio output in my Dell
  Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
  SPDIF output. This is the situation in both "pactl list sinks" and
  pavucontrol. I hear no sound from applications, probably because it's
  going to SPDIF. I don't have a way to listen to SPDIF to see if that
  is indeed the case.

  ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
  through the laptop's speakers.

  This problem never happened in Ubuntu 19.10 and earlier. It might have
  worked earlier in 20.04 also, but I'm not sure of that. Rebooting
  didn't help. Purging and reinstalling pulseaudio and its automatically
  installed dependencies didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1414 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 14 13:37:43 2020
  InstallationDate: Installed on 2012-01-19 (3008 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1872791/+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 1878094] Re: Ubuntu 20.04 / Pulseaudio RTP receive broken sound

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Ubuntu 20.04 / Pulseaudio RTP receive broken sound

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  just upgraded some of my computers to Ubuntu 20.04, also tried with
  fresh install, in all case the pulseaudio rtp receive module is giving
  me very poor sound.

  Easily reproducible on a single machine :

  pacmd load-module module-null-sink sink_name=MyNullSink
  pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true
  pacmd load-module module-rtp-recv

  And then play something in the null sink, loopback sound will be bad
  (lags).

  What I noticed : if I open the rtp stream with vlc, it's ok, sound is
  good.

  Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which
  implements RTP through gstreamer, which is new.

  So I tested my rtp stream with gstreamer:

  gst-launch-1.0 udpsrc address=224.0.0.56 port=46586
  caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" !
  .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample !
  pulsesink

  And it works fine, so I definitively believe there is an issue in the
  new module-rtp-recv.so bundled with PulseAudio and that is now based
  on gstreamer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC2', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 11 22:22:55 2020
  InstallationDate: Installed on 2019-03-31 (407 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-09 (2 days ago)
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1404
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX H370-I GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1404:bd09/13/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXH370-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [deleted]
  mtime.conffile..etc.pulse.daemon.conf: 2020-05-10T12:17:27.278185
  mtime.conffile..etc.pulse.default.pa: 2020-05-10T12:13:15.278817
  mtime.conffile..etc.pulse.system.pa: 2020-05-11T16:24:47.654012

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1878094/+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 1878617] Re: Apple pages file type should be added to MIME types

2022-05-20 Thread Bug Watch Updater
** Changed in: shared-mime-info
   Status: Unknown => Fix Released

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

Title:
  Apple pages file type should be added to MIME types

Status in shared-mime-info:
  Fix Released
Status in mime-support package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Fix Committed

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 1875369] Re: recording device won't change

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  recording device won't change

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  installed from lubuntu .iso
  fully updated as of yesterday
  fresh boot this morning

  some of these details are most likely irrelevant, but it's what i do to keep 
things simple:
  ignore graphical login screen, change to VT2
  startx /usr/bin/xterm

  in the xterm:
  /opt/firefox/firefox&  #(nightly)
  openbox&
  pavucontrol-qt&
  pavucontrol&#results are the same regardless which of the pavucontrols is 
invoked

  in firefox:
  voice.google.com
  start a call

  in either of the pavucontrols:
  try to change the recording device:
  the menu opens, select the desired device, but it just doesn't change.
  doesn't matter which of the two pavucontrols was invoked

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 27 07:49:12 2020
  InstallationDate: Installed on 2020-03-15 (42 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ETA2WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6008SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E540
  dmi.product.name: 20C6008SUS
  dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1875369/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  New
Status in pulseaudio source package in Kinetic:
  Triaged
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1879905] Re: Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

2022-05-20 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => Fix Released

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

Title:
  Can no longer connect to Ubuntu WPA hotspot  after upgrade to 20.04

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  I upgraded my Ubuntu client to 20.04 and could continue to connect to
  my WPA Hotspot running on an Ubuntu server. Upon update of the server
  to 20.04 I could no longer connect with any of my various client OSs.

  After using the updated network-manager from
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1870359, I can now connect to the hotspot from all of my
  machines running many flavors of OS (Windows, MacOS, Android, Ubuntu
  19.10), but I cannot connect from my machine running Ubuntu 20.04.

  If I turn off the encryption on the hotspot or turn on WEP encryption
  (using nm-connection-editor), then I can connect.

  Seeing that my client running 19.10 can connect, I'm not sure if this
  is a problem specif to my particular laptop running 20.04, or if it is
  rather a problem that any client updating to 20.04 will have. I will
  update my other 19.10 machine, that is currently working with the WPA
  hotspot, to help differentiate between these two possibilities.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:00 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #dns-nameservers 8.8.8.8 8.8.4.4
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
  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/network-manager/+bug/1879905/+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 1882587] Re: Truncated audio frequency response on snd-aloop device (resample-method = speex-float-1)

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  Truncated audio frequency response on snd-aloop device (resample-
  method = speex-float-1)

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi. I've found something strange happening when I record the output of
  a sound card through loopback device audio monitor.

  If I load the snd-aloop module, then setup a player to play a chirp sound 
that spans a sine wave between 10Hz and 22kHz through it, and then record the 
virtual monitor device through Audacity it drops the frequencies something over 
16kHz like it have a low pass filter on it.
  The  sampling rate is 44100 or 48000, it doesn't matters, the result is the 
same.

  Also in some cases I found that the signal path between channels
  doesn't have correct syncing. A chirp sound is ideal for testing,
  because if there is some delay between channels, it would produce a
  comb filter like frequency response on the mono mix.

  It also happens with real sound cards, not virtual ones.

  The question is about how to narrow down the issue. I think it's not
  ALSA related, because it happens both on the hardware device and the
  virtual loop one.

  Attached I put my chirp test sound.

  I played it on the command line with:

  $ ffplay -loop 1000 chirp_test.flac

  Then I setup the recording path with pavucontrol, to target the
  Audacity input

  My versions:

  pulseaudio 12.2-2
  linux kernel 5.6.13

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  pulseaudio:
Installed: 1:12.2-9~bionic1
Candidate: 1:12.2-9~bionic1
Version table:
   *** 1:12.2-9~bionic1 500
  500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu 
bionic/main amd64 Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7.8 500
  500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   1:11.1-1ubuntu7.7 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1:11.1-1ubuntu7 500
  500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Attached on this there is a .tar.gz containing both .flac files
  chirp_test.flac is the original file.
  chirp_loopback_recorded.flac is the recorded file from the loopback device.

  Thank You.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1882587/+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 1885675] Re: Apps crash with SIGSEGV in stream_state from ... from iris_blorp_exec from blorp_clear from clear_color from iris_clear

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
  Apps crash with SIGSEGV in stream_state from ... from iris_blorp_exec
  from blorp_clear from clear_color from iris_clear

Status in Mesa:
  New
Status in avogadro package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mpv package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1885675/+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 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  pulseaudio doesn't enforce sample rate set in daemon.conf

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Before submitting this bugreport I've went through the daemon.conf man page 
and the pulseaudio documentation, but have not found a solution to my problem.
  I've moved from Debian stable with
  pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with
  pulseaudio version 13.99.1-1ubuntu3.2.
  I'm experiencing cracking issues on external USB audio device Xonar U3 while 
listening to certain audio sources (system sounds included). This issue doesn't 
happen when using my laptop's internal audio device.
  Output of 'cat /proc/asound/card2/stream0' without audio stream running:
  C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, 
full  : USB Audio

  Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 200
Momentary freq = 44100 Hz (0x2c.199a)
Interface 1
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 1 OUT (ADAPTIVE)
Rates: 8000, 16000, 44100, 48000
Bits: 16

  Capture:
Status: Stop
Interface 2
Altset 1
Format: S16_LE
Channels: 2
Endpoint: 2 IN (ASYNC)
Rates: 8000, 16000, 44100, 48000
Bits: 16
  The following behaviour happens with default settings in 
/etc/pulse/daemon.conf:
  Xonar U3 plugged in, firefox running:
Momentary freq = 48000 Hz (0x30.)

  Xonar U3 plugged in, Clementine/Strawberry audio player running:
Momentary freq = 44100 Hz (0x2c.199a)

  Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz:
Momentary freq = 48000 Hz (0x30.)
  I've modified the daemon.conf as follows:
  ; default-sample-format = s16le #no change on this line, this is 
corresponding with the format the usb audio device suggests to be using
  ; default-sample-rate = 48000
  ; alternate-sample-rate = 48000
  However, when running video or audio sources with 44100Hz audio, applications 
 do not respect the default-sample-rate and Momentary freq reports 44100Hz, 
while other sources either send 48kHz by default or have no problem respecting 
the setting (I've tried the game Into the Breach, VLC running 48kHz video and 
audio files).
  Complete /etc/pulse/daemon.conf contents:
  https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73
  Checking syslog doesn't indicate any errors either, gist:
  https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370
  ==Workarounds attempted==

  Modifying /etc/pulse/default.pa to include:

  load-module module-udev-detect tsched=0
  Even after killing pulseaudio, this did not resolve anything. It 
also doesn't look like a good overall solution to the problem.

  Modifying daemon.conf to:

  ; resample-method = src-sinc-best-quality
  ; avoid-resampling = true
  Did not fix the issue.
  It is not possible to roll back PA to a previous version in Kubuntu 20.04 
without breaking dependencies of the Plasma desktop, so this was not attempted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  zelmor 1994 F pulseaudio
   /dev/snd/controlC1:  zelmor 1994 F pulseaudio
   /dev/snd/controlC0:  zelmor 1994 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 24 16:30:11 2020
  InstallationDate: Installed on 2020-04-28 (25 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S11H00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20B7S11H00
  dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2020-05-22T14:02:09.141811

To manage 

[Touch-packages] [Bug 1880198] Re: Ubuntu as bluetooth speaker - volume on bluetooth client ignored

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Ubuntu as bluetooth speaker - volume on bluetooth client ignored

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm using my 20.04 system as a media center. It's got a bluetooth
  adapter plugged into a USB port. I can connect to the system with my
  phone and ipad as an A2DP source and play music.

  The problem is that the volume on the source device is not respected

  When the volume on the source device goes to 0, the sound is muted as
  expected, but any other volume on the source device leads to the same
  volume on the Ubuntu server. The only way to adjust the volume is from
  the server.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kodi   1455 F pulseaudio
   /dev/snd/controlC0:  kodi   1455 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 22 16:42:57 2020
  InstallationDate: Installed on 2015-09-30 (1695 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2404
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1880198/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

Status in PulseAudio:
  Fix Released
Status in alsa-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  When you start playing some audio, the sound disappears.

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
Subsystem: ASUSTeK Computer Inc. M5A78L LE
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  
  uname -a
  Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  alsa-info

  
  !!
  !!ALSA Information Script v 0.4.65
  !!

  !!Script ran on: Fri Jun 19 13:38:12 UTC 2020

  
  !!Linux Distribution
  !!--

  Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
  20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
  20.04 LTS" HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-
  policies/privacy-policy" UBUNTU_CODENAME=focal

  
  !!DMI Information
  !!---

  Manufacturer:  System manufacturer
  Product Name:  System Product Name
  Product Version:   System Version
  Firmware Version:  1201   
  Board Vendor:  ASUSTeK Computer INC.
  Board Name:M5A78L-M LX/BR

  
  !!ACPI Device Status Information
  !!---

  /sys/bus/acpi/devices/ATK0110:00/status15
  /sys/bus/acpi/devices/PNP0103:00/status15
  /sys/bus/acpi/devices/PNP0400:00/status15
  /sys/bus/acpi/devices/PNP0501:00/status15
  /sys/bus/acpi/devices/PNP0C0C:00/status11
  /sys/bus/acpi/devices/PNP0C0F:00/status9
  /sys/bus/acpi/devices/PNP0C0F:01/status9
  /sys/bus/acpi/devices/PNP0C0F:02/status9
  /sys/bus/acpi/devices/PNP0C0F:03/status9
  /sys/bus/acpi/devices/PNP0C0F:04/status9
  /sys/bus/acpi/devices/PNP0C0F:05/status9
  /sys/bus/acpi/devices/PNP0C0F:06/status9
  /sys/bus/acpi/devices/PNP0C0F:07/status9
  /sys/bus/acpi/devices/device:20/status 15
  /sys/bus/acpi/devices/device:21/status 15

  
  !!Kernel Information
  !!--

  Kernel release:5.4.0-37-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes

  
  !!ALSA Version
  !!

  Driver version: k5.4.0-37-generic
  Library version:1.2.3
  Utilities version:  1.2.2

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe9f4000 irq 16

  
  !!PCI Soundcards installed in the system
  !!--

  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 
Azalia (Intel HDA) [1002:4383]
Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445]

  
  !!Modprobe options (Sound related)
  !!

  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_usb_audio: index=-2
  snd_usb_caiaq: index=-2
  snd_usb_ua101: index=-2
  snd_usb_us122l: index=-2
  snd_usb_usx2y: index=-2
  snd_cmipci: mpu_port=0x330 fm_port=0x388
  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_hda_intel: model=auto
  snd_hda_intel: dmic detect=0

  
  !!Loaded sound module options
  !!---

  !!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
dmic_detect : Y
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index : 

[Touch-packages] [Bug 1881284] Re: Pause the music after suspend

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  Pause the music after suspend

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Hi, I don't know how to describe it. What I basically need is pause
  the media/music automatically after I come back from suspend.

  Let's suppose we're suspending the laptop while playing the media
  (Spotify, youtube)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 18:09:52 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-04 (24 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1881284/+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 1886728] Re: OpenVPN OTP replaces the ordinary password

2022-05-20 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => New

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

Title:
  OpenVPN OTP replaces the ordinary password

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When OpenVPN has One-time password (OTP) enabled, and the user
  connects, a dialog asks the user to enter the One-time password (OTP)
  and press ok. This action replaces the ordinary "long term" password
  with the OTP. This causes annoyance as the next login will fail
  because the password is wrong and the user has to enter both the
  password and the OTP the next time they log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 01:07:18 2020
  InstallationDate: Installed on 2020-03-23 (106 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to focal on 2020-05-11 (57 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1886728/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

2022-05-20 Thread Bug Watch Updater
** Changed in: shared-mime-info
   Status: Unknown => Fix Released

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1893052] Re: Speaker and microphone mute LEDs should also relate to external audio devices

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Speaker and microphone mute LEDs should also relate to external audio
  devices

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  The F1 and F4 LEDs are not working when a USB-C headset is plugged in.  The 
LEDs work correctly for internal devices and when using the bantam jack.  This 
is on 20.04 LTS release.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  1699 F pulseaudio
   /dev/snd/controlC1:  z  1699 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-17 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 4810JP0100
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d8cb81d5-6bc2-454c-917f-0e9edde5f857 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET19W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4810JP0100
  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:bvrN2VET19W(1.04):bd07/10/2020:svnLENOVO:pn4810JP0100:pvrThinkPadP1Gen3:rvnLENOVO:rn4810JP0100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 3
  dmi.product.name: 4810JP0100
  dmi.product.sku: LENOVO_MT_4810_BU_Think_FM_ThinkPad P1 Gen 3
  dmi.product.version: ThinkPad P1 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1893052/+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 1892377] Re: Please add LDAC support in pulseaudio-module-bluetooth

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Please add LDAC support in pulseaudio-module-bluetooth

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  There is a project which enables these codecs in pulseaudio (by adding
  profiles for these): https://github.com/EHfive/pulseaudio-modules-bt

  For LDAC (codec) it uses libldac from the AOSP project:
  https://android.googlesource.com/platform/external/libldac

  There is a libldac dispatcher by the same author:
  https://github.com/EHfive/ldacBT

  It would be nice to have this functionality out-of-the-box in Ubuntu.
  This cannot be merged to PulseAudio upstream because the Android
  libldac library is under Apache License 2.0 which is incompatible with
  pulseaudio license LGPL 2.1:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36#note_160736

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1892377/+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 1900812] Re: pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd_h

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  pulseaudio crashed with SIGSEGV in
  pa_sink_move_streams_to_default_sink() from report_jack_state() from
  mixer_class_event() from hctl_elem_event_handler() from
  snd_hctl_elem_throw_event()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  * Impact

  There is a segfault issue started with the recent update

  * Test case

  We don't have specific steps to trigger the issue so test for regression and 
verify that reports stop on
  https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0

  * Regression potential

  The regression was created by a fix for gnome-control-center device
  selection issues, check that the settings still work correctly,
  allowing to change devices and showing the active one as selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1900812/+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 1904793] Re: upower abruptly thinks battery has gone to 1% and hibernates

2022-05-20 Thread Bug Watch Updater
** Changed in: upower
   Status: Unknown => Fix Released

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

Title:
  upower abruptly thinks battery has gone to 1% and hibernates

Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Triaged

Bug description:
  Whenever I go on battery after 20-30 minutes upower will very abruptly
  think my battery is at 1% and force my laptop to hibernate. This seems
  to happen at random times, I've seen it when my battery was reported
  to be 90%, 76%, 45%, 25%, etc. If I try to resume Ubuntu locks up
  forcing me to hard reset the machine. I suspect this is because upower
  thinks my battery is still at 1% when its not. My laptops firmware
  correctly reports the battery level and shows that I have plenty of
  power remaining. The last few times this happened I kept powertop up
  which shows that I do have plenty of power even when upower thinks I
  have none. Essentially this makes my laptop unusable on battery.

  Laptop: Lenovo X1 Carbon Extreme Gen 2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: upower 0.99.11-2
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Nov 18 13:59:24 2020
  InstallationDate: Installed on 2019-12-29 (325 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1904793/+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 1893563] Re: netplan: can't login to ap mode with psk

2022-05-20 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => Fix Released

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

Title:
  netplan: can't login to ap mode with psk

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  I've setup my wifi cards as ap over a bridge using netplan.
  If I add:

  auth:
key-management: psk
password: "testinglang"

  then my clients are unable to connect.
  If I remove those lines above in netplan then the clients are able to connect 
but without a password.

  If I run wpa_cli -i wlp3s0 status, I get:

  bssid=4c:1d:96:71:a3:90
  freq=2412
  ssid=walad2
  id=0
  mode=AP
  pairwise_cipher=CCMP+TKIP
  group_cipher=TKIP
  key_mgmt=UNKNOWN
  wpa_state=COMPLETED
  p2p_device_address=4c:1d:96:71:a3:91
  address=4c:1d:96:71:a3:90
  uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a

  I notice that key_mgmt=UNKNOWN. Perhaps that's the problem?

  Any pointers on how to debug and fix this?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: netplan.io 0.99-0ubuntu3~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Aug 30 23:11:48 2020
  InstallationDate: Installed on 2020-08-16 (14 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netplan.io
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1905078] Re: pavucontrol duplex profiles disappeared for SB Audigy after upgrading to Ubuntu 20.04

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  pavucontrol duplex profiles disappeared for SB Audigy after upgrading
  to Ubuntu 20.04

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Released

Bug description:
  I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile
  is gone. The duplex profile was there and was working properly before.

  The following seems to be related:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1905078/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Crackling audio on Raspberry Pi Desktop

Status in PulseAudio:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Attempting to play audio (e.g. from rhythmbox) on the raspberry pi
  desktop image, results in broken up / crackling audio. The "tsched=0"
  workaround noted in
  
https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling
  successfully avoids the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1899953/+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 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => Fix Released

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

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Fedora:
  Won't Fix

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1915870/+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 1916851] Re: module-echo-cancel fails on first run

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  module-echo-cancel fails on first run

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have the following in `.config/pulse/default.pa`:

  ```
  .include /etc/pulse/default.pa
  load-module module-echo-cancel aec_method=webrtc 
aec_args="analog_gain_control=0 digital_gain_control=1"
  ```

  After a reboot, there is no echo cancelled device.

  And then I run `systemctl --user restart pulseaudio` and the echo
  cancelled devices appear.

  That's a bit of a hassle.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shahar39906 F pulseaudio
   /dev/snd/controlC1:  shahar39906 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 16:05:48 2021
  InstallationDate: Installed on 2010-10-12 (3788 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago)
  dmi.bios.date: 10/24/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.1a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: X10SRA
  dmi.product.sku: Default string
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1916851/+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 1921766] Re: Output device not remembered after connecting/disconnecting another

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  Output device not remembered after connecting/disconnecting another

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for
  development work. I run it on a Lenovo X1 Carbon 8th Generation
  connected to dual monitors via a Lenovo dock. Both monitors are
  capable of outputting sound via HDMI.

  I use bluetooth headphones frequently with my Ubuntu 20.10 system, but
  I don't leave them on -- I turn them on and off as needed for Zoom
  calls. When I'm not on a call, however, I prefer to use my laptop's
  speakers for audio -- not my monitor speakers.

  Turning the bluetooth headphones on works fine, they connect and
  pulseaudio correctly identifies the new connection and switches to the
  headphones as the audio device.

  However, when I turn the headphones off, pulseaudio always selects an
  HDMI audio device as the sound device to use, not the internal speaker
  device that I was using prior to turning on the headphones. I must
  manually open Sound Settings and select the speaker device every time
  I turn my headphones off.

  My expectation is that the device I was using prior to connecting the
  headphones is remembered and switched back to by default after I
  disconnect my bluetooth headphones.

  I've tried using the pavucontrol app to disable the HDMI audio
  devices, but the hardware device disable settings are not granular
  enough to let me target the HDMI devices independently of the speaker
  device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1921766/+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 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

2022-05-20 Thread Bug Watch Updater
** Changed in: openvpn
   Status: Unknown => New

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

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in OpenVPN:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Invalid

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openvpn/+bug/1917887/+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 1930550] Re: usb sound devices crackling

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => New

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

Title:
  usb sound devices crackling

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, 
i have xduoo05plus, audeze mobius, audient id4.
  I also tried to modify 

  default-fragments = 5
  default-fragment-size-msec = 2

  to different sugested on stackoverflow articles setting

  Also this is in my config:
  high-priority = yes
  nice-level = -11

  realtime-scheduling = yes
  realtime-priority = 5

  
  I even tried to switch to pipewire, but it still the same. Possible issue in 
alsa kernel drivers for usb interface, submitting bug to pulse as it default in 
ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Jun  2 11:11:55 2021
  InstallationDate: Installed on 2019-08-13 (658 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago)
  dmi.bios.date: 08/12/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85-HD3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174
  mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1930550/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

2022-05-20 Thread Bug Watch Updater
** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  * Impact

  The pulseaudio service sometime segfaults on session closing which
  trigger a bug report dialog

  * Test plan

  Log out of a desktop session and back in, there should be no error
  prompt

  The issue isn't triggered only randomly it seems so it might be easier to 
check that reports stop on
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  * Where problems could occur

  The change is in the X session closing handling so shouldn't impact on
  normal use, if incorrect the fix could lead to increase the chance of
  hitting the segfault when an Xsession is closed

  
  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1955483] Re: dhcp4 (wlp1s0): could not get netmask from lease

2022-05-20 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => Fix Released

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

Title:
  dhcp4 (wlp1s0): could not get netmask from lease

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  New

Bug description:
  I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1
  (impish). It's been reported and fixed upstream. Any chance of getting
  an update to the impish package with the fix?

  Dec 21 06:23:54 t495 NetworkManager[989]:   [1640089434.9548] device 
(wlp1s0): supplicant interface state: associating -> 4way_handshake
  Dec 21 06:23:54 t495 NetworkManager[989]:   [1640089434.9548] device 
(p2p-dev-wlp1s0): supplicant management interface state: associating -> 
4way_handshake
  Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation 
completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP]
  Dec 21 06:23:54 t495 kernel: [  787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): 
wlp1s0: link becomes ready
  Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - 
Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=]
  Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-53 noise= txrate=1000
  Dec 21 06:23:54 t495 NetworkManager[989]:   [1640089434.9698] device 
(wlp1s0): supplicant interface state: 4way_handshake -> completed
  Dec 21 06:23:54 t495 NetworkManager[989]:   [1640089434.9698] device 
(wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. 
Connected to wireless network "VesperXB-Arawa"
  Dec 21 06:23:54 t495 NetworkManager[989]:   [1640089434.9699] device 
(p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> 
completed
  Dec 21 06:23:54 t495 NetworkManager[989]:   [1640089434.9703] device 
(wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'managed')
  Dec 21 06:23:54 t495 NetworkManager[989]:   [1640089434.9707] dhcp4 
(wlp1s0): activation: beginning transaction (timeout in 45 seconds)
  Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on 
interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893.
  Dec 21 06:23:54 t495 avahi-daemon[984]: New relevant interface wlp1s0.IPv6 
for mDNS.
  Dec 21 06:23:54 t495 avahi-daemon[984]: Registering new address record for 
fe80::86b7:7a02:8867:b893 on wlp1s0.*.
  Dec 21 06:23:55 t495 NetworkManager[989]:   [1640089435.0002] dhcp4 
(wlp1s0): could not get netmask from lease
  Dec 21 06:23:55 t495 NetworkManager[989]:   [1640089435.0003] dhcp4 
(wlp1s0): state changed unknown -> fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1955483/+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 1932155] Re: Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT)

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => Fix Released

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

Title:
  Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD
  GPUs (e.g. RX 5500 XT)

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets
  occur with various previous-generation AMD Radeon GPUs, for instance
  Radeon RX 5500 XT. There is a recent fix in the mesa library.

  Please see upstream mesa bug including available patch:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

  Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like
  it could apply to 21.0 (which is in focal-proposed) too, with minor
  effort.

  Thanks if you can backport this!

  amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145

  I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from
  focal-updates/focal-security

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1932155/+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 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => Fix Released

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

Title:
  [jammy regression] webkit apps do not display content (yelp, epiphany,
  gnome-online-accounts etc)

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Fix Released
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Invalid

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1943818] Re: mesa built with -O3 on ppc64el has broken EGL

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
  mesa built with -O3 on ppc64el has broken EGL

Status in Mesa:
  New
Status in The Ubuntu-power-systems project:
  New
Status in gcc-11 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  If mesa is built with -O3 then EGL will fail with:

  libEGL warning: DRI2: failed to create any config

  this can be easily reproduced by building libepoxy which then runs a
  series of tests.

  The same is fine on amd64, and also ppc64el is fine with gcc-10 and
  -O3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1943818/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2022-05-20 Thread Bug Watch Updater
** Changed in: dbus
   Status: Unknown => New

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  New
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Released
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  Fix Released
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 

[Touch-packages] [Bug 1919404] Re: Desktop icon shadows are broken at scale 200%

2022-05-20 Thread Bug Watch Updater
** Changed in: gnome-shell-extension-desktop-icons-ng
   Status: Unknown => Fix Released

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

Title:
  Desktop icon shadows are broken at scale 200%

Status in Gnome Shell Extension Desktop Icons Ng:
  Fix Released
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Desktop icon shadows are broken at scale 200%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+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 1971901] Re: dlltool uses non-unique temp filenames

2022-05-20 Thread Bug Watch Updater
Launchpad has imported 11 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=28885.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2022-02-12T15:27:37+00:00 Mikpelinux wrote:

With binutils-2.38 in a cross to x86_64-w64-mingw32 I persistently see
random breakage in dlltool during the build of mingw-w64's "crt".

Example 1:
...
x86_64-w64-mingw32-dlltool --as-flags=--64 -m i386:x86-64 -k 
--as=x86_64-w64-mingw32-as --output-lib lib64/libd3dcompiler_33.a  --input-def 
/tmp/mingw-w64-v9.0.0/mingw-w64-crt/lib64/d3dcompiler_33.def
x86_64-w64-mingw32-dlltool --as-flags=--64 -m i386:x86-64 -k 
--as=x86_64-w64-mingw32-as --output-lib lib64/libd3dcompiler_34.a  --input-def 
/tmp/mingw-w64-v9.0.0/mingw-w64-crt/lib64/d3dcompiler_34.def
x86_64-w64-mingw32-dlltool --as-flags=--64 -m i386:x86-64 -k 
--as=x86_64-w64-mingw32-as --output-lib lib64/libd3dcompiler_35.a  --input-def 
/tmp/mingw-w64-v9.0.0/mingw-w64-crt/lib64/d3dcompiler_35.def
x86_64-w64-mingw32-dlltool --as-flags=--64 -m i386:x86-64 -k 
--as=x86_64-w64-mingw32-as --output-lib lib64/libd3dcompiler_36.a  --input-def 
/tmp/mingw-w64-v9.0.0/mingw-w64-crt/lib64/d3dcompiler_36.def
Assembler messages:
Error: can't open D3DCompiler_dll_t.s for reading: No such file or directory
x86_64-w64-mingw32-dlltool --as-flags=--64 -m i386:x86-64 -k 
--as=x86_64-w64-mingw32-as --output-lib lib64/libd3dcompiler_37.a  --input-def 
/tmp/mingw-w64-v9.0.0/mingw-w64-crt/lib64/d3dcompiler_37.def
x86_64-w64-mingw32-dlltool: x86_64-w64-mingw32-as exited with status 1
x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
D3DCompiler_dll_t.o: No such file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s0.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s1.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s2.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s3.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s4.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s5.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s6.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s7.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s8.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s9.o: No such 
file or directory
make[1]: *** [Makefile:83854: lib64/libd3dcompiler_36.a] Error 1
make[1]: *** Waiting for unfinished jobs
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s0.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s1.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s2.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s3.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s4.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s5.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s6.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s7.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s8.o: No such 
file or directory
x86_64-w64-mingw32-dlltool: cannot delete D3DCompiler_dll_s9.o: No such 
file or directory

Example 2:
...
x86_64-w64-mingw32-dlltool --as-flags=--64 -m i386:x86-64 -k 
--as=x86_64-w64-mingw32-as --output-lib lib64/libd3dx9.a  --input-def 
/tmp/mingw-w64-v9.0.0/mingw-w64-crt/lib64/d3dx9_43.def
x86_64-w64-mingw32-dlltool --as-flags=--64 -m i386:x86-64 -k 
--as=x86_64-w64-mingw32-as --output-lib lib64/libd3dx10.a  --input-def 
/tmp/mingw-w64-v9.0.0/mingw-w64-crt/lib64/d3dx10_43.def
x86_64-w64-mingw32-dlltool: lib32/libd3dx9.a: error reading d3dx9_43_dll_h.o: 
file truncated
make[1]: *** [Makefile:83819: lib32/libd3dx9.a] Error 1
make[1]: *** Waiting for unfinished jobs
x86_64-w64-mingw32-dlltool: lib64/libd3dx9.a: error reading d3dx9_43_dll_t.o: 
No such file or directory

I've also seen it produce .a files that ar complained about containing
invalid or truncated files.

These random failures occur persistently when using binutils-2.38 and
parallel make (make -jN) for mingw-w64's crt. The failures disappear if
I use non-parallel make, or revert to binutils-2.37.

A git bisect identified this late change in 2.38 development as the
cause:

# first bad 

[Touch-packages] [Bug 1964274] Re: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool

2022-05-20 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Unknown => Fix Released

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

Title:
  Xwayland crashes with wl_display@1: error 1: invalid arguments for
  wl_shm@6.create_pool

Status in X.Org X server:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in wayland package in Ubuntu:
  Fix Committed
Status in xwayland package in Ubuntu:
  Fix Released

Bug description:
  System :
  Ubuntu 21.10
  Kernel 5.13.0-35
  Session : Wayland

  Each time I try to rip a CD with "abcde" gnome-shell crashes
  What I understand from the logs :
  Before the CD is ripped, abcde downloads a picture (from internet) as a cover 
of the CD.
  When tracker-extract discovers this picture something bad happens.
  Then gnome-shell crashes.
  After the crash (and re-login into Ubuntu) I can resume the ripping process 
as the picture has been cached by abcde, and tracker-extract does not interact 
again with it.
  Obviously the problem is back for each new CD.

  The problem appeared quite recently, probably less than 1 month ago.

  Logs :
   00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Activating via 
systemd: service name='org.freedesktop.Tracker3.Miner.Extract' 
unit='tracker-extract-3.service' requested by ':1.8' (uid=1000 pid=3573 
comm="/usr/libexec/tracker-mi>
   00:13:06 host systemd[3523]: Starting Tracker metadata extractor...
   00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Successfully 
activated service 'org.freedesktop.Tracker3.Miner.Extract'
   00:13:06 host systemd[3523]: Started Tracker metadata extractor.
   00:13:14 host tracker-extract-3[11545]: Not a JPEG file: starts with 0x89 
0x50
   00:13:14 host tracker-extract[11545]: Task for 
'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' finished with error: 
Could not get any metadata for 
uri:'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' and mime:'image/jpeg'
   00:13:14 host gnome-shell[3640]: WL: file descriptor expected, object (6), 
message create_pool(nhi)
   00:13:14 host gnome-shell[3640]: WL: error in client communication (pid 3640)
   00:13:14 host gnome-shell[4456]: (EE)
   00:13:14 host gnome-shell[4456]: Fatal server error:
   00:13:14 host gnome-shell[4456]: (EE) wl_display@1: error 1: invalid 
arguments for wl_shm@6.create_pool
   00:13:14 host gnome-shell[4456]: (EE)
   00:13:14 host gnome-shell[3640]: Connection to xwayland lost

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1964274/+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 1966613] Re: Navigating with arrow keys broken for RTL text

2022-05-20 Thread Bug Watch Updater
** Changed in: pango
   Status: Unknown => Fix Released

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

Title:
  Navigating with arrow keys broken for RTL text

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Fix Released

Bug description:
  RTL text renders fine, and navigating within a line with the arrow
  keys works as expected. However, using the left and right arrow keys
  to move to the next or previous lines is broken.

  To reproduce:
  1. Open gnome-text-editor and paste the following into its window:
  זוהי השורה הראשונה
  זוהי השורה השנייה
  זוהי השורה השלישית
  make sure it is aligned to the right, as it should.
  2. place the caret in the middle of the 2nd line.
  3. With the arrows, move the caret to the left of the line (its end).
  4. Press the left arrow key one more time.
  Expected results:
  1. The caret moves to the right hand side of the next line.
  Actual results:
  1. The caret moves to the left hand side of the previous line.

  The same issue exists in reverse: if you move the caret with the arrow
  keys to the right of the line (its beginning) and press the right
  arrow key one more time, it will move to the right hand side of the
  next line instead of the left hand side of the previous line, as it
  should.

  This make navigation in RTL files highly uncomfortable.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-text-editor 42.0-2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 03:09:24 2022
  InstallationDate: Installed on 2022-01-31 (55 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pango/+bug/1966613/+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 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%

2022-05-20 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  All the windows and the desktop icons disappear constantly after
  setting Scaling to 300%

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Summary
  ===

  Device with nvidia GPU, using proprietary drivers, wayland activated
  by default.

  By default, the scaling is set to 200% (the screen is UHD). If
  selecting 300%, all the windows close down, as well as the desktop
  icons (Home) as long as the mouse cursor is in the way.

  To fix the issue, one has to open the Display Settings (while making
  sure the mouse cursor is never above any of the Settings windows!),
  then set Scaling back to 200% using the keyboard.

  This problem does not happen in X11, and does not happen in Wayland if
  I select 100%, 200% or even 400% scaling!

  Steps to reproduce
  ==

  - Install 22.04 beta, selecting "install third party software" to make sure 
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
  - After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE 
should return `wayland`)
  - Go to Settings > Display, select 300% scaling, then press Apply

  Expected result
  ===

  The scaling is set to 300% and user can keep using the device.

  Actual result
  =

  The scaling is set to 300% and all the windows are shut down. If user
  tries to reopen a window (e.g. Terminal), it is shut down immediately
  if the mouse cursor is hovering it. The desktop icons keep
  disappearing and reappearing for as long as the mouse cursor is
  hovering the background.

  The only way to stop this is to go back to Settings > Display, and,
  using the keyboard, set the scaling back to 200%.

  Information
  ===

  Version:  Ubuntu Jammy Jellyfish (development branch) [Beta image]
  Release:  22.04

  Device: Dell Precision 7760 with Nvidia GPU
  CID: 202103-28858

  Third party software installed during installation

  Wayland in use.

  ii  linux-generic-hwe-20.045.15.0.23.25   
 amd64Complete Generic Linux kernel and headers
  ii  linux-headers-5.15.0-235.15.0-23.23   
 all  Header files related to Linux kernel version 5.15.0
  ii  linux-headers-5.15.0-23-generic5.15.0-23.23   
 amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
  ii  linux-headers-generic-hwe-20.045.15.0.23.25   
 amd64Generic Linux kernel headers
  ii  linux-image-5.15.0-23-generic  5.15.0-23.23   
 amd64Signed kernel image generic
  ii  linux-image-generic-hwe-20.04  5.15.0.23.25   
 amd64Generic Linux kernel image
  ii  linux-modules-5.15.0-23-generic5.15.0-23.23   
 amd64Linux kernel extra modules for version 5.15.0 on 64 bit 
x86 SMP
  ii  linux-modules-extra-5.15.0-23-generic  5.15.0-23.23   
 amd64Linux kernel extra modules for version 5.15.0 on 64 bit 
x86 SMP
  ii  linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 
 amd64Linux kernel nvidia modules for version 5.15.0-23
  ii  linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 
 amd64Extra drivers for nvidia-510 for the generic-hwe-20.04 
flavour
  ii  linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 
 amd64Linux kernel nvidia modules for version 5.15.0-23 
(objects)
  ii  linux-signatures-nvidia-5.15.0-23-generic  5.15.0-23.23+1 
 amd64Linux kernel signatures for nvidia modules for version 
5.15.0-23-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  1 10:24:25 2022
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 

[Touch-packages] [Bug 1967565] Re: upower takes long time to detect laptop AC charger plugged in

2022-05-20 Thread Bug Watch Updater
** Changed in: upower
   Status: Unknown => Fix Released

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

Title:
  upower takes long time to detect laptop AC charger plugged in

Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Triaged

Bug description:
  upower takes a really long time (around 1-2 minutes) to detect when an AC 
charger is plugged-in.
  'upower -d' shows battery state as discharging after AC charger is plugged-in.
  'systemctl restart upower.service' would update the status immediately as 
charging. Otherwise, it takes 1-2 minutes before upower updates the status.

  Laptop Model: Acer Aspire E15 E5-573G-56JN

  Laptop battery and AC charger is not faulty as the
  charging/discharging status gets correctly detected when using Windows
  10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: upower 0.99.11-1build2
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  1 23:07:12 2022
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1967565/+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 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-05-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in Mesa:
  New
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1966221/+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 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice

2022-05-20 Thread Bug Watch Updater
** Changed in: accountsservice
   Status: Unknown => New

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

Title:
  Valgrind memory errors in gnome-shell 42 from accountsservice

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

Bug description:
  Valgrind memory errors in gnome-shell 42 from accountsservice:

  ==60511== Invalid read of size 8
  ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120)
  ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417)
  ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557)
  ==60511==by 0x1E428ECA: _act_user_update_from_object_path 
(act-user.c:1346)
  ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==  Block was alloc'd at
  ==60511==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4DA5718: g_malloc (gmem.c:125)
  ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072)
  ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098)
  ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911)
  ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011)
  ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181)
  ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821)
  ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706)
  ==60511==by 0x1E429BD8: act_user_manager_get_user 
(act-user-manager.c:1879)
  ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0)
  ==60511== 
  ==60511== Invalid read of size 8
  ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a 
(gtype.c:4091)
  ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982)
  ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708)
  ==60511==by 0x1E4298E7: on_find_user_by_name_finished 
(act-user-manager.c:1187)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300)
  ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256)
  ==60511==by 0x4C2107E: g_dbus_connection_call_done 
(gdbusconnection.c:5895)
  ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230)
  ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244)
  ==60511==  Address 0x185b5110 is 0 bytes inside a block of size 64 free'd
  ==60511==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
  ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562)
  ==60511==by 0x1E428ECA: UnknownInlinedFun 

[Touch-packages] [Bug 1974223] Re: FTBFS since changes in apt for automatic kernel removal

2022-05-19 Thread Bug Watch Updater
** Changed in: unattended-upgrades (Debian)
   Status: Unknown => Fix Released

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

Title:
  FTBFS since changes in apt for automatic kernel removal

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  Since the following changes in apt have landed in focal-updates and
  bionic-updates, unattended-upgrades FTBFS on both series:

* Revert "Protect currently running kernel at run-time"
* Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  
  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1973760] Re: Crash when using DIGEST-MD5 with SSF>=128

2022-05-18 Thread Bug Watch Updater
** Changed in: cyrus-sasl2 (Debian)
   Status: Unknown => New

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

Title:
  Crash when using DIGEST-MD5 with SSF>=128

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 package in Debian:
  New

Bug description:
  I'm still troubleshooting this, but at the moment apps negotiating a
  DIGEST-MD5 authentication and requesting some form of transport
  encryption (ssf != 0) are crashing. The only example I have so far is
  the openldap client tools (so just one app really).

  ssf=0 works:
  $ ldapwhoami  -U ubuntu@lxd -w ubuntusecret -O maxssf=0
  SASL/DIGEST-MD5 authentication started
  SASL username: ubuntu@lxd
  SASL SSF: 0
  dn:uid=ubuntu@lxd,cn=vms,cn=digest-md5,cn=auth

  
  ssf=128 crashes:
  $ ldapwhoami  -U ubuntu@lxd -w ubuntusecret -O maxssf=128
  SASL/DIGEST-MD5 authentication started
  SASL username: ubuntu@lxd
  SASL SSF: 128
  SASL data security layer installed.
  Segmentation fault (core dumped)

  The crash seems to be inside openssl. I'll get a proper stack trace.

  2.1.27, also built with openssl3, does not crash. So far only 2.1.28
  (in kinetic-proposed).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1973760/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

2022-05-18 Thread Bug Watch Updater
** Changed in: wpa (Debian)
   Status: Unknown => New

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Triaged
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1958267/+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 1974037] Re: openssl: EVP_EC_gen() segfault without init

2022-05-18 Thread Bug Watch Updater
** Changed in: openssl (Debian)
   Status: New => Fix Released

** Changed in: openssl (Debian)
   Importance: Undecided => Unknown

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

Title:
  openssl: EVP_EC_gen() segfault without init

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed
Status in openssl source package in Kinetic:
  Confirmed
Status in openssl package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1010958:

  Source: sscg
  Version: 3.0.2-1
  Severity: serious
  Tags: ftbfs

  https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1

  ...
   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal 11 
SIGSEGV
  04:32:21 MALLOC_PERTURB_=87 
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
  ...

  Summary of Failures:

   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal
  11 SIGSEGV

  Ok: 9
  Expected Fail:  0
  Fail:   1
  Unexpected Pass:0
  Skipped:0
  Timeout:0
  dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=4 ninja test returned exit code 1
  make: *** [debian/rules:6: binary-arch] Error 25

  This has also been reported on the openssl-users mailing list:

  https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

2022-05-14 Thread Bug Watch Updater
** Changed in: gdb
   Status: Incomplete => Fix Released

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Fix Released
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Released
Status in glibc source package in Focal:
  Fix Released
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning

2022-05-13 Thread Bug Watch Updater
** Changed in: firefox
   Status: Unknown => Confirmed

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

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

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

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

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


-- 
Mailing list: https://launchpad.net/~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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

2022-05-12 Thread Bug Watch Updater
** Changed in: openssl (Debian)
   Status: Unknown => Fix Released

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

Title:
  [openssl3] please sync openssl.cnf to ease changing security level

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl package in Debian:
  Fix Released

Bug description:
  openssl.cnf as provided misses some directive, which make it a bit
  difficult to change security level, which since openssl 3 disables
  SHA1 signatures.

  See also this Debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1010360 and the committed fix:
  
https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4

  Can you please sync this change in Ubuntu openssl?

  This way one should just add a single directive to change the security
  level.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

2022-05-10 Thread Bug Watch Updater
** Changed in: kbd-chooser
   Status: New => Fix Released

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  Fix Released
Status in console-setup package in Ubuntu:
  New
Status in kbd package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press `` key, enter some letters in CAPITALS (while CapsLock 
LED is on)
  5. Press `` key again, enter some letters in lowercase (while 
CapsLock LED is off)

  Expected results:
  * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock 
key function

  Actual results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

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


  1   2   3   4   5   6   7   8   9   10   >