[Touch-packages] [Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"

[Dmitry-a-durnev]

Actually it's more simple than that, initramfs(step 6) is not required. After 
each kernel upgrade (during apt dist/full upgrade) I face the "invalid 
argument" error and each time I fix it only by steps
 
1, 2, 5, 7, 8, 9.

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

Title:
  systemctl hibernate error: "Call to Hibernate failed: Invalid
  argument"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped
  working.

  Trying to hibernate:
  systemctl hibernate

  I get:
  Call to Hibernate failed: Invalid argument

  systemctl status systemd-hibernate.service

  -
  × systemd-hibernate.service - Hibernate
   Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; 
static)
   Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 
1min 33s ago
 Docs: man:systemd-hibernate.service(8)
  Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate 
(code=exited, status=1/FAILURE)
 Main PID: 4473 (code=exited, status=1/FAILURE)
  CPU: 5ms

  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting 
systemd-hibernate.service - Hibernate...
  мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location 
to hibernate to: Invalid argument
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main 
process exited, code=exited, status=1/FAILURE
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed 
with result 'exit-code'.
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start 
systemd-hibernate.service - Hibernate.
  --

  Previous version (254.x) worked: swapfile(on EXT4 fs) is used to
  hibernate/resume, resume with resume_offset kernel parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+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 2063332] Re: Multiple problems Ubuntu 24.04 with Qt5

[Dmitry Shachnev]

What you describe sounds like an effect of switching from X11 to
Wayland, not a regression in Qt.

In X11, the window decorations can be drawn either by the window manager
or by the application itself. Qt relied on window manager, so the
decorations looked uniform.

In Wayland, there is no choice, and Qt draws its own window decorations,
which may be different from GNOME ones. If you signed into a Wayland
session in Ubuntu 22.04, you would likely get the same effect.

There is a third-party package which may make things better for Qt
applications in GNOME: qgnomeplatform-qt5. After installing it, try
running your application with QT_QPA_PLATFORMTHEME=gnome environment
variable.

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

Title:
  Multiple problems Ubuntu 24.04 with Qt5

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  After the upgrade to the 24.04 beta Qt5 UI is not at its best. Please,
  notice that all this functionality is working on 22.04.

  1. Windows controls settings from Gnome are not applied
  When you set the Windows Title bar buttons to Placement Left, then Qt apps 
ignore this setting. The default gt4 apps behave properly and place the buttons 
to the left.

  2. Windows actions like double click to maximize from settings also do
  not with in the Qt5 apps unlike in gt4 apps.

  3. Several keyboard shortcuts are passed differently to Qt5 apps.
  The key "Ctrl+Period" is not passed to the qt app at all
  The key "Ctrl+~" is passed as "Ctrl+0"
  The key "Shift+Alt+F7" is also not working
  This means some different handling is applied in Qt5 apps

  4. If you use the env var "export QT_QPA_PLATFORM=xcb" and start the
  Qt5 app, then it all works properly. The windows controls are on the
  right side, you can use double click the title bar to maximize and
  also the shortcuts are working fine. However, in such scenario no app
  starts fullscreen. It starts in a positioned window (the position is
  remembered) instead even if you maximized the window before you exited
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libqt5core5t64 5.15.13+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 14:20:24 2024
  InstallationDate: Installed on 2020-05-12 (1443 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to noble on 2024-04-20 (4 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-04-19T01:50:32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2063332/+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 2060102] Re: apt dist-upgrade uninstalls quassel-client

[Dmitry Shachnev]

Hi Heinrich!

The noble archive for amd64 is currently in a semi-broken state. As an
attempt to mitigate the consequences of CVE-2024-3094, all amd64
binaries built with compromised xz-utils were removed from the archive,
which rendered some packages uninstallable.

If you want a stable archive, try using noble-updates only (without the
release pocket). It contains an older, pre-CVE-2024-3094 snapshot. Or
wait until things settle down and packages become installable in noble
again.

Also, installing the packages using "dpkg -i" may break your system, as
that command does not check the dependencies. Use "apt install ./*.deb"
instead, which is safer.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094

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

Title:
  apt dist-upgrade uninstalls quassel-client

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in quassel package in Ubuntu:
  New

Bug description:
  Trying to run dist-upgrade asks for uninstalling quassel-client on
  amd64. This is related to some unfullfillable dependencies:

  The following packages have unmet dependencies:
   quassel-client : Depends: libqt5core5t64 (>= 5.15.1) but it is not 
installable
Depends: libqt5dbus5t64 (>= 5.14.1) but it is not 
installable
Depends: libqt5gui5t64 (>= 5.14.1) but it is not 
installable or
 libqt5gui5-gles (>= 5.14.1) but it is not installed
Depends: libqt5network5t64 (>= 5.15.1) but it is not 
installable
Depends: libqt5widgets5t64 (>= 5.14.1) but it is not 
installable

  $ sudo apt-get dist-upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
quassel-client
  The following packages have been kept back:
2to3 alsa-ucm-conf apache2-data breeze-cursor-theme debconf-kde-data exim4 
gnupg gnupg-agent gvfs-common hplip-data hplip-gui kde-cli-tools-data 
khotkeys-data kio-extras-data
ktexteditor-data kubuntu-desktop kwayland-data kwin-data 
libavahi-client3:i386 libavahi-common-data:i386 libavahi-common3:i386 
libblkid1:i386 libcairo-gobject2:i386
libcairo2:i386 libcanberra-gtk-module:i386 libcanberra-gtk0:i386 
libcom-err2:i386 libdbus-1-3:i386 libfreetype6:i386 libgail-common:i386 
libgdk-pixbuf-2.0-0:i386
libgl1-mesa-dri:i386 libglapi-mesa:i386 libglx-mesa0:i386 
libgssapi-krb5-2:i386 libharfbuzz0b:i386 libk5crypto3:i386 libkf5bluezqt-data 
libkf5contacts-data
libkf5declarative-data libkf5dnssd-data libkf5filemetadata-data 
libkf5holidays-data libkf5kcmutils-data libkf5kdelibs4support-data 
libkf5khtml-data libkf5notifyconfig-data
libkf5package-data libkf5parts-data libkf5people-data libkf5pty-data 
libkf5sane-data libkf5screen-bin libkf5screen-data libkf5screen8 
libkf5screendpms8 libkf5sonnet5-data
libkf5su-data libkf5syntaxhighlighting-data libkf5sysguard-bin 
libkf5sysguard-data libkimageannotator-common libkpim5gapi-data libkrb5-3:i386 
libkrb5support0:i386 libksgrd9
libksysguardformatter1 libksysguardsensorfaces1 libksysguardsensors1 
libksysguardsystemstats1 libmount1:i386 libnsl2:i386 libnss-nisplus:i386 
libnvidia-compute-535:i386
libnvidia-decode-535:i386 libnvidia-encode-535:i386 libnvidia-fbc1-535:i386 
libnvidia-gl-535:i386 libpango-1.0-0:i386 libpangocairo-1.0-0:i386 
libpangoft2-1.0-0:i386
libprocesscore9 libprocessui9 libqt6webengine6-data librsvg2-2:i386 
librsvg2-common:i386 libsane-common libselinux1 libselinux1:i386 
libselinux1-dev libsharpyuv0:i386
libsystemd0:i386 libuuid1:i386 libvirt-daemon-config-network 
libvirt-daemon-config-nwfilter libvirt-daemon-system-systemd libvirt-l10n 
libvolume-key1 libwebp7:i386
libzvbi-common mesa-vulkan-drivers:i386 plasma-desktop-data 
plasma-discover-common powerdevil-data python3-magic 
qml-module-org-kde-ksysguard samba-common
ubuntu-advantage-tools vim vim-common vim-runtime vim-tiny zlib1g:i386
  The following packages will be upgraded:
quassel-data
  1 upgraded, 0 newly installed, 1 to remove and 113 not upgraded.
  Need to get 0 B/866 kB of archives.
  After this operation, 4.382 kB disk space will be freed.
  Do you want to continue? [Y/n]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2060102/+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 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"

[Dmitry-a-durnev]

Somehow this was fixed for me by the following (almost random) sequence
of steps:

1. remove resume/resume_offset kernel parameters from /etc/default/grub
2. update-grub, reboot: hibernate options appear in ubuntu shutdown menu
3. hibernate: works, no more "invalid argument" error.
4. resume(power on): not works - just regular power on. Tried several times.
5. return resume/resume_offset kernel parameters back to /etc/default/grub. 
6. initramfs -c -k all : maybe this fixed it? (should not be necessary to do)
7. update-grub
8. hibernate
9. resume: works (!)

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

Title:
  systemctl hibernate error: "Call to Hibernate failed: Invalid
  argument"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped
  working.

  Trying to hibernate:
  systemctl hibernate

  I get:
  Call to Hibernate failed: Invalid argument

  systemctl status systemd-hibernate.service

  -
  × systemd-hibernate.service - Hibernate
   Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; 
static)
   Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 
1min 33s ago
 Docs: man:systemd-hibernate.service(8)
  Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate 
(code=exited, status=1/FAILURE)
 Main PID: 4473 (code=exited, status=1/FAILURE)
  CPU: 5ms

  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting 
systemd-hibernate.service - Hibernate...
  мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location 
to hibernate to: Invalid argument
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main 
process exited, code=exited, status=1/FAILURE
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed 
with result 'exit-code'.
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start 
systemd-hibernate.service - Hibernate.
  --

  Previous version (254.x) worked: swapfile(on EXT4 fs) is used to
  hibernate/resume, resume with resume_offset kernel parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+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 2057687] [NEW] systemctl hibernate error: "Call to Hibernate failed: Invalid argument"

[Dmitry-a-durnev]

Public bug reported:

After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped
working.

Trying to hibernate:
systemctl hibernate

I get:
Call to Hibernate failed: Invalid argument

systemctl status systemd-hibernate.service

-
× systemd-hibernate.service - Hibernate
 Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static)
 Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 
33s ago
   Docs: man:systemd-hibernate.service(8)
Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate 
(code=exited, status=1/FAILURE)
   Main PID: 4473 (code=exited, status=1/FAILURE)
CPU: 5ms

мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service 
- Hibernate...
мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to 
hibernate to: Invalid argument
мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main 
process exited, code=exited, status=1/FAILURE
мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed 
with result 'exit-code'.
мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start 
systemd-hibernate.service - Hibernate.
--

Previous version (254.x) worked: swapfile(on EXT4 fs) is used to
hibernate/resume, resume with resume_offset kernel parameters.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: 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/2057687

Title:
  systemctl hibernate error: "Call to Hibernate failed: Invalid
  argument"

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped
  working.

  Trying to hibernate:
  systemctl hibernate

  I get:
  Call to Hibernate failed: Invalid argument

  systemctl status systemd-hibernate.service

  -
  × systemd-hibernate.service - Hibernate
   Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; 
static)
   Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 
1min 33s ago
 Docs: man:systemd-hibernate.service(8)
  Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate 
(code=exited, status=1/FAILURE)
 Main PID: 4473 (code=exited, status=1/FAILURE)
  CPU: 5ms

  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting 
systemd-hibernate.service - Hibernate...
  мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location 
to hibernate to: Invalid argument
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main 
process exited, code=exited, status=1/FAILURE
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed 
with result 'exit-code'.
  мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start 
systemd-hibernate.service - Hibernate.
  --

  Previous version (254.x) worked: swapfile(on EXT4 fs) is used to
  hibernate/resume, resume with resume_offset kernel parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[Dmitry]

Same problem Razer Blade 16 2023

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

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

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 1926802] Re: qt5-default package is missed in 21.04

[Dmitry Shachnev]

What is the point of installing runtime libraries by hand?

The idea is that you install some application that you want to use, and
it pulls the library packages as dependencies.

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

Title:
  qt5-default package is missed in 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in Unity Linux:
  New

Bug description:
  Previous 20.10 version has the qt5-default package in place (see
  https://packages.ubuntu.com/groovy/qt5-default ).

  Please upload the  qt5-default package for 21.04 Ubuntu version.

  What is interesting - all its dependencies can be simply installed
  with `sudo apt-get install qtbase5-dev qtchooser qt5-qmake
  qtbase5-dev-tools` .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04

[Dmitry Shachnev]

Okay, I can try patching out the QT_NO_ANIMATION line in our packaging.

** No longer affects: qtbase-opensource-src (Ubuntu)

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

Title:
  Indeterminate Qt progress bars don't display properly in 20.04

Status in qtstyleplugins-src package in Ubuntu:
  New

Bug description:
  In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar
  (meaning its minimum and maximum values have both been set to zero)
  does not display properly. It is supposed to animate in a way that
  shows that something is happening with an unknown time remaining.
  Instead, it sits still with its progress bar showing approximately 25
  to 30% progress.

  To test this, make a simple Qt program with a QProgressBar in the main
  window, and add these lines to the constructor of the main window:

  ui->progressBar->setMinimum(0);
  ui->progressBar->setMaximum(0);

  This problem is not present in standard Ubuntu 20.04. Standard Ubuntu
  correctly animates the indeterminate progress bar. It's unclear to me
  which package is at fault, but it seems to be something specific to
  Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem.

  Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it
  doesn't have this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1906138/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04

[Dmitry Shachnev]

I don't remember why I disabled animation in that commit. Probably I had
some build failure when it's enabled.

Anyway, qtstyleplugins is abandoned and no longer developed (the last
commit was more than 6 years ago). I recommend to NOT include it in
dependencies of any package.

Qt 6.5.0 will have a much improved GTK 3 integration support:
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=4ca8a6840842d5ff.

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

Title:
  Indeterminate Qt progress bars don't display properly in 20.04

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtstyleplugins-src package in Ubuntu:
  New

Bug description:
  In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar
  (meaning its minimum and maximum values have both been set to zero)
  does not display properly. It is supposed to animate in a way that
  shows that something is happening with an unknown time remaining.
  Instead, it sits still with its progress bar showing approximately 25
  to 30% progress.

  To test this, make a simple Qt program with a QProgressBar in the main
  window, and add these lines to the constructor of the main window:

  ui->progressBar->setMinimum(0);
  ui->progressBar->setMaximum(0);

  This problem is not present in standard Ubuntu 20.04. Standard Ubuntu
  correctly animates the indeterminate progress bar. It's unclear to me
  which package is at fault, but it seems to be something specific to
  Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem.

  Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it
  doesn't have this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+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 2016703] Re: qbusmacros.h fails to compile: wrong case on case-sensitive include

[Dmitry Shachnev]

This bug is still present in Qt 6. Submitted a fix upstream:
https://codereview.qt-project.org/c/qt/qtbase/+/472832.

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

Title:
  qbusmacros.h fails to compile: wrong case on case-sensitive include

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  /usr/include/arm-linux-gnueabihf/qt5/QtDBus/qdbusmacros.h in
  qtbase5-dev cannot compile:

  /usr/include/arm-linux-gnueabihf/qt5/QtDBus/qdbusmacros.h:8:10: fatal error: 
QtDbus/qtdbusglobal.h: No such file or directory
  8 | #include 
|  ^~~
  compilation terminated.

  
  The correct filename is , not .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2016703/+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 2013095] Re: sphinx autopkgtest needs to be updated for webkit 2.40

[Dmitry Shachnev]

I will fix it via Debian.

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

Title:
  sphinx autopkgtest needs to be updated for webkit 2.40

Status in pygobject package in Ubuntu:
  New
Status in sphinx package in Ubuntu:
  Triaged
Status in texlive-extra package in Ubuntu:
  New

Bug description:
  The sphinx autopkgtest needs to be updated for webkitgtk 2.40 which
  made breaking changes to the gtk4 library (webkit2-5.0 -> webkit-6.0).

  Our usual auto-transition tools didn't detect the autopkgtest-only
  dependency.

  https://github.com/WebKit/WebKit/blob/main/Source/WebKit/gtk/migrating-
  to-webkitgtk-6.0.md

  I am adding some other affected packages for our excuses tracker page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2013095/+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 2013083] [NEW] libwebp-dev doesn't install CMake configs

[Dmitry]

Public bug reported:

Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu
package doesn't install them. This prevents client applications from
using the recommended find_package(WebP) functionality.

Please install the CMake configs along with the pkg-config files.

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

** Summary changed:

- libwebp-dev doesn't install CMake rules
+ libwebp-dev doesn't install CMake configs

** Description changed:

  Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu
  package doesn't install them. This prevents client applications from
  using the recommended find_package(WebP) functionality.
  
- Please install CMake configs along with pkg-config files.
+ Please install the CMake configs along with the pkg-config files.

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

Title:
  libwebp-dev doesn't install CMake configs

Status in libwebp package in Ubuntu:
  New

Bug description:
  Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu
  package doesn't install them. This prevents client applications from
  using the recommended find_package(WebP) functionality.

  Please install the CMake configs along with the pkg-config files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2013083/+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 1999220] Re: libQt5Core.so.5 incompatible with older kernels (<3.15)

[Dmitry Shachnev]

Ubuntu 22.04 (jammy), the current LTS release, has kernel 5.15.
Ubuntu 20.04 (focal), the previous LTS release, has kernel 5.4.
Ubuntu 18.04 (bionic) has kernel 4.15.
Ubuntu 16.04 (xenial) has kernel 4.4.

The version of libQt5Core.so.5 in jammy requires kernel 3.17. This
kernel is present in all mentioned releases. I think it's a reasonable
requirement, we cannot support ancient kernels forever.

This requirement is needed for getrandom feature.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Won't Fix

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

Title:
   libQt5Core.so.5 incompatible with older kernels (<3.15)

Status in qtbase-opensource-src package in Ubuntu:
  Won't Fix

Bug description:
  When running programs that use  libQt5Core.so.5 on pre-3.15 kernels (e.g. 
from a container)
  one gets

  error while loading shared libraries: libQt5Core.so.5: cannot open
  shared object file: No such file or directory

  A workaround (from https://github.com/dnschneid/crouton/wiki/Fix-
  error-while-loading-shared-libraries:-libQt5Core.so.5):

  sudo strip --remove-section=.note.ABI-tag /usr/lib64/libQt5Core.so.5

  At least 20.04 and 22.04 are affected.
  I guess, something can be changed in the way the library compiles to make it 
more portable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1999220/+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 1986936] Re: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages

[Dmitry Shachnev]

> what package the link libQt5Core.so is supposed to be a part of

qtbase5-dev

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the
  corresponding :i386 packages

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  While trying to link against corresponding libraries to get i386 executable 
like that:
  > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ...

  I get the following errors:

  > /usr/bin/ld: skipping incompatible 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets  

   
  > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory

  
  > /usr/bin/ld: skipping incompatible 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets  

   
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so 
when searching for -lQt5Gui 

  > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory

  
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so 
when searching for -lQt5Gui 

  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so 
when searching for -lQt5Core
   
  > /usr/bin/ld: cannot find -lQt5Core: No such file or directory   

  
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so 
when searching for -lQt5Core 

  despite corresponging packages are installed (libqt5gui5:i386 and same
  for widgets and core).

  Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no
  symlinks named exactly libQt5Core.so (and same for two other libs).

  Adding those symlinks by hand completely solves the problem.

  I believe however that those symlinks must be installed by
  corresponding .debs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1986936/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Marking as verified per comment #23. I also restarted the failed
autopkgtest.

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
  less secure protocols.

  [Test Plan]

  1. Create test.cpp with the following contents:

  #include 
  #include 
  #include 
  #include 

  int main(int argc, char **argv) {
  QCoreApplication app(argc, argv);
  QSslSocket s;
  QSslConfiguration cfg = s.sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s.setSslConfiguration(cfg);
  s.connectToHostEncrypted("www.ubuntu.com", 443);
  s.waitForConnected();
  qDebug() << s.sessionProtocol();
  return 0;
  }

  2. Create test.pro with the following contents:

  CONFIG += debug warn_all
  QT = core network
  SOURCES = test.cpp

  3. Install qtbase5-dev package.

  4. Compile using `qmake && make`.

  5. Run the generated ./test executable. It should print 15, not -1.

  [Where problems could occur]

  It is unlikely to cause issues on 64-bit platforms because long and
  uint64_t are both 64 bits long. On armhf potential problems may be
  related to availability of other protocols.

  [Original Description]

  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Oops, forgot about that. Done.

Also, ABI is not affected. We have symbols to track ABI, and there are
no symbols changes for libqt5network5.

** Description changed:

+ [Impact]
+ 
+ Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
+ less secure protocols.
+ 
+ [Test Plan]
+ 
+ 1. Create test.cpp with the following contents:
+ 
+ #include 
+ #include 
+ #include 
+ #include 
+ 
+ int main(int argc, char **argv) {
+ QCoreApplication app(argc, argv);
+ QSslSocket s;
+ QSslConfiguration cfg = s.sslConfiguration();
+ cfg.setProtocol(QSsl::TlsV1_3OrLater);
+ s.setSslConfiguration(cfg);
+ s.connectToHostEncrypted("www.ubuntu.com", 443);
+ s.waitForConnected();
+ qDebug() << s.sessionProtocol();
+ return 0;
+ }
+ 
+ 2. Create test.pro with the following contents:
+ 
+ CONFIG += debug warn_all
+ QT = core network
+ SOURCES = test.cpp
+ 
+ 3. Install qtbase5-dev package.
+ 
+ 4. Compile using `qmake && make`.
+ 
+ 5. Run the generated ./test executable. It should print 15, not -1.
+ 
+ [Where problems could occur]
+ 
+ It is unlikely to cause issues on 64-bit platforms because long and
+ uint64_t are both 64 bits long. On armhf potential problems may be
+ related to availability of other protocols.
+ 
+ [Original Description]
+ 
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04
  
  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf
  
  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).
  
  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)
  
  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());
  
  marking it as security since the most secure tls protocol is not used on
  some platforms

** Changed in: qtbase-opensource-src (Ubuntu Jammy)
   Status: Incomplete => Confirmed

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
  less secure protocols.

  [Test Plan]

  1. Create test.cpp with the following contents:

  #include 
  #include 
  #include 
  #include 

  int main(int argc, char **argv) {
  QCoreApplication app(argc, argv);
  QSslSocket s;
  QSslConfiguration cfg = s.sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s.setSslConfiguration(cfg);
  s.connectToHostEncrypted("www.ubuntu.com", 443);
  s.waitForConnected();
  qDebug() << s.sessionProtocol();
  return 0;
  }

  2. Create test.pro with the following contents:

  CONFIG += debug warn_all
  QT = core network
  SOURCES = test.cpp

  3. Install qtbase5-dev package.

  4. Compile using `qmake && make`.

  5. Run the generated ./test executable. It should print 15, not -1.

  [Where problems could occur]

  It is unlikely to cause issues on 64-bit platforms because long and
  uint64_t are both 64 bits long. On armhf potential problems may be
  related to availability of other protocols.

  [Original Description]

  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

A few days ago I asked on #ubuntu-security about it and was told that it's 
better to make a non-security SRU upload for it:
https://irclogs.ubuntu.com/2022/08/22/%23ubuntu-security.html#t12:01

So I uploaded it, and now it's waiting in unapproved queue for a release team 
member review:
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Confirmed

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1986936] Re: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages

[Dmitry Shachnev]

You probably need to install qtbase5-dev:i386, not just libqt5*:i386.

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

Title:
  No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the
  corresponding :i386 packages

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  While trying to link against corresponding libraries to get i386 executable 
like that:
  > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ...

  I get the following errors:

  > /usr/bin/ld: skipping incompatible 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets  

   
  > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory

  
  > /usr/bin/ld: skipping incompatible 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets  

   
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so 
when searching for -lQt5Gui 

  > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory

  
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so 
when searching for -lQt5Gui 

  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so 
when searching for -lQt5Core
   
  > /usr/bin/ld: cannot find -lQt5Core: No such file or directory   

  
  > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so 
when searching for -lQt5Core 

  despite corresponging packages are installed (libqt5gui5:i386 and same
  for widgets and core).

  Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no
  symlinks named exactly libQt5Core.so (and same for two other libs).

  Adding those symlinks by hand completely solves the problem.

  I believe however that those symlinks must be installed by
  corresponding .debs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1986936/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

I was not able to test it on Ubuntu because I don't have armhf hardware,
but I have just tested it on a Debian porterbox. The only difference
between Debian bookworm and sid versions of Qt is presence of this
patch.

I used this test code and complied it with qmake && make.

mitya57@harris:~/test$ cat test.pro
CONFIG += debug warn_all
QT = core network
SOURCES = test.cpp

mitya57@harris:~/test$ cat test.cpp
#include 
#include 
#include 
#include 

int main(int argc, char **argv) {
QCoreApplication app(argc, argv);
QSslSocket s;
QSslConfiguration cfg = s.sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s.setSslConfiguration(cfg);
s.connectToHostEncrypted("www.ubuntu.com", 443);
s.waitForConnected();
qDebug() << s.sessionProtocol();
return 0;
}

Without patch:

(bookworm_armhf-dchroot)mitya57@harris:~/test$ ./test 
-1

With patch:

(sid_armhf-dchroot)mitya57@harris:~/test$ ./test 
15

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Confirmed

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

I used your patch from comment #10 with only one minor change: for old
OpenSSL versions I replaced long with unsigned long to match the latest
version of upstream patch. But it doesn't matter for Ubuntu anyway.

I am attaching a debdiff for jammy-security and subscribing ~ubuntu-
security-sponsors.

** Patch added: "qtbase-opensource-src_5.15.3+dfsg-2ubuntu0.2.diff"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+attachment/5607636/+files/qtbase-opensource-src_5.15.3+dfsg-2ubuntu0.2.diff

** Also affects: qtbase-opensource-src (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu Jammy)
   Status: New => Confirmed

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Jammy:
  Confirmed

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Thank you. I will be offline for a few days, so I will upload this next
week.

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Thank you. Once the patch is accepted upstream, I will backport it to
Debian/Ubuntu packaging.

In Ubuntu we don't care about older OpenSSL versions, but upstream Qt
does care.

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

[Dmitry Shachnev]

Thank you for the patch!

Qt 6 still uses unsigned long:
https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/tls/openssl/qsslsocket_openssl_symbols.cpp#n126

Can you please submit your patch to codereview.qt-project.org, or at
least file a bug at bugreports.qt.io?

We usually don't add patches that were not merged upstream.

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1939255] Re: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once

[Dmitry Teselkin]

Hi. It seems this issue may occur not only when receiving addresses on multiple 
interfaces, but also when dhcp requests on multiple interfaces times out and 
the hook script was called with 'reason' == FAIL.
Found on Ubuntu 20.04.3 LTS, systemd is 245.4-4ubuntu3.15.

** Attachment added: "DHCPDISCOVER-no_DHCPOFFERS-exit_1.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+attachment/5581263/+files/DHCPDISCOVER-no_DHCPOFFERS-exit_1.png

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

Title:
  dhclient triggers systemd-resolved start limit when processing more
  than 5 interfaces at once

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  on a system where systemd-resolved is running, if dhclient is used on
  more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter-
  hooks.d/resolved' script multiple times, which then restarts systemd-
  resolved multiple times, triggering the unit's start-limit throttle
  which results in the unit entering failed state

  [test case]

  on a system with more than 5 available interfaces to run dhclient on
  (where all the interfaces will get a dhcp response), run dhclient with
  the interfaces:

  $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15

  check if systemd-resolved failed:

  $ journalctl -b -1 -u systemd-resolved
  ...
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start 
request repeated too quickly.
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with 
result 'start-limit-hit'.
  Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name 
Resolution.

  [regression potential]

  failure to start/stop/restart systemd-resolved, or problems adding
  dhclient-provided DNS nameservers to systemd-resolved

  [scope]

  this is needed only for b/f

  the dhclient 'hook' script is provided by the systemd package in focal
  and earlier, and needs fixing in those releases

  in h and later, the 'hook' script is included in the isc-dhcp-client
  package and notifies systemd-resolved in a more direct way without
  requiring restarting, and so doesn't trigger the restart limiting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+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 1969182] [NEW] package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Dmitry Gribenchuk]

Public bug reported:

Have this problem and kernel panic when boot on 5.15.0-25.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  grid   2148 F pulseaudio
 /dev/snd/pcmC0D0p:   grid   2148 F...m pulseaudio
CasperMD5CheckResult: fail
Date: Fri Apr 15 08:32:07 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-04-04 (10 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: LENOVO 20RA002SRT
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/vg_core-sys ro quite splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET33W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RA002SRT
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.ec.firmware.release: 1.13
dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
dmi.product.family: ThinkPad E14
dmi.product.name: 20RA002SRT
dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
dmi.product.version: ThinkPad E14
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Have this problem and kernel panic when boot on 5.15.0-25.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grid   2148 F pulseaudio
   /dev/snd/pcmC0D0p:   grid   2148 F...m pulseaudio
  CasperMD5CheckResult: fail
  Date: Fri Apr 15 08:32:07 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-04-04 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: LENOVO 20RA002SRT
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/vg_core-sys ro quite splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R16ET33W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20RA002SRT
  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.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
  

[Touch-packages] [Bug 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

Ok, thank you Paulo.

As advised by Brian, I'm adding block-proposed tags to make sure the
current packages don't get accidentally released.

** Tags added: block-proposed-focal block-proposed-impish

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  Fix Committed
Status in qtbase-opensource-src source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

Marc, can you do it please? You can take my changes but use a different
version number so that it's rebuilt. Then we will ask the SRU team to
remove the versions in -proposed.

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  Fix Committed
Status in qtbase-opensource-src source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

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

[Dmitry Mikhailov]

You can rebuild 13.99-1 RTP modules without GStreamer support as per
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/889

If you can't wait for fix you can grab prebuilt library binaries from
there although I'm against using unsigned untested 3rd-party binaries in
production. Works for me.

-- 
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:
  Unknown
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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

Tested in an Impish chroot:

root@mitya57:/test# time ./test-2021-38593 ./input.svg
Testing for CVE-2021-38593...
If the test doesn't finish immediately, you probably are affected.
Test finished.

real0m0.033s
user0m0.004s
sys 0m0.017s
root@mitya57:/test# echo $?
0
root@mitya57:/test# apt policy libqt5gui5
libqt5gui5:
  Installed: 5.15.2+dfsg-12ubuntu1
  Candidate: 5.15.2+dfsg-12ubuntu1
  Version table:
 *** 5.15.2+dfsg-12ubuntu1 500
500 http://archive.ubuntu.com/ubuntu impish-proposed/universe amd64 
Packages
100 /var/lib/dpkg/status
 5.15.2+dfsg-12 500
500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages

With the version from release pocket, the test program does not finish
after 30 seconds.

** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  Fix Committed
Status in qtbase-opensource-src source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

** Also affects: qtbase-opensource-src (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  New
Status in qtbase-opensource-src source package in Impish:
  New

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

** Description changed:

+ [Impact]
+ 
  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593
  
  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942
  
- The original issue is public since July 29th. If I'm allowed to upload
- further files, I'll send a simple test program.
+ The original issue is public since July 29th.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: libqt5svg5 5.12.8-0ubuntu1
- ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9
- Uname: Linux 5.14.0-1005-oem x86_64
- ApportVersion: 2.20.11-0ubuntu27.21
- Architecture: amd64
- CasperMD5CheckResult: skip
- CurrentDesktop: GNOME
- Date: Mon Nov  8 20:24:34 2021
- InstallationDate: Installed on 2012-07-06 (3411 days ago)
- InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
- ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
- SourcePackage: qtsvg-opensource-src
- UpgradeStatus: Upgraded to focal on 2020-10-03 (400 days ago)
+ [Test Plan]
+ 
+ 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
+ 2. Build the attached project with the system's version of Qt:
+/usr/lib/qt5/bin/qmake test-2021-38593.pro && make
+ 3. Start the resulting binary and pass the path to the included input file as 
first parameter:
+./test-2021-38593 ./input.svg
+The binary should return immediately and without error messages. If it 
doesn't, you might be affected.
+ 
+ [Where problems could occur]
+ 
+ The fix tries to skip drawing dashes that would be invisible anyway. So
+ a potential problem may that it skips too much. In fact, this has
+ already happened, and upstream had to adjust the fix.
+ 
+ [Other Info]
+ 
+ The patch is a combination of the following upstream commits:
+ 
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  New

Bug description:
  [Impact]

  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th.

  [Test Plan]

  1. Install libqt5svg5-dev, qtbase5-dev and their dependencies.
  2. Build the attached project with the system's version of Qt:
 /usr/lib/qt5/bin/qmake test-2021-38593.pro && make
  3. Start the resulting binary and pass the path to the included input file as 
first parameter:
 ./test-2021-38593 ./input.svg
 The binary should return immediately and without error messages. If it 
doesn't, you might be affected.

  [Where problems could occur]

  The fix tries to skip drawing dashes that would be invisible anyway.
  So a potential problem may that it skips too much. In fact, this has
  already happened, and upstream had to adjust the fix.

  [Other Info]

  The patch is a combination of the following upstream commits:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

> Anything I can do now to help this arrive in 20.04?

No, I just need to find some free time again. Thanks for reminding me.

** Also affects: qtbase-opensource-src (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Focal:
  New

Bug description:
  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th. If I'm allowed to upload
  further files, I'll send a simple test program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5svg5 5.12.8-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9
  Uname: Linux 5.14.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Nov  8 20:24:34 2021
  InstallationDate: Installed on 2012-07-06 (3411 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtsvg-opensource-src
  UpgradeStatus: Upgraded to focal on 2020-10-03 (400 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593

[Dmitry Shachnev]

** Package changed: qtsvg-opensource-src (Ubuntu) => qtbase-opensource-
src (Ubuntu)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Dmitry Shachnev (mitya57)

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th. If I'm allowed to upload
  further files, I'll send a simple test program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5svg5 5.12.8-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9
  Uname: Linux 5.14.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Nov  8 20:24:34 2021
  InstallationDate: Installed on 2012-07-06 (3411 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtsvg-opensource-src
  UpgradeStatus: Upgraded to focal on 2020-10-03 (400 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1951470] Re: webkit javascript segmentation fault

[Dmitry Shachnev]

I have uploaded Focal, Impish and Hirsute debdiffs, they are now waiting
for approval in review queues.

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

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  In Progress
Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-opensource-src source package in Focal:
  In Progress
Status in qtwebkit-opensource-src source package in Hirsute:
  In Progress
Status in qtwebkit-opensource-src source package in Impish:
  In Progress
Status in qtwebkit-opensource-src source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * WebKit Javascript engine is causing a segmentation fault on big
  endian (s390x) systems.

   * This happens for example when transferring an html to a pdf file
  using wkhtmltopdf.

   * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
 in macro getProperty(slow), which solves this unpleasant situation.

   * The JIT ocde is 32bit (even on 64bit systems),
 hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.

  [Test Plan]

   * Testing is very straight forward by following these steps:

   * install the following packages (incl. their dependencies):
 $ sudo apt install libqt5webkit5 wkhtmltopdf

   * create an html file like this:
 $ vi index.html
 $ cat index.html
 
 
   
   
 
   
 
   
 

   * create a JavaScript file like this:
 $ vi min.js
 $ cat min.js
 var i = Math.max

   * call wkhtmltopdf to process the local files:
 $ wkhtmltopdf --enable-local-file-access index.html test.pdf

   * if it's broken one gets this output:
 Loading page (1/2)
 Segmentation fault (core dumped) ] 50%
 and no pdf file was generated:
 $ ls *.pdf
 ls: cannot access '*.pdf': No such file or directory

   * in case it's fixed one gets this output:
 Loading page (1/2)
 Printing pages (2/2)   
 Done   
 and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
 $ ls -l ./*.pdf
 -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf

  [Where problems could occur]

   * While this issue only affects big endian systems (like s390x),
 a bad fix may have an impact on little endian systems, too
 for example in case the wrong function got used in the macro.

   * But loadpFromInstruction is known to work for LE and BE systems;

   * and on top cross-architecture builds were done:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470

   * and tested on s390x (if the fix works) and on non-s390x (regression
  testing).

   * The changes are otherwise very limited, just:
 macro getProperty(slow)
 -loadisFromInstruction(6, t1)
 +loadpFromInstruction(6, t1)
 hence I think there is not much more to say.

  [Other Info]
   
   * The maintainer of the Debian packages (Dmitry Shachnev)
 is going to add this to the Debian package, too.

   * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs
  are ongoing.

   * The issue does not occur with the very latest upstream version anymore,
 and was fixed in a similar way as part of a commit
 that fixes numerous other CLoop issues on top:
 "Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
 commit 3fdde71c7d95d758a61fcbc4c58168616794c102

  __

  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine

  Contact Information = andreas.kreb...@de.ibm.com

  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Z

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   index.html:
  
  
    
    

    
  
    
  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%

  Userspace tool common name: wkhtmltopdf

  The userspace tool has the following bit modes: 64

  Userspace rpm: libqt5webkit5

  Userspace tool obtained from project website:  na

  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes 
the prope

[Touch-packages] [Bug 1946595] Re: indicator-applet-complete clock occasionally shows UTC

[Dmitry Shachnev]

Standalone is not indicator, it's mate-panel's built-in clock applet.

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

Title:
  indicator-applet-complete clock occasionally shows UTC

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Sometimes at login, but sometimes at other times, the clock in
  indicator-applet-complete starts showing UTC instead of local.

  It is not a system clock problem, in the terminal and in the
  standalone clock applet the time is correct. See
  https://i.stack.imgur.com/x11A4.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: indicator-applet-complete (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Oct 10 08:37:00 2021
  InstallationDate: Installed on 2018-04-27 (1261 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: indicator-applet
  UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1946595/+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 1946595] Re: indicator-applet-complete clock occasionally shows UTC

[Dmitry Shachnev]

The applet just shows what the actual indicator provides, so reassigning
to indicator-datetime.

** Package changed: indicator-applet (Ubuntu) => indicator-datetime
(Ubuntu)

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

Title:
  indicator-applet-complete clock occasionally shows UTC

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Sometimes at login, but sometimes at other times, the clock in
  indicator-applet-complete starts showing UTC instead of local.

  It is not a system clock problem, in the terminal and in the
  standalone clock applet the time is correct. See
  https://i.stack.imgur.com/x11A4.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: indicator-applet-complete (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sun Oct 10 08:37:00 2021
  InstallationDate: Installed on 2018-04-27 (1261 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: indicator-applet
  UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1946595/+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 1941933] Re: sticks the mouse pointer when using the touchpad

[Dmitry Shapkin]

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

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

Title:
  sticks the mouse pointer when using the touchpad

Status in Ubuntu:
  New

Bug description:
  Periodicaly sticks the mouse pointer when using the touchpad.
  Ubuntu 21.04 on laptop Honor BDR-WFH9HN.
  When I use a mouse - everything is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 28 08:43:04 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: QUANTA Computer Inc Iris Xe Graphics [152d:127d]
  InstallationDate: Installed on 2021-08-08 (19 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:1040 Quanta Computer, Inc. 
ov9734_techfront_camera
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HONOR BOD-WXX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=2eeed0ae-6ec0-453a-95f4-20c82c0509ad ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2021
  dmi.bios.release: 3.2
  dmi.bios.vendor: HONOR
  dmi.bios.version: 3.02
  dmi.board.asset.tag: N/A
  dmi.board.name: BOD-WXX9-PCB
  dmi.board.vendor: HONOR
  dmi.board.version: M1050
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HONOR
  dmi.chassis.version: M1050
  dmi.ec.firmware.release: 3.2
  dmi.modalias: 
dmi:bvnHONOR:bvr3.02:bd02/22/2021:br3.2:efr3.2:svnHONOR:pnBOD-WXX9:pvrM1050:rvnHONOR:rnBOD-WXX9-PCB:rvrM1050:cvnHONOR:ct10:cvrM1050:
  dmi.product.family: MagicBook
  dmi.product.name: BOD-WXX9
  dmi.product.sku: C171
  dmi.product.version: M1050
  dmi.sys.vendor: HONOR
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1941933/+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 1933669] Re: qt3d5-dev - cmake support missing for Qt3D Animation

[Dmitry Shachnev]

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

Unfortunately these files are only available in newer Ubuntu versions (≥
20.10). See bug 1878233 for details.

** This bug has been marked a duplicate of bug 1878233
   Unable to locate package/Headers missing

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

Title:
  qt3d5-dev - cmake support missing for Qt3D Animation

Status in qt3d-opensource-src package in Ubuntu:
  New

Bug description:
  Hello,

  I'm working on a Qt application which uses the Qt3D module. The
  application is spec'd to support ubuntu 20.04 at least.

  The qt3d-dev package (at least on focal) is missing the following
  files:

  /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfig.cmake
  
/usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfigVersion.cmake

  All others Qt3D modules have their own similar files but not the Animation 
module.
  This prevent me from building my application using official packages.
  Are they missing on purpose? Is there any work around?

  All the best

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1933669/+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 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

I have performed the verification following the Test Plan. The full log
is attached.

Relevant part:

The following packages will be REMOVED:
  qt5-default
The following NEW packages will be installed:
  gcc-11-base libboost-iostreams1.74.0 libcap2 libisl23 libmd0 libperl5.32 
libxrender1 libxxhash0 lto-disabled-list perl-modules-5.32
The following packages will be upgraded:
  ... libqt5core5a libqt5dbus5 libqt5gui5 ...

As can be seen here, no *-gles packages are installed.

** Attachment added: "chroot-upgrade.txt"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src-gles/+bug/1920130/+attachment/5504247/+files/chroot-upgrade.txt

** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute

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

Title:
  System icons missing in kubuntu 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src-gles package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Hirsute:
  Fix Committed
Status in qtbase-opensource-src-gles source package in Hirsute:
  Fix Committed
Status in qtbase-opensource-src-gles package in Debian:
  Fix Released

Bug description:
  [Impact]

  This affects Groovy → Hirsute upgrades for users who had qt5-default
  package installed.

  For these users, apt could replace libqt5gui5 with libqt5gui5-gles,
  which is not suitable for most desktop systems and can result in all
  kinds of broken UI (such as missing icons).

  [Test Plan]

  1. Get a groovy amd64 system (e.g. a chroot).
  2. Install qt5-default package.
  3. Replace groovy with hirsute in /etc/apt/sources.list.
  4. Run "apt update".
  5. Run "apt dist-upgade".

  Incorrect behavior:

  The following packages will be REMOVED:
libqt5gui5 qt5-default qtbase5-dev
  The following NEW packages will be installed:
... libqt5gui5-gles ...

  Correct behavior: only qt5-default is removed, libqt5gui5 is not
  removed and libqt5gui5-gles is not installed.

  [Where problems could occur]

  The fix is adding "Breaks: qt5-default" in three packages:
  - qtbase5-dev (built from qtbase-opensource-src source).
  - qtbase5-gles-dev (built from qtbase-opensource-src-gles source).
  - libqt5gui5-gles (built from qtbase-opensource-src-gles source).

  It can affect apt's dependency resolver. Example of a problem may be
  the resolver keeping the old behavior in some cases.

  [Other Info]

  See this post for details on what the -gles packages are:
  https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html

  See my discussion with one of the developers of apt on this issue:
  https://lists.debian.org/debian-devel/2021/05/msg00076.html
  https://lists.debian.org/debian-devel/2021/05/msg00150.html
  https://lists.debian.org/debian-devel/2021/05/msg00162.html

  Also see this comment where I collected some links to stories of users who 
were affected by this bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389#10

  [Original Description]

  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 

[Touch-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

[Dmitry Shachnev]

The fix should land in Impish (21.10) very soon:
https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.15.2+dfsg-6.

Do you also want a fix for Hirsute (21.04)? If yes, you can help me by
filling the SRU template in the description (see
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template).

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

** Description changed:

+ [Impact]
+ 
+ This affects Groovy → Hirsute upgrades for users who had qt5-default
+ package installed.
+ 
+ For these users, apt could replace libqt5gui5 with libqt5gui5-gles,
+ which is not suitable for most desktop systems and can result in all
+ kinds of broken UI (such as missing icons).
+ 
+ [Test Plan]
+ 
+ 1. Get a groovy amd64 system (e.g. a chroot).
+ 2. Install qt5-default package.
+ 3. Replace groovy with hirsute in /etc/apt/sources.list.
+ 4. Run "apt update".
+ 5. Run "apt dist-upgade".
+ 
+ Incorrect behavior:
+ 
+ The following packages will be REMOVED:
+   libqt5gui5 qt5-default qtbase5-dev
+ The following NEW packages will be installed:
+   ... libqt5gui5-gles ...
+ 
+ Correct behavior: only qt5-default is removed, libqt5gui5 is not removed
+ and libqt5gui5-gles is not installed.
+ 
+ [Where problems could occur]
+ 
+ The fix is adding "Breaks: qt5-default" in three packages:
+ - qtbase5-dev (built from qtbase-opensource-src source).
+ - qtbase5-gles-dev (built from qtbase-opensource-src-gles source).
+ - libqt5gui5-gles (built from qtbase-opensource-src-gles source).
+ 
+ It can affect apt's dependency resolver. Example of a problem may be the
+ resolver keeping the old behavior in some cases.
+ 
+ [Other Info]
+ 
+ See this post for details on what the -gles packages are:
+ https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html
+ 
+ See my discussion with one of the developers of apt on this issue:
+ https://lists.debian.org/debian-devel/2021/05/msg00076.html
+ https://lists.debian.org/debian-devel/2021/05/msg00150.html
+ https://lists.debian.org/debian-devel/2021/05/msg00162.html
+ 
+ Also see this comment where I collected some links to stories of users who 
were affected by this bug:
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389#10
+ 
+ [Original Description]
+ 
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially
  was fine, but I then install kdenlive and krita which has messed up the
  system icons and window decorations (corners of windows are showing
  black squares).
  
  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.
  
  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04
  
  Looking at the following may shed some light on the problem...
  
  Thanks, Paul.
  
- more .xsession-errors 
+ more .xsession-errors
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
- 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
+  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
+ 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
+  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
-  of null
+  of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
- 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or 

[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

As it turns out, this also needs a change in qtbase-opensource-src.
Change in -gles is not enough:

https://lists.debian.org/debian-devel/2021/05/msg00076.html
https://lists.debian.org/debian-devel/2021/05/msg00150.html

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  System icons missing in kubuntu 21.04

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src-gles package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Hirsute:
  New
Status in qtbase-opensource-src-gles source package in Hirsute:
  New
Status in qtbase-opensource-src-gles package in Debian:
  Fix Released

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from 
launcher.
  kdeinit5: Got SETENV 
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0'
 from launch
  er.
  QDBusConnection: error: could not send signal to service "" path 
"//home/paul/.kde/share/config/kdeglobals" interface 
  "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: 
//home/paul/.kde/share/config/kdeglobals
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25:
 QML ScrollBar: Bindi
  ng loop detected for property 

[Touch-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

[Dmitry Shachnev]

Thank you for the links!

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => In Progress

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Dmitry Shachnev (mitya57)

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

[Dmitry Shachnev]

Qt actually prefers system copy from shared-mime-info if it's available.
Here is the code for 5.12.8 (used in Ubuntu 20.04):

https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/mimetypes/qmimedatabase.cpp?h=5.12.8#n99

The internal copy (":/qt-project.org/qmime") is only used when the
system one is missing (fdoIterator == mimeDirs.constEnd()).

Furthermore, in Ubuntu 20.10 and 21.04 we are building Qt with -no-
mimetype-database, which makes Qt use *only* the system copy:

https://salsa.debian.org/qt-kde-team/qt/qtbase/-/commit/f0d53be16a31ea55

So I think it is a bug in shared-mime-info only, not in Qt. Do you
agree?

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

Hi Owen,

Thanks a lot for sharing the log. Indeed, qt5-default seems to be the
cause of this bug. In https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=976389#15 I explained in more detail my
understanding of why this is happening.

The fix should land in Impish (development release) in a few hours, and
then I will look at a fix for Hirsute (21.04).

** Package changed: qtdeclarative-opensource-src (Ubuntu) =>
qtdeclarative-opensource-src-gles (Ubuntu)

** Changed in: qtdeclarative-opensource-src-gles (Ubuntu)
   Status: Won't Fix => Fix Committed

** Also affects: qtdeclarative-opensource-src-gles (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

Title:
  System icons missing in kubuntu 21.04

Status in qtdeclarative-opensource-src-gles package in Ubuntu:
  Fix Committed
Status in qtdeclarative-opensource-src-gles source package in Hirsute:
  New
Status in qtdeclarative-opensource-src-gles package in Debian:
  New

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from 
launcher.
  kdeinit5: Got SETENV 
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0'
 from launch
  er.
  QDBusConnection: error: could not send signal to service "" path 
"//home/paul/.kde/share/config/kdeglobals" interface 
  "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: 

[Touch-packages] [Bug 1926802] Re: qt5-default package is missed in 21.04

[Dmitry Shachnev]

Qt 4 was removed, Qt 5 is now default, so that package is no longer
needed.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  qt5-default package is missed in 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Previous 20.10 version has the qt5-default package in place (see
  https://packages.ubuntu.com/groovy/qt5-default ).

  Please upload the  qt5-default package for 21.04 Ubuntu version.

  What is interesting - all its dependencies can be simply installed
  with `sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5
  -dev-tools` .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+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 1850814] Re: Copy & Paste is broken in QT apps after 50 days uptime

[Dmitry Shachnev]

This bug is fixed in Qt 5.12.3 and newer. The current LTS version,
Ubuntu 20.04, has Qt 5.12.8. So this bug is already fixed for some time.

Unfortunately I don't have time to support older releases like 18.04.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Fix Released

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

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

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

Title:
  Copy & Paste is broken in QT apps after 50 days uptime

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Debian:
  Unknown

Bug description:
  Please see this bug report:
  https://bugreports.qt.io/browse/QTBUG-65145

  And this corresponding fix:
  https://codereview.qt-project.org/c/qt/qtbase/+/254187/

  Any way to get this included in a Ubuntu 18.04 package update?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libqt5core5a 5.9.5+dfsg-0ubuntu2.3
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Oct 31 09:14:55 2019
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1850814/+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 1926373] Re: Missing header files for Qt3DExtras:

[Dmitry Shachnev]

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

This is fixed in Ubuntu 20.10 (Groovy) and newer versions.

Unfortunately it is not possible to fix this for 20.04 (Focal) because
the change does not meet the stable update criteria.

** This bug has been marked a duplicate of bug 1878233
   Unable to locate package/Headers missing

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

Title:
  Missing header files for Qt3DExtras:

Status in qt3d-opensource-src package in Ubuntu:
  New

Bug description:
  Unable to build most examples contained in the qt3d5-examples (and, of
  course, any code that relies on Qt3DExtras). This is caused by a
  missing development package with headers for Qt3DExtras.

  The Qt3DExtras binary library (libQt53DExtras.so) is included in the
  qt3d5-dev package, but all the Qt3DExtras header files are missing
  (Qt3DExtras/QForwardRenderer, Qt3DExtras/QPhongMaterial, etc...). This
  makes QT OpenGL development in Ubuntu pretty much unusable.

  At first, installing mssql-mlservices-python and manually copying it's
  version of the Qt3DExtras headers seemed to be a work-around, but it
  resulted in undefined references during linking.

  I would have tagged "qt3d5-examples" in the "In what package did you
  find this bug?", but it tells me that the package doesn't exist in
  ubuntu, whereas https://packages.ubuntu.com/focal/qt3d5-examples
  clearly lists it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1926373/+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 1923513] [NEW] xrandr --panning problem

[dmitry eshchenko]

Public bug reported:

Dear community 
Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint 
20 

Distribution: 
cat /etc/upstream-release/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"

Netbook is with small screen 
1024x600
To get bigger virtual screen I use xrandr like:

xrandr --fb 1024x768 --output LVDS1 --panning 1024x768

To return to normal screen I use

xrandr --fb 1024x600

What is expected:
when the mouse moves outside the 1024x600 screen - new "clean" virtual area 
appears.

What is in reality:

With fresh Ubuntu the first script results to wrong "background" image on the 
extended area:
When I move mouse down below the original 600 pixels,
first 768-600=168 strings are shown like a background image.
Or 
new virtual 601 string is the copy of the old 1
602 string is the copy of the old 2
...
768 string is the copy of the old 168
 
It looks like an index shift in the array:
The string which "disappears" from the top is moved to the bottom   

This "background" image can be overwritten by the real application window.
For example, if I move the terminal window it appears on the top of this 
"background"   
But after moving mouse back inside the 1024x600 screen and back outside the 
1024x600 screen,
the shifted copy of the top part of the screen appears at the bottom according 
the 
1->601 
2->602 etc logic.

After playing a lot with xrandr parameters I had found a workaround:
One has to specify the first parameter in --fb bigger than the first parameter 
in --panning

For example:
xrandr --fb 1025x768 --output LVDS1 --panning 1024x768

Here 1025>1024

I had checked this bug  with two different laptops, so it is not related with 
the hardware.
More information:
xrandr -v
xrandr program version   1.5.0
Server reports RandR version 1.6

The working configuration:
xrandr
Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767
LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 
220mm x 130mm panning 1024x768+0+0
   1024x600  60.19*+
   1024x576  59.9059.82  
   960x540   59.6359.82  
   800x600   60.3256.25  
   864x486   59.9259.57  
   640x480   59.94  
   720x405   59.5158.99  
   640x360   59.8459.32  
   512x300   60.00  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis

Wrongly working configuration:
 
xrandr
Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 
220mm x 130mm panning 1024x768+0+0
   1024x600  60.19*+
   1024x576  59.9059.82  
   960x540   59.6359.82  
   800x600   60.3256.25  
   864x486   59.9259.57  
   640x480   59.94  
   720x405   59.5158.99  
   640x360   59.8459.32  
   512x300   60.00  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Hope you can reproduce this bug.

Best regards, Dmitry

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

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

Title:
  xrandr --panning problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Dear community 
  Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux 
Mint 20 

  Distribution: 
  cat /etc/upstream-release/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu Focal Fossa"

  Netbook is with small screen 
  1024x600
  To get bigger virtual screen I use xrandr like:

  xrandr --fb 1024x768 --output LVDS1 --panning 1024x768

  To return to normal screen I use

  xrandr --fb 1024x600

  What is expected:
  when the mouse moves outside the 1024x600 screen - new "clean" virtual area 
appears.

  What is in reality:

  With fresh Ubuntu the first script results to wrong "background" image on the 
extended area:
  When I move mouse down below the original 600 pixels,
  first 768-600=168 strings are shown like a background image.
  Or 
  new virtual 601 string is the copy of the old 1
  602 string is the copy of the old 2
  ...
  768 string is the copy of the old 168
   
  It looks like an index shift in the array:
  The string which "disappears" from the top is moved to the bottom   

  This "background" image can be overwritten by the real application window.
  For example, if I move the terminal window it appears on the top of this 
"background"   
  But after moving mous

[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

@poet_imp Thanks for the logs! Unfortunately, these are only the latest
logs and they don't explain what happened when you upgraded Ubuntu.

Maybe you can attach the historical logs from /var/log/apt too? They
have names like history.log.*.gz and term.log.*.gz. If you upgraded
recently, then I guess it would be *.1.gz. Otherwise you can look at
modification dates.

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

Title:
  System icons missing in kubuntu 21.04

Status in qtdeclarative-opensource-src package in Ubuntu:
  Won't Fix
Status in qtdeclarative-opensource-src-gles package in Debian:
  New

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from 
launcher.
  kdeinit5: Got SETENV 
'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0'
 from launch
  er.
  QDBusConnection: error: could not send signal to service "" path 
"//home/paul/.kde/share/config/kdeglobals" interface 
  "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: 
//home/paul/.kde/share/config/kdeglobals
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25:
 QML ScrollBar: Bindi
  ng loop detected for property "visible"
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: 
QML GridView: Binding loop detected for pro
 

[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

Hi! I am the Qt maintainer here.

The fix mentioned in https://bugs.launchpad.net/ubuntu/+source
/qtdeclarative-opensource-src/+bug/1920130/comments/4 is the correct
one. libqt5quick5-gles is not intended for general use, it should be
only installed on OpenGL ES capable hardware.

However, I really want to understand how users end up with this package
being installed. See this related thread in Debian:
https://lists.debian.org/debian-devel/2021/01/msg00404.html.

If anyone else upgrading from Groovy to Hirsute sees this, please attach
here these log files (or, if you think they are private, send them
directly to me mity...@ubuntu.com):

- /var/log/apt/history.log
- /var/log/apt/term.log

Also if removing libqt5quick5-gles tries to remove any other package
(which does not have -gles in name), please paste the list of those
packages.

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

** Also affects: qtdeclarative-opensource-src-gles (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389
   Importance: Unknown
   Status: Unknown

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

Title:
  System icons missing in kubuntu 21.04

Status in qtdeclarative-opensource-src package in Ubuntu:
  Won't Fix
Status in qtdeclarative-opensource-src-gles package in Debian:
  Unknown

Bug description:
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors 
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  QSGTextureAtlas: texture atlas allocation failed, code=501
  file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML 
ColumnLayout: Cannot anchor to an item that 
  isn't a parent or sibling.
  xsettingsd: Reloading configuration
  xsettingsd: Loaded 11 settings from 
/home/paul/.config/xsettingsd/xsettingsd.conf
  kdeinit5: Got SETENV 

[Touch-packages] [Bug 1905969] Re: Asus Zephyrus G14 microphone not works

[Dmitry Mamchyts]

Hi, @Manah
After kernel upgrade to 5.10.9-051009-generic - all works fine.

Also I am install asus-nb-ctrl (https://gitlab.com/asus-linux/asus-nb-
ctrl). You can see comment that in 5.11 all must works fine by default.

Now, I am waiting 21.04 release (looks like by default ubuntu will use
5.11 kernel).

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

Title:
  Asus Zephyrus G14 microphone not works

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA 
GeForce GTX 1650.
  I am use 5.9.8-050908-generic kernel from 
(kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/)

  dmamchyts@ga401ih:~$ cat /etc/os-release
  NAME="Ubuntu"
  VERSION="20.10 (Groovy Gorilla)"

  I have some problem with notebook microphone.
  When I use headphones via 3.5 jack - all works fine.
  But without headphones - system doesn't see any microphone device in settings.
  I am using KDE

  
dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l
 List of PLAYBACK Hardware Devices 
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 
Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

  
  Also, I try to report issue into kernel team (they help me to fix issue with 
speakers), you can find some into it: 
https://bugzilla.kernel.org/show_bug.cgi?id=210359

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  Uname: Linux 5.9.8-050908-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov 27 17:13:59 2020
  InstallationDate: Installed on 2020-11-10 (17 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.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: 11/05/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GA401IH.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA401IH
  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.ec.firmware.release: 3.13
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.210:bd11/05/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG Zephyrus G14
  dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905969/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Dmitry Obelov]

As a workaround please disable that feature by editing
/etc/pulse/default.pa and commenting or removing load-module module-
switch-on-port-available and reboot the system.

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1906091] Re: libx264-148 libx264-152 conflict segmentation fault SIGSEGV

[Dmitry]

Rico Tzschichholz, thank you very much, you are absolutely correct. There was 
OpenCV 3.3 installed on my system, it remained after update from 16.04 to 18.04 
with all its 16.04 dependencies.
I removed OpenCV 3.3 and everything got fixed.
Thanks a lot for help.
The issue is fixed and may be closed.

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

Title:
  libx264-148 libx264-152 conflict segmentation fault SIGSEGV

Status in x264 package in Ubuntu:
  New

Bug description:
  In my app I have segfault due to conflict of libx264-148 vs libx264-152.
  I use gstreamer and libopencv_videoio in my project.
  System is Ubuntu 18.04.5

  The problem is that versions of libx264 get mixed due to implicit
  linking.

  Libraries are linked like this:
  gstreamer -> x264enc -> libx264-152
  libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148

  Both opencv-based code and gstreamer-based code works well if used
  separately.

  At the top of backtrace I see:
  Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
  #0  0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at 
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
  #1  0x7f2927a93f55 in x264_nal_encode () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
  #2  0x7f2927af866c in  () at /usr/lib/x86_64-linux-gnu/libx264.so.148
  #3  0x7f2927b0143b in x264_encoder_headers () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148

  If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in
  both libx264-148 and libx264-152

  
  Here is example code which fails (C++ needed):

  int main (int argc, char *argv[])
  {
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;

gst_init (, );

auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);

GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");

app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();

app->pipeline = gst_parse_launch(R"(filesrc
  location=videoplayback.mp4 ! decodebin ! videoconvert ! x264enc
  byte-stream=true threads=1
  tune=zerolatency bitrate=400 key-
  int-max=50 option-string="force-cfr=1" !
  video/x-h264,profile=baseline,stream-format="byte-stream" !
  h264parse ! mpegtsmux ! hlssink
  location="/tmp/data%06d.ts" max-files=100
  playlist-length=10 playlist-location="/tmp/kek"
  target-duration=10 playlist-root=".")", NULL);

g_assert (app->pipeline);

bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);

gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);

caps = gst_caps_new_simple ("video/x-raw-rgb",
  "bpp",G_TYPE_INT,8,
  "depth",G_TYPE_INT,8,
   "width", G_TYPE_INT, 640,
   "height", G_TYPE_INT, 480,
   NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);

g_main_loop_run (app->loop);

GST_DEBUG ("stopping");

gst_element_set_state (app->pipeline, GST_STATE_NULL);

gst_object_unref (bus);
g_main_loop_unref (app->loop);

return 0;
  }


  
  How can I solve this? PLease help!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-05-07 (1667 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: x264 2:0.152.2854+gite9a5903-2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-118-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-12-28 (338 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1906091/+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 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend

[Dmitry Petukhov]

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

I have this issue too. I'm using Dell latitude 5501, Xubuntu 20 and Xfce. It's 
very painful.
Is anybody have found the solution?

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

Title:
  lightdm does not greet or present login prompt when resuming from
  laptop suspend

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Expected result: when opening laptop lid the lock screen presents
  itself so I can unlock my session

  Actual result: the contents of my desktop are visible (windows, etc)
  and I can move my mouse cursor around but I cannot interact with the
  desktop session at all. Hovering over UI elements or clicking them has
  no effect.

  In order to get the login prompt I have to ctrl+alt+f1, login at the
  console, and run sudo systemctl restart lightdm, then I can login
  normally and resume whatever I was doing from before I closed the
  laptop lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 23 09:08:32 2019
  InstallationDate: Installed on 2019-11-09 (14 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+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 1906091] ProcEnviron.txt

[Dmitry]

apport information

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

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

Title:
  libx264-148 libx264-152 conflict segmentation fault SIGSEGV

Status in x264 package in Ubuntu:
  New

Bug description:
  In my app I have segfault due to conflict of libx264-148 vs libx264-152.
  I use gstreamer and libopencv_videoio in my project.
  System is Ubuntu 18.04.5

  The problem is that versions of libx264 get mixed due to implicit
  linking.

  Libraries are linked like this:
  gstreamer -> x264enc -> libx264-152
  libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148

  Both opencv-based code and gstreamer-based code works well if used
  separately.

  At the top of backtrace I see:
  Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
  #0  0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at 
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
  #1  0x7f2927a93f55 in x264_nal_encode () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
  #2  0x7f2927af866c in  () at /usr/lib/x86_64-linux-gnu/libx264.so.148
  #3  0x7f2927b0143b in x264_encoder_headers () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148

  If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in
  both libx264-148 and libx264-152

  
  Here is example code which fails (C++ needed):

  int main (int argc, char *argv[])
  {
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;

gst_init (, );

auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);

GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");

app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();

app->pipeline = gst_parse_launch(R"(filesrc
  location=videoplayback.mp4 ! decodebin ! videoconvert ! x264enc
  byte-stream=true threads=1
  tune=zerolatency bitrate=400 key-
  int-max=50 option-string="force-cfr=1" !
  video/x-h264,profile=baseline,stream-format="byte-stream" !
  h264parse ! mpegtsmux ! hlssink
  location="/tmp/data%06d.ts" max-files=100
  playlist-length=10 playlist-location="/tmp/kek"
  target-duration=10 playlist-root=".")", NULL);

g_assert (app->pipeline);

bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);

gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);

caps = gst_caps_new_simple ("video/x-raw-rgb",
  "bpp",G_TYPE_INT,8,
  "depth",G_TYPE_INT,8,
   "width", G_TYPE_INT, 640,
   "height", G_TYPE_INT, 480,
   NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);

g_main_loop_run (app->loop);

GST_DEBUG ("stopping");

gst_element_set_state (app->pipeline, GST_STATE_NULL);

gst_object_unref (bus);
g_main_loop_unref (app->loop);

return 0;
  }


  
  How can I solve this? PLease help!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-05-07 (1667 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: x264 2:0.152.2854+gite9a5903-2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-118-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-12-28 (338 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1906091/+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 1906091] ProcCpuinfoMinimal.txt

[Dmitry]

apport information

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

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

Title:
  libx264-148 libx264-152 conflict segmentation fault SIGSEGV

Status in x264 package in Ubuntu:
  New

Bug description:
  In my app I have segfault due to conflict of libx264-148 vs libx264-152.
  I use gstreamer and libopencv_videoio in my project.
  System is Ubuntu 18.04.5

  The problem is that versions of libx264 get mixed due to implicit
  linking.

  Libraries are linked like this:
  gstreamer -> x264enc -> libx264-152
  libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148

  Both opencv-based code and gstreamer-based code works well if used
  separately.

  At the top of backtrace I see:
  Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
  #0  0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at 
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
  #1  0x7f2927a93f55 in x264_nal_encode () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
  #2  0x7f2927af866c in  () at /usr/lib/x86_64-linux-gnu/libx264.so.148
  #3  0x7f2927b0143b in x264_encoder_headers () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148

  If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in
  both libx264-148 and libx264-152

  
  Here is example code which fails (C++ needed):

  int main (int argc, char *argv[])
  {
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;

gst_init (, );

auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);

GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");

app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();

app->pipeline = gst_parse_launch(R"(filesrc
  location=videoplayback.mp4 ! decodebin ! videoconvert ! x264enc
  byte-stream=true threads=1
  tune=zerolatency bitrate=400 key-
  int-max=50 option-string="force-cfr=1" !
  video/x-h264,profile=baseline,stream-format="byte-stream" !
  h264parse ! mpegtsmux ! hlssink
  location="/tmp/data%06d.ts" max-files=100
  playlist-length=10 playlist-location="/tmp/kek"
  target-duration=10 playlist-root=".")", NULL);

g_assert (app->pipeline);

bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);

gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);

caps = gst_caps_new_simple ("video/x-raw-rgb",
  "bpp",G_TYPE_INT,8,
  "depth",G_TYPE_INT,8,
   "width", G_TYPE_INT, 640,
   "height", G_TYPE_INT, 480,
   NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);

g_main_loop_run (app->loop);

GST_DEBUG ("stopping");

gst_element_set_state (app->pipeline, GST_STATE_NULL);

gst_object_unref (bus);
g_main_loop_unref (app->loop);

return 0;
  }


  
  How can I solve this? PLease help!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-05-07 (1667 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: x264 2:0.152.2854+gite9a5903-2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-118-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-12-28 (338 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1906091/+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 1906091] Re: libx264-148 libx264-152 conflict segmentation fault SIGSEGV

[Dmitry]

apport information

** Tags added: apport-collected bionic third-party-packages

** Description changed:

  In my app I have segfault due to conflict of libx264-148 vs libx264-152.
  I use gstreamer and libopencv_videoio in my project.
  System is Ubuntu 18.04.5
  
  The problem is that versions of libx264 get mixed due to implicit
  linking.
  
  Libraries are linked like this:
  gstreamer -> x264enc -> libx264-152
  libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
  
  Both opencv-based code and gstreamer-based code works well if used
  separately.
  
  At the top of backtrace I see:
  Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
  #0  0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at 
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
  #1  0x7f2927a93f55 in x264_nal_encode () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
  #2  0x7f2927af866c in  () at /usr/lib/x86_64-linux-gnu/libx264.so.148
  #3  0x7f2927b0143b in x264_encoder_headers () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148
  
  If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in both
  libx264-148 and libx264-152
  
  
  Here is example code which fails (C++ needed):
  
  int main (int argc, char *argv[])
  {
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;
  
gst_init (, );

auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);
  
GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");
  
app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();
  
app->pipeline = gst_parse_launch(R"(filesrc location=videoplayback.mp4
  ! decodebin ! videoconvert ! x264enc byte-stream=true
  threads=1 tune=zerolatency
  bitrate=400 key-int-max=50 option-
  string="force-cfr=1" ! video/x-h264,profile=baseline,stream-
  format="byte-stream" ! h264parse ! mpegtsmux !
  hlssink location="/tmp/data%06d.ts" max-
  files=100 playlist-length=10 playlist-
  location="/tmp/kek" target-duration=10
  playlist-root=".")", NULL);
  
g_assert (app->pipeline);
  
bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);
  
gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);
  
caps = gst_caps_new_simple ("video/x-raw-rgb",
  "bpp",G_TYPE_INT,8,
  "depth",G_TYPE_INT,8,
   "width", G_TYPE_INT, 640,
   "height", G_TYPE_INT, 480,
   NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);

g_main_loop_run (app->loop);
  
GST_DEBUG ("stopping");
  
gst_element_set_state (app->pipeline, GST_STATE_NULL);

gst_object_unref (bus);
g_main_loop_unref (app->loop);
  
return 0;
  }
  
  
  
  How can I solve this? PLease help!
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.18
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2016-05-07 (1667 days ago)
+ InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: x264 2:0.152.2854+gite9a5903-2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
+ Tags: bionic third-party-packages
+ Uname: Linux 4.15.0-118-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2019-12-28 (338 days ago)
+ UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  libx264-148 libx264-152 conflict segmentation fault SIGSEGV

Status in x264 package in Ubuntu:
  New

Bug description:
  In my app I have segfault due to conflict of libx264-148 vs libx264-152.
  I use gstreamer and libopencv_videoio in my project.
  System is Ubuntu 18.04.5

  The problem is that versions of libx264 get mixed due to implicit
  linking.

  Libraries are linked like this:
  gstreamer -> x264enc -> libx264-152
  libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148

  Both opencv-based code and gstreamer-based code works well if used
  separately.

  At the top of backtrace I see:
  Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
  #0  0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at 
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
  #1  0x7f2927a93f55 in x264_nal_encode () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
  #2  0x7f2927af866c in  () at 

[Touch-packages] [Bug 1906091] [NEW] libx264-148 libx264-152 conflict segmentation fault SIGSEGV

[Dmitry]

Public bug reported:

In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5

The problem is that versions of libx264 get mixed due to implicit
linking.

Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148

Both opencv-based code and gstreamer-based code works well if used
separately.

At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0  0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at 
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1  0x7f2927a93f55 in x264_nal_encode () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2  0x7f2927af866c in  () at /usr/lib/x86_64-linux-gnu/libx264.so.148
#3  0x7f2927b0143b in x264_encoder_headers () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148

If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in both
libx264-148 and libx264-152


Here is example code which fails (C++ needed):

int main (int argc, char *argv[])
{
  App *app = _app;
  GError *error = NULL;
  GstBus *bus;
  GstCaps *caps;

  gst_init (, );
  
  auto cap = cv::VideoCapture("videoplayback.mp4");
  cv::Mat f;
  cap.read(f);
  cv::imshow("f", f);

  GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
  "appsrc pipeline example");

  app->loop = g_main_loop_new (NULL, TRUE);
  app->timer = g_timer_new();

  app->pipeline = gst_parse_launch(R"(filesrc location=videoplayback.mp4
! decodebin ! videoconvert ! x264enc byte-stream=true
threads=1 tune=zerolatency
bitrate=400 key-int-max=50 option-
string="force-cfr=1" ! video/x-h264,profile=baseline,stream-
format="byte-stream" ! h264parse ! mpegtsmux !
hlssink location="/tmp/data%06d.ts" max-
files=100 playlist-length=10 playlist-
location="/tmp/kek" target-duration=10
playlist-root=".")", NULL);

  g_assert (app->pipeline);

  bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
  g_assert(bus);

  gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);

  caps = gst_caps_new_simple ("video/x-raw-rgb",
"bpp",G_TYPE_INT,8,
"depth",G_TYPE_INT,8,
 "width", G_TYPE_INT, 640,
 "height", G_TYPE_INT, 480,
 NULL);
  gst_element_set_state (app->pipeline, GST_STATE_PLAYING);
  
  g_main_loop_run (app->loop);

  GST_DEBUG ("stopping");

  gst_element_set_state (app->pipeline, GST_STATE_NULL);
  
  gst_object_unref (bus);
  g_main_loop_unref (app->loop);

  return 0;
}


How can I solve this? PLease help!

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


** Tags: gst gstreamer h264 libx264 opencv

** Summary changed:

- libx264-148 libx264-152 conflict segmentation failt SIGSEGV
+ libx264-148 libx264-152 conflict segmentation fault SIGSEGV

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

Title:
  libx264-148 libx264-152 conflict segmentation fault SIGSEGV

Status in x264 package in Ubuntu:
  New

Bug description:
  In my app I have segfault due to conflict of libx264-148 vs libx264-152.
  I use gstreamer and libopencv_videoio in my project.
  System is Ubuntu 18.04.5

  The problem is that versions of libx264 get mixed due to implicit
  linking.

  Libraries are linked like this:
  gstreamer -> x264enc -> libx264-152
  libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148

  Both opencv-based code and gstreamer-based code works well if used
  separately.

  At the top of backtrace I see:
  Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
  #0  0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at 
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
  #1  0x7f2927a93f55 in x264_nal_encode () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
  #2  0x7f2927af866c in  () at /usr/lib/x86_64-linux-gnu/libx264.so.148
  #3  0x7f2927b0143b in x264_encoder_headers () at 
/usr/lib/x86_64-linux-gnu/libx264.so.148

  If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in
  both libx264-148 and libx264-152

  
  Here is example code which fails (C++ needed):

  int main (int argc, char *argv[])
  {
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;

gst_init (, );

auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);

GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");

app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();

app->pipeline = gst_parse_launch(R"(filesrc
  location=videoplayback.mp4 ! decodebin ! 

[Touch-packages] [Bug 1905969] [NEW] Asus Zephyrus G14 microphone not works

[Dmitry Mamchyts]

Public bug reported:

I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA 
GeForce GTX 1650.
I am use 5.9.8-050908-generic kernel from 
(kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/)

dmamchyts@ga401ih:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.10 (Groovy Gorilla)"

I have some problem with notebook microphone.
When I use headphones via 3.5 jack - all works fine.
But without headphones - system doesn't see any microphone device in settings.
I am using KDE


  dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0


Also, I try to report issue into kernel team (they help me to fix issue with 
speakers), you can find some into it: 
https://bugzilla.kernel.org/show_bug.cgi?id=210359

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.1
Uname: Linux 5.9.8-050908-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Nov 27 17:13:59 2020
InstallationDate: Installed on 2020-11-10 (17 days ago)
InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 LANGUAGE=
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.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: 11/05/2020
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GA401IH.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GA401IH
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.ec.firmware.release: 3.13
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.210:bd11/05/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Zephyrus G14
dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug groovy

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

Title:
  Asus Zephyrus G14 microphone not works

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA 
GeForce GTX 1650.
  I am use 5.9.8-050908-generic kernel from 
(kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/)

  dmamchyts@ga401ih:~$ cat /etc/os-release
  NAME="Ubuntu"
  VERSION="20.10 (Groovy Gorilla)"

  I have some problem with notebook microphone.
  When I use headphones via 3.5 jack - all works fine.
  But without headphones - system doesn't see any microphone device in settings.
  I am using KDE

  
dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l
 List of PLAYBACK Hardware Devices 
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 
Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

  
  Also, I try to report issue into kernel team (they help me to fix issue with 
speakers), you can find some into it: 
https://bugzilla.kernel.org/show_bug.cgi?id=210359

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  Uname: Linux 5.9.8-050908-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov 27 17:13:59 2020
  InstallationDate: Installed on 2020-11-10 (17 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.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: 11/05/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GA401IH.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA401IH
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No 

[Touch-packages] [Bug 1896405] Re: Cannot install libglib2.0-dev on ubuntu 20.04.1

[Dmitry Shachnev]

** Package changed: gnome-panel (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  Cannot install  libglib2.0-dev on ubuntu 20.04.1

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I already tried running `apt update/upgrade`, but it did not make any
  difference.

  Why these versions conflicts are happening?

  1. libglib2.0-bin : Conflicts: libglib2.0-bin:i386 but 2.64.2-1~fakesync1 is 
to be installed
  1. libglib2.0-bin:i386 : Conflicts: libglib2.0-bin but 2.64.3-1~ubuntu20.04.1 
is installed
  1. libglib2.0-dev : Depends: libglib2.0-0 (= 2.64.2-1~fakesync1) but 
2.64.3-1~ubuntu20.04.1 is installed
  1. libglib2.0-0 : Breaks: libglib2.0-0:i386 (!= 2.64.3-1~ubuntu20.04.1) but 
2.64.2-1~fakesync1 is to be installed
  1. libglib2.0-0:i386 : Breaks: libglib2.0-0 (!= 2.64.2-1~fakesync1) but 
2.64.3-1~ubuntu20.04.1 is installed

  ```
  $ sudo aptitude install libglib2.0-dev
  The following NEW packages will be installed:
gcc-10-base:i386{a} libblkid-dev{a} libblkid1:i386{a} libc6:i386{a} 
libcrypt1:i386{a} libelf1:i386{a} libffi-dev{a} libffi7:i386{a} 
libgcc-s1:i386{a} libglib2.0-0:i386{ab} 
libglib2.0-bin:i386{ab} libglib2.0-dev{b} libglib2.0-dev-bin{a} 
libidn2-0:i386{a} libmount-dev{a} libmount1:i386{a} libpcre2-8-0:i386{a} 
libpcre2-dev{a} libpcre2-posix2{a} 
libpcre3:i386{a} libselinux1:i386{a} libselinux1-dev{a} libsepol1-dev{a} 
libunistring2:i386{a} zlib1g:i386{a} 
  0 packages upgraded, 25 newly installed, 0 to remove and 0 not upgraded.

  Need to get 8.701 kB of archives. After unpacking 41,3 MB will be used.
  The following packages have unmet dependencies:
   libglib2.0-bin : Conflicts: libglib2.0-bin:i386 but 2.64.2-1~fakesync1 is to 
be installed
   libglib2.0-bin:i386 : Conflicts: libglib2.0-bin but 2.64.3-1~ubuntu20.04.1 
is installed
   libglib2.0-dev : Depends: libglib2.0-0 (= 2.64.2-1~fakesync1) but 
2.64.3-1~ubuntu20.04.1 is installed
   libglib2.0-0 : Breaks: libglib2.0-0:i386 (!= 2.64.3-1~ubuntu20.04.1) but 
2.64.2-1~fakesync1 is to be installed
   libglib2.0-0:i386 : Breaks: libglib2.0-0 (!= 2.64.2-1~fakesync1) but 
2.64.3-1~ubuntu20.04.1 is installed
  open: 2; closed: 4; defer: 0; conflict: 0

  The following actions will resolve these dependencies:

   Keep the following packages at their current version:
  1) libglib2.0-0:i386 [Not Installed]  
  2) libglib2.0-bin:i386 [Not Installed]
  3) libglib2.0-dev [Not Installed] 

  Accept this solution? [Y/n/q/?] y
  No packages will be installed, upgraded, or removed.
  0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B of archives. After unpacking 0 B will be used.
  ```

  ```
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.1 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.1 LTS"
  VERSION_ID="20.04"
  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;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1896405/+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 1895349] Re: Sync libgweather 3.36.1-1 (main) from Debian unstable (main)

[Dmitry Shachnev]

This bug was fixed in the package libgweather - 3.36.1-1
Sponsored for Amr Ibrahim (amribrahim1987)

---
libgweather (3.36.1-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions. (Closes: #968909)

 -- Simon McVittie   Fri, 28 Aug 2020 23:36:23 +0100

** Changed in: libgweather (Ubuntu)
   Status: New => 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/1895349

Title:
  Sync libgweather 3.36.1-1 (main) from Debian unstable (main)

Status in libgweather package in Ubuntu:
  Fix Released

Bug description:
  Please sync libgweather 3.36.1-1 (main) from Debian unstable (main)

  It's a bug-fix release.

  Changelog entries since current groovy version 3.36.0-1:

  libgweather (3.36.1-1) unstable; urgency=medium

* Team upload
* New upstream release
  - This version works around the unavailability of the NOAA weather
services by using very short-term forecasts as current weather
conditions. (Closes: #968909)

   -- Simon McVittie   Fri, 28 Aug 2020 23:36:23 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1895349/+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 1890170] Re: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2

[Dmitry Shachnev]

** Tags added: regression-update

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

Title:
  ImportError libstdc++.so.6 cannot allocate memory after importing
  PyQt5.Qt PyQt5.QtCore and cv2

Status in mysql-8.0 package in Ubuntu:
  New
Status in opencv package in Ubuntu:
  New
Status in pyqt5 package in Ubuntu:
  New

Bug description:
  I'm using an updated Lubuntu focal. Starting maybe last week (monday July 
27th), if in python3 I do
  from PyQt5 import Qt, QtCore
  import cv2

  I get
  ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in 
static TLS block

  I noticed only now that the reverse (first import cv2, then Qt,
  QtCore) seems to work correctly and displays no errors. I'm afraid I
  might not be able to do the reverse in my real software...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 17:49:20 2020
  InstallationDate: Installed on 2020-07-15 (19 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890170/+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 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)

[Dmitry Shachnev]

The correct metadata here is Breaks, and it is already present, see
https://salsa.debian.org/qt-kde-team/qt/qtbase/commit/78c0aa9db8684a1a.
Apt didn't remove Qt 4 because you had some packages depending on it.

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

Title:
  Unable to upgrade several qt5 packages (libqt5gui5, …)

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable
  to upgrade the packages below.

  The following packages have been kept back:
libboost-date-time-dev libboost-dev libboost-filesystem-dev 
libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 
libqt5sql5
libqt5svg5 libqt5widgets5 libqt5xml5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+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 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)

[Dmitry Shachnev]

That is correct behavior. You had many Qt 4 packages installed, however
Qt 4 was removed from Ubuntu, and it conflicts with the latest version
of Qt 5. So you need to remove Qt 4 in order to upgrade Qt 5.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  Unable to upgrade several qt5 packages (libqt5gui5, …)

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable
  to upgrade the packages below.

  The following packages have been kept back:
libboost-date-time-dev libboost-dev libboost-filesystem-dev 
libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 
libqt5sql5
libqt5svg5 libqt5widgets5 libqt5xml5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+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 1887959] Re: Unable to upgrade several qt5 packages (libqt5gui5, …)

[Dmitry Shachnev]

What happens when you try to "apt install libqt5core5a"?

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

Title:
  Unable to upgrade several qt5 packages (libqt5gui5, …)

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 19.10 (maybe 18.04) to 20.04, I am unable
  to upgrade the packages below.

  The following packages have been kept back:
libboost-date-time-dev libboost-dev libboost-filesystem-dev 
libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5printsupport5 
libqt5sql5
libqt5svg5 libqt5widgets5 libqt5xml5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1887959/+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 1886331] [NEW] Xorg freeze

[Dmitry Kuteynikov]

Public bug reported:

Cannot boot sometimes - black screen with a mouse pointer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul  5 18:47:44 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed
 rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615]
InstallationDate: Installed on 2020-06-05 (29 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP HP Pavilion Laptop 15-cw1xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.34
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8615
dmi.board.vendor: HP
dmi.board.version: 46.23
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.34:bd07/31/2019:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cw1xxx
dmi.product.sku: 6QF12EA#AB7
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

** Attachment added: "dmesg.0"
   https://bugs.launchpad.net/bugs/1886331/+attachment/5389899/+files/dmesg.0

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Cannot boot sometimes - black screen with a mouse pointer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 18:47:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615]
  InstallationDate: Installed on 2020-06-05 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Pavilion Laptop 15-cw1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8615
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  

[Touch-packages] [Bug 1886217] Re: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all

[Dmitry Syomin]

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

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

Title:
  [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front]
  No sound at all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula
  with Supreme FX audio card. No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitrys2051 F pulseaudio
   /dev/snd/controlC1:  dmitrys2051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 21:25:22 2020
  InstallationDate: Installed on 2020-07-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitrys2051 F pulseaudio
   /dev/snd/controlC1:  dmitrys2051 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Maximus Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: Maximus Formula
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886217/+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 1886217] [NEW] [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all

[Dmitry Syomin]

Public bug reported:

Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula
with Supreme FX audio card. No sound.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dmitrys2051 F pulseaudio
 /dev/snd/controlC1:  dmitrys2051 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul  3 21:25:22 2020
InstallationDate: Installed on 2020-07-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dmitrys2051 F pulseaudio
 /dev/snd/controlC1:  dmitrys2051 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1403
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Maximus Formula
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: Maximus Formula
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

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

Title:
  [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front]
  No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula
  with Supreme FX audio card. No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitrys2051 F pulseaudio
   /dev/snd/controlC1:  dmitrys2051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 21:25:22 2020
  InstallationDate: Installed on 2020-07-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitrys2051 F pulseaudio
   /dev/snd/controlC1:  dmitrys2051 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Maximus Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: Maximus Formula
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1878233] Re: Unable to locate package/Headers missing

[Dmitry Shachnev]

It is too late to include any warning for Ubuntu 20.04. Maybe I could
add it to the package description if there were other important bugs to
fix in a stable release update, but there are no such bugs yet.

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

Title:
  Unable to locate package/Headers missing

Status in qt3d-opensource-src package in Ubuntu:
  Fix Released
Status in qt3d-opensource-src source package in Focal:
  Won't Fix

Bug description:
  Hi,

  I am a scientific software developper and I'm trying to use Qt3D on Ubuntu 
20.04LTS.
  I am not used to filing bugs here, sorry if its not following the standards, 
any comments on this will also be appreciated.

  Here is a list of the packages I installed prior to this bug.
  sudo apt install qt3d5-dev
  sudo apt install qt3d5-dev-tools
  sudo apt install qt3d-assimpsceneimport-plugin
  sudo apt install qt3d-defaultgeometryloader-plugin
  sudo apt install qt3d-gltfsceneio-plugin
  sudo apt install qt3d-scene2d-plugin
  sudo apt install qml-module-qt3d

  I also ran the command line:
  sudo strip --remove-section=.note.ABI-tag 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

  as per my computer science colleague request

  But I am having errors left and right concerning the headers, as much
  as I actually have to include in my CMakleLists.txt those lines (I
  started to debug from Windows to Linux since our scientific build
  machine uses this target):

  #- *target*
  # Note: 3D Disabled on build machine because of 3D in QT
  if( ${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
add_subdirectory(*target*)
set_target_properties(*target* PROPERTIES FOLDER "apps/*target*")
#Tell CMake to produce a visual studio Qt Project for integration with Qt 
Vs Tools
set_target_properties(*target* PROPERTIES VS_GLOBAL_KEYWORD Qt4VSv1.0)
  else
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DCore")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DRender")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DExtras") ->this 
one useless
  endif()

  as you can see:
  /usr/include/x86_64-linux-gnu/qt5$ ls
  Qt3DCoreQt3DQuickRender   QtDBusQtNetwork   
QtPositioning   QtQuick   QtSerialPort  QtUiTools   QtWebKit
  Qt3DInput   Qt3DQuickScene2D  QtDesignerQtOpenGL
QtPositioningQuick  QtQuickParticles  QtSql QtWebChannel
QtWebKitWidgets
  Qt3DLogic   Qt3DRenderQtDesignerComponents  QtOpenGLExtensions  
QtPrintSupport  QtQuickShapes QtSvg QtWebEngine 
QtWidgets
  Qt3DQuick   QtConcurrent  QtGui QtPacketProtocol
QtQml   QtQuickTest   QtTestQtWebEngineCore QtXml
  Qt3DQuickInput  QtCoreQtHelpQtPlatformHeaders   
QtQmlDebug  QtQuickWidgetsQtUiPluginQtWebEngineWidgets

  And this sub-package that you have does not contain the headers.
  https://packages.ubuntu.com/focal/amd64/libqt53dextras5/filelist

  I think I will also be submitting there I find it weird.
  I will probably download Qt3D sources and temporarily link the headers 
directly there but this is far from optimal for a build machine, as you might 
expect. 

  And finaly, this packages appear when I tab on: apt install qt3d-op...
  but when I run the install it cant find it. This is probably the issue that 
you want to look at, as I will be going to this other package to see why the 
headers are not following.

  Thank you very much and I hope I followed the guidelines here are my infos:
  /usr/include/x86_64-linux-gnu/qt5$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy qt3d-opensource-src 
  N: Unable to locate package qt3d-opensource-src

  /usr/include/x86_64-linux-gnu/qt5$ apt-cache policy libqt53dextras5 
  libqt53dextras5:
Installed: 5.12.8+dfsg-0ubuntu1
Candidate: 5.12.8+dfsg-0ubuntu1
Version table:
   *** 5.12.8+dfsg-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  /usr/include/x86_64-linux-gnu/qt5$ sudo apt install qt3d-opensource-src 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package qt3d-opensource-src

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1878233/+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 1878233] Re: Unable to locate package/Headers missing

[Dmitry Shachnev]

Yes.

The official documentation for Qt 3D Extras (https://doc.qt.io/qt-5
/qt3dextras-module.html) says:

"This module is under development and is subject to change."

We decided not to include headers for this module until it becomes
stable. We made an exception for Qt 5.14 packages because the difference
between 5.14 and the final Qt 5 API/ABI was minimal, and I backported a
patch to make sure the ABI does not change in the future. For Qt 5.12 no
such exception can be made.

I can't say that it makes the Qt 3D package unusable. You can still use
the API that is declared stable. Also you are always free to build your
own version of Qt 3D or create a PPA for it.

** Also affects: qt3d-opensource-src (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: qt3d-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: qt3d-opensource-src (Ubuntu Focal)
   Status: New => Won't Fix

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

Title:
  Unable to locate package/Headers missing

Status in qt3d-opensource-src package in Ubuntu:
  Fix Released
Status in qt3d-opensource-src source package in Focal:
  Won't Fix

Bug description:
  Hi,

  I am a scientific software developper and I'm trying to use Qt3D on Ubuntu 
20.04LTS.
  I am not used to filing bugs here, sorry if its not following the standards, 
any comments on this will also be appreciated.

  Here is a list of the packages I installed prior to this bug.
  sudo apt install qt3d5-dev
  sudo apt install qt3d5-dev-tools
  sudo apt install qt3d-assimpsceneimport-plugin
  sudo apt install qt3d-defaultgeometryloader-plugin
  sudo apt install qt3d-gltfsceneio-plugin
  sudo apt install qt3d-scene2d-plugin
  sudo apt install qml-module-qt3d

  I also ran the command line:
  sudo strip --remove-section=.note.ABI-tag 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

  as per my computer science colleague request

  But I am having errors left and right concerning the headers, as much
  as I actually have to include in my CMakleLists.txt those lines (I
  started to debug from Windows to Linux since our scientific build
  machine uses this target):

  #- *target*
  # Note: 3D Disabled on build machine because of 3D in QT
  if( ${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
add_subdirectory(*target*)
set_target_properties(*target* PROPERTIES FOLDER "apps/*target*")
#Tell CMake to produce a visual studio Qt Project for integration with Qt 
Vs Tools
set_target_properties(*target* PROPERTIES VS_GLOBAL_KEYWORD Qt4VSv1.0)
  else
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DCore")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DRender")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DExtras") ->this 
one useless
  endif()

  as you can see:
  /usr/include/x86_64-linux-gnu/qt5$ ls
  Qt3DCoreQt3DQuickRender   QtDBusQtNetwork   
QtPositioning   QtQuick   QtSerialPort  QtUiTools   QtWebKit
  Qt3DInput   Qt3DQuickScene2D  QtDesignerQtOpenGL
QtPositioningQuick  QtQuickParticles  QtSql QtWebChannel
QtWebKitWidgets
  Qt3DLogic   Qt3DRenderQtDesignerComponents  QtOpenGLExtensions  
QtPrintSupport  QtQuickShapes QtSvg QtWebEngine 
QtWidgets
  Qt3DQuick   QtConcurrent  QtGui QtPacketProtocol
QtQml   QtQuickTest   QtTestQtWebEngineCore QtXml
  Qt3DQuickInput  QtCoreQtHelpQtPlatformHeaders   
QtQmlDebug  QtQuickWidgetsQtUiPluginQtWebEngineWidgets

  And this sub-package that you have does not contain the headers.
  https://packages.ubuntu.com/focal/amd64/libqt53dextras5/filelist

  I think I will also be submitting there I find it weird.
  I will probably download Qt3D sources and temporarily link the headers 
directly there but this is far from optimal for a build machine, as you might 
expect. 

  And finaly, this packages appear when I tab on: apt install qt3d-op...
  but when I run the install it cant find it. This is probably the issue that 
you want to look at, as I will be going to this other package to see why the 
headers are not following.

  Thank you very much and I hope I followed the guidelines here are my infos:
  /usr/include/x86_64-linux-gnu/qt5$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy qt3d-opensource-src 
  N: Unable to locate package qt3d-opensource-src

  /usr/include/x86_64-linux-gnu/qt5$ apt-cache policy libqt53dextras5 
  libqt53dextras5:
Installed: 5.12.8+dfsg-0ubuntu1
Candidate: 5.12.8+dfsg-0ubuntu1
Version table:
   *** 5.12.8+dfsg-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe 

[Touch-packages] [Bug 1882249] Re: Qt3DQuickExtras headers are never packaged

[Dmitry Shachnev]

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

Yes, as you say it is present in Groovy, however we did not include it
before because this module is a technical preview and not declared
stable by upstream.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909306 for
details.

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

** This bug has been marked a duplicate of bug 1878233
   Unable to locate package/Headers missing

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

Title:
  Qt3DQuickExtras headers are never packaged

Status in qt3d-opensource-src package in Ubuntu:
  New

Bug description:
  All the headers for the libraries in the Qt3DQuick packages
  (called libqt53dquick5) are in the qt3d5-dev package,
  except for those for libqt53dquickextras5, which I have not been able
  to find.

  This makes it for example impossible to compile the code from
  qt3d5-examples:

  main.cpp:51:10: fatal error: Qt3DQuickExtras/qt3dquickwindow.h: No such file 
or directory
 51 | #include 
|  ^~~
  compilation terminated.

  The file is missing in xenial, eoan, and focal, and present in
  qt3d5-dev in bionic and groovy:

  
https://packages.ubuntu.com/search?searchon=contents=qt3dquickwindow.h=exactfilename=focal=any

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt53dquickextras5 5.12.8+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-lowlatency 5.4.34
  Uname: Linux 5.4.0-33-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  5 15:45:20 2020
  InstallationDate: Installed on 2020-05-28 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: qt3d-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1882249/+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 1874487] Re: [crash][always] Gwenview crashes when dragging displayed image

[Dmitry Shachnev]

Ubuntu 20.04 LTS has Qt 5.12.8, so I am marking this as fixed.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => 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/1874487

Title:
  [crash][always] Gwenview crashes when dragging displayed image

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  - What I was doing when the application crashed:
  1. open any image in Gwenview
  2. double click on it to make it fullscreen
  3. in fullscreen mode, before the top bar dissapears (!), start dragging the 
image
  - Result:
  Gwenview crashes immediately.

  The crash can be reproduced every time.

  Upstream reports:
  https://bugs.kde.org/show_bug.cgi?id=420467
  https://bugs.kde.org/show_bug.cgi?id=403582

  That issue was resolved upstream in Qt 5.12.5:
  https://bugreports.qt.io/browse/QTBUG-74110

  >Qt Version: 5.12.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1874487/+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 1878233] Re: Unable to locate package/Headers missing

[Dmitry Shachnev]

This is now fixed in Qt 5.14 packages in groovy-proposed. Unfortunately,
this will not be fixed in Ubuntu 20.04 LTS (focal) because it does not
meet the Stable Release Update criteria.

If you want to use this API in focal, I suggest you to use locally built
Qt or create a PPA.

** Changed in: qt3d-opensource-src (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Unable to locate package/Headers missing

Status in qt3d-opensource-src package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  I am a scientific software developper and I'm trying to use Qt3D on Ubuntu 
20.04LTS.
  I am not used to filing bugs here, sorry if its not following the standards, 
any comments on this will also be appreciated.

  Here is a list of the packages I installed prior to this bug.
  sudo apt install qt3d5-dev
  sudo apt install qt3d5-dev-tools
  sudo apt install qt3d-assimpsceneimport-plugin
  sudo apt install qt3d-defaultgeometryloader-plugin
  sudo apt install qt3d-gltfsceneio-plugin
  sudo apt install qt3d-scene2d-plugin
  sudo apt install qml-module-qt3d

  I also ran the command line:
  sudo strip --remove-section=.note.ABI-tag 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

  as per my computer science colleague request

  But I am having errors left and right concerning the headers, as much
  as I actually have to include in my CMakleLists.txt those lines (I
  started to debug from Windows to Linux since our scientific build
  machine uses this target):

  #- *target*
  # Note: 3D Disabled on build machine because of 3D in QT
  if( ${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
add_subdirectory(*target*)
set_target_properties(*target* PROPERTIES FOLDER "apps/*target*")
#Tell CMake to produce a visual studio Qt Project for integration with Qt 
Vs Tools
set_target_properties(*target* PROPERTIES VS_GLOBAL_KEYWORD Qt4VSv1.0)
  else
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DCore")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DRender")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DExtras") ->this 
one useless
  endif()

  as you can see:
  /usr/include/x86_64-linux-gnu/qt5$ ls
  Qt3DCoreQt3DQuickRender   QtDBusQtNetwork   
QtPositioning   QtQuick   QtSerialPort  QtUiTools   QtWebKit
  Qt3DInput   Qt3DQuickScene2D  QtDesignerQtOpenGL
QtPositioningQuick  QtQuickParticles  QtSql QtWebChannel
QtWebKitWidgets
  Qt3DLogic   Qt3DRenderQtDesignerComponents  QtOpenGLExtensions  
QtPrintSupport  QtQuickShapes QtSvg QtWebEngine 
QtWidgets
  Qt3DQuick   QtConcurrent  QtGui QtPacketProtocol
QtQml   QtQuickTest   QtTestQtWebEngineCore QtXml
  Qt3DQuickInput  QtCoreQtHelpQtPlatformHeaders   
QtQmlDebug  QtQuickWidgetsQtUiPluginQtWebEngineWidgets

  And this sub-package that you have does not contain the headers.
  https://packages.ubuntu.com/focal/amd64/libqt53dextras5/filelist

  I think I will also be submitting there I find it weird.
  I will probably download Qt3D sources and temporarily link the headers 
directly there but this is far from optimal for a build machine, as you might 
expect. 

  And finaly, this packages appear when I tab on: apt install qt3d-op...
  but when I run the install it cant find it. This is probably the issue that 
you want to look at, as I will be going to this other package to see why the 
headers are not following.

  Thank you very much and I hope I followed the guidelines here are my infos:
  /usr/include/x86_64-linux-gnu/qt5$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy qt3d-opensource-src 
  N: Unable to locate package qt3d-opensource-src

  /usr/include/x86_64-linux-gnu/qt5$ apt-cache policy libqt53dextras5 
  libqt53dextras5:
Installed: 5.12.8+dfsg-0ubuntu1
Candidate: 5.12.8+dfsg-0ubuntu1
Version table:
   *** 5.12.8+dfsg-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  /usr/include/x86_64-linux-gnu/qt5$ sudo apt install qt3d-opensource-src 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package qt3d-opensource-src

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1878233/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

[Dmitry]

Asus Zenbook UX533FTC, Ubuntu 20.04 fresh install, dual boot with
Windows 10. Same was on Ubuntu 19.10 (dualboot). I already live half a
year without sound on my laptop. Can uninstalling Windows to single-boot
Ubuntu can help?

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  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.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1875317] Re: Unable to launch the application by its desktop icon copied from Applications menu

[Dmitry Shachnev]

** No longer affects: ubuntu-meta (Ubuntu)

** No longer affects: gnome-panel (Ubuntu)

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

Title:
  Unable to launch the application by its desktop icon copied from
  Applications menu

Status in gnome-flashback package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install GNOME FlashBack, login to it
  2. Open Applications menu
  3. Drag some icon from Applications menu to the desktop
  4.1. Do mouse double click on just copied icon
  4.2. Make icon executable
  4.3. Do mouse double click on just copied icon again

  Expected results:
  * user is able to run application by clicking on its desktop-file

  Actual results:
  * user is unable to run application by clicking on its desktop-file, the text 
editor is opened instead

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  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
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Apr 27 12:16:04 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1875317/+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 1869765] Re: Problems dealing with Java Script promise in HTML

[Dmitry Shachnev]

** Changed in: qtwebkit-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  Problems dealing with Java Script promise in HTML

Status in qtwebkit-opensource-src package in Ubuntu:
  Invalid

Bug description:
  We're using the GlobalProtect UI Client in Ubuntu. This uses
  libqt5webkit5 to provide allow login with an external SAML single sign
  on provider. This works with several identity providers (okta,
  jumpcloud). However, it does not work with Azure.

  Issue ID 9415 - https://docs.paloaltonetworks.com/globalprotect/5-1
  /globalprotect-app-release-notes/gp-app-release-information/known-
  issues-related-to-gp-app

  The problem seems to be that the Azure AD HTML response has a java
  promise in it and this seems to be problematic in versions of
  libqt5webkit5 >= 5.212.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1869765/+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 1869765] Re: Problems dealing with Java Script promise in HTML

[Dmitry Shachnev]

Will you mind if I close this bug then?

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

Title:
  Problems dealing with Java Script promise in HTML

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  We're using the GlobalProtect UI Client in Ubuntu. This uses
  libqt5webkit5 to provide allow login with an external SAML single sign
  on provider. This works with several identity providers (okta,
  jumpcloud). However, it does not work with Azure.

  Issue ID 9415 - https://docs.paloaltonetworks.com/globalprotect/5-1
  /globalprotect-app-release-notes/gp-app-release-information/known-
  issues-related-to-gp-app

  The problem seems to be that the Azure AD HTML response has a java
  promise in it and this seems to be problematic in versions of
  libqt5webkit5 >= 5.212.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1869765/+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 1869765] Re: Problems dealing with Java Script promise in HTML

[Dmitry Shachnev]

Hi! WebKit is a complicated codebase, so I don’t think I can help you
here. You may get some luck if you report this on
https://github.com/qtwebkit/qtwebkit/issues.

Though, 5.212 series is based on a very old WebKit version, not sure if
the author wants to fix any bugs there (he usually recommends trying
qtwebkit-dev-wip branch but it's too unstable for packaging into
Ubuntu).

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

Title:
  Problems dealing with Java Script promise in HTML

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  We're using the GlobalProtect UI Client in Ubuntu. This uses
  libqt5webkit5 to provide allow login with an external SAML single sign
  on provider. This works with several identity providers (okta,
  jumpcloud). However, it does not work with Azure.

  Issue ID 9415 - https://docs.paloaltonetworks.com/globalprotect/5-1
  /globalprotect-app-release-notes/gp-app-release-information/known-
  issues-related-to-gp-app

  The problem seems to be that the Azure AD HTML response has a java
  promise in it and this seems to be problematic in versions of
  libqt5webkit5 >= 5.212.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1869765/+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 1866571] Re: Sync acl 2.2.53-6 (main) from Debian unstable (main)

[Dmitry Shachnev]

This bug was fixed in the package acl - 2.2.53-6
Sponsored for Logan Rosen (logan)

---
acl (2.2.53-6) unstable; urgency=medium

  * Redirect stderr to stdout globally in autopkgtests instead of doing
that per command.
  * Enable set -x and -u in autopkgtests.
  * Add support for cross-compilation to autopkgtests. Closes: #947048
  * Update upstream email address. Closes: #949688
  * Fix usage of uninitialized variable in getfacl. Closes: #612599
Thanks to Vasily Gurevich .
  * Switch to Standards-Version 4.5.0 (no changes needed).

 -- Guillem Jover   Sun, 01 Mar 2020 02:06:51 +0100

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

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

Title:
  Sync acl 2.2.53-6 (main) from Debian unstable (main)

Status in acl package in Ubuntu:
  Fix Released

Bug description:
  Please sync acl 2.2.53-6 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Make autopkgtests cross-test-friendly.
  This patch was pulled into Debian.

  Changelog entries since current focal version 2.2.53-5ubuntu1:

  acl (2.2.53-6) unstable; urgency=medium

* Redirect stderr to stdout globally in autopkgtests instead of doing
  that per command.
* Enable set -x and -u in autopkgtests.
* Add support for cross-compilation to autopkgtests. Closes: #947048
* Update upstream email address. Closes: #949688
* Fix usage of uninitialized variable in getfacl. Closes: #612599
  Thanks to Vasily Gurevich .
* Switch to Standards-Version 4.5.0 (no changes needed).

   -- Guillem Jover   Sun, 01 Mar 2020 02:06:51
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acl/+bug/1866571/+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 1866570] Re: Sync alsa-lib 1.2.2-2.1 (main) from Debian unstable (main)

[Dmitry Shachnev]

This bug was fixed in the package alsa-lib - 1.2.2-2.1
Sponsored for Logan Rosen (logan)

---
alsa-lib (1.2.2-2.1) unstable; urgency=medium

  [ Matthias Klose ]
  * Non-maintainer upload.
  
  [ Sebastien Bacher ]
  * debian/patches/python3.8.diff:
- fix the build with python 3.8

 -- Matthias Klose   Sat, 07 Mar 2020 19:21:22 +0100

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

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

Title:
  Sync alsa-lib 1.2.2-2.1 (main) from Debian unstable (main)

Status in alsa-lib package in Ubuntu:
  Fix Released

Bug description:
  Please sync alsa-lib 1.2.2-2.1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Resynchronize with Debian
* debian/patches/python3.8.diff:
  - fix the build with python 3.8
  The Python 3.8 patch was pulled into Debian.

  Changelog entries since current focal version 1.2.2-2ubuntu1:

  alsa-lib (1.2.2-2.1) unstable; urgency=medium

[ Matthias Klose ]
* Non-maintainer upload.

[ Sebastien Bacher ]
* debian/patches/python3.8.diff:
  - fix the build with python 3.8

   -- Matthias Klose   Sat, 07 Mar 2020 19:21:22 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1866570/+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 1848784] Re: Crash in Qt 5.12.2

[Dmitry Shachnev]

Fixed in eoan by https://launchpad.net/ubuntu/+source/qtbase-opensource-
src/5.12.4+dfsg-4ubuntu1.1.

disco has reached end of life on 2020-01-18, so this won't be fixed
there.

** Changed in: qtbase-opensource-src (Ubuntu Eoan)
   Status: New => Fix Released

** Changed in: qtbase-opensource-src (Ubuntu Disco)
   Status: New => Won't Fix

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Disco:
  Won't Fix
Status in qtbase-opensource-src source package in Eoan:
  Fix Released

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme

[Dmitry Shachnev]

In Focal this is now fixed in yaru-theme 20.04.1.

** No longer affects: qtbase-opensource-src (Ubuntu)

** Also affects: yaru-theme (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => 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/1853768

Title:
  Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show
  them as normal document icon under Yaru theme

Status in Yaru Theme:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Eoan:
  New

Bug description:
  Qt apps, like kid3-qt, which uses these legacy icons:

  document-open.png
  document-open-recent.png
  document-save.png
  document-save-as.png
  document-revert.png
  document-import.png
  document-export.png

  The icons are all shown as the same normal document icon under Yaru.

  Qt apps only have a problem with legacy icons starting with
  "document-*" and all other legacy icons are inherited from Humanity
  under Yaru.

  Is there a general solution to force Qt apps to choose the closest
  icon name from Yaru or Humanity?

  Should this bug be issued against upstream Qt?

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1853768/+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 1862344] [NEW] Please switch from python-windowmocker to python3-windowmocker

[Dmitry Shachnev]

Public bug reported:

The dependency of python3-autopilot-tests should be updated from python-
windowmocker to python3-windowmocker.

In the code, window-mocker should be probably replaced with window-
mocker3, as python3-windowmocker ships /usr/bin/window-mocker3.

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

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

Title:
  Please switch from python-windowmocker to python3-windowmocker

Status in autopilot package in Ubuntu:
  New

Bug description:
  The dependency of python3-autopilot-tests should be updated from
  python-windowmocker to python3-windowmocker.

  In the code, window-mocker should be probably replaced with window-
  mocker3, as python3-windowmocker ships /usr/bin/window-mocker3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1862344/+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 1858141] Re: "Advanced" tab is missing from Print dialog in Qt5 applications

[Dmitry Shachnev]

Thank you for filing this bug and adding the required SRU information.
But I have to reject it:

Actually, that patch is just the tip of the iceberg.

It does not apply cleanly unless you backport many other patches. If you
look at OpenSUSE, they have added 11 patches related to printing dialog
and also 17 other patches related to printing:

https://build.opensuse.org/request/show/569841
https://build.opensuse.org/package/show/KDE:Qt:5.9/libqt5-qtbase

Some of these patches change private API, so they require rebuild of
packages relying on it. Unfortunately, this does not meet our SRU
criteria.

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

** Changed in: qtbase-opensource-src (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  "Advanced" tab is missing from Print dialog in Qt5 applications

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Won't Fix

Bug description:
  Please backport Qt patch 213391 to qtbase-opensource-src in Bionic:
  https://codereview.qt-project.org/#/c/213391/

  
  [Impact]
  On Kubuntu 18.04 (bionic), any applications using Qt5 are unable to fully 
configure printers from within the "Print..." dialog because the "Advanced" tab 
is no longer present.  Settings shown here will differ by printer, but this 
includes important settings such as paper type (plain, glossy, photo, etc.), 
print resolution, and ink usage strategies.  Gwenview and Okular are notable 
affected applications.  GTK applications are unaffected and do show the 
advanced options provided by the printer driver.  As a workaround for Qt5 
applications, the printer *default* advanced settings can be successfully 
accessed and changed from within the "Printers" section of Plasma's "System 
Settings", but this is cumbersome, unintuitive, and is not the intended way of 
interacting with these settings on a per-print-job basis.

  
  [Additional Information]
  This was identified as a bug in Qt5 upstream:
  https://bugreports.qt.io/browse/QTBUG-54464

  The bug was fixed upstream in Qt 5.11, but Bionic is stable on Qt 5.9.
  I'd like to request that this patch be backported to Bionic, please.

  
  [Regression Potential]
  OpenSUSE has already backported this patch to their Qt 5.9 stable branch, so 
there is precedent for this patch being low risk:
  
https://build.opensuse.org/package/view_file/KDE:Qt:5.9/libqt5-qtbase/0010-Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=1

  
  Software Versions:

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

  $ apt-cache policy libqt5printsupport5
  libqt5printsupport5:
Installed: 5.9.5+dfsg-0ubuntu2.4
Candidate: 5.9.5+dfsg-0ubuntu2.4
Version table:
   *** 5.9.5+dfsg-0ubuntu2.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.9.5+dfsg-0ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   5.9.5+dfsg-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1858141/+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 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme

[Dmitry Shachnev]

When an icon is missing (e.g. document-open), Qt first falls back to
splitting the name by dashes and taking the first part of it (document).
Only then it falls back to parent icon themes (Yaru → Humanity). So for
all document-* icons it uses document.png from MimeTypes context.

Doing it vice versa would fix the bug. However, the specification
explicitly tells us to behave as Qt currently does:
https://specifications.freedesktop.org/icon-naming-spec/icon-naming-
spec-latest.html#guidelines

> if the more specific item does not exist in the current theme, and
does exist in a parent theme, the generic icon from the current theme is
preferred, in order to keep consistent style.

Another potential fix would be ignoring the MimeTypes context. The
specification says that fallback happens “for all contexts other than
MimeTypes”. However currently Qt’s icon loader does not take contexts
into account at all. So fixing it in Qt would be difficult.

I have just pinged the Yaru theme maintainer, let’s hope the fix from
Yaru will land in Ubuntu soon.

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

Title:
  Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show
  them as normal document icon under Yaru theme

Status in Yaru Theme:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  Qt apps, like kid3-qt, which uses these legacy icons:

  document-open.png
  document-open-recent.png
  document-save.png
  document-save-as.png
  document-revert.png
  document-import.png
  document-export.png

  The icons are all shown as the same normal document icon under Yaru.

  Qt apps only have a problem with legacy icons starting with
  "document-*" and all other legacy icons are inherited from Humanity
  under Yaru.

  Is there a general solution to force Qt apps to choose the closest
  icon name from Yaru or Humanity?

  Should this bug be issued against upstream Qt?

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1853768/+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 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

I have retried the tests, and now the only failing one is pinentry. But
it has passed only once, and that was by accident. Please ignore it:

http://autopkgtest.ubuntu.com/packages/p/pinentry/bionic/amd64

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  [Impact]
  In Qt5 applications, print dialog (Printer Properties) always defaults to A4 
paper size, even when Letter is set as a default in all system and KDE 
preferences. After changing manually, Letter-size pages print correctly, but 
the setting does not stick.

  This impacts users of Qt applications who print things and live in
  countries where ISO 216 is not default, most notably the United
  States.

  [Test Case]
  1) Use system settings (KDE preferences, gnome-control-center or 
system-config-printer) to set the printer size to Letter.
  2) Open any Qt application (e.g. KWrite or Falkon).
  3) Open a print dialog.
  4) Behavior expected: Print dialog would default to Letter paper size and not 
A4.

  [Regression Potential]
  Two possibilities for regressions that I can imagine are:
  - crashes because something is not defined;
  - wrong default paper size (A4 wanted but CUPS returns something else).

  [Additional Information]
  The issue also affects other print settings, e.g. margins, though the 
aforementioned patch does not deal with these. A similar issue regarding the 
duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, 
but other print settings continue to cause problems.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1848784] Re: Crash in Qt 5.12.2

[Dmitry Shachnev]

Focal now has Qt 5.12.5 where this is fixed.

** Also affects: qtbase-opensource-src (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu Bionic)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Changed in: qtbase-opensource-src (Ubuntu Disco)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Changed in: qtbase-opensource-src (Ubuntu Eoan)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => 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/1848784

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New
Status in qtbase-opensource-src source package in Disco:
  New
Status in qtbase-opensource-src source package in Eoan:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

Thanks for the quick feedback!

I have just uploaded this fix to Ubuntu, it is waiting in the review
queue. Per the procedure, when it is accepted you will be asked to test
the fix again, this time installing the packages from bionic-proposed
repository.

Also updated the bug description to contain the needed fields for stable
release procedure.

** Description changed:

  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677
  
- In Qt5 applications, print dialog (Printer Properties) always defaults
- to A4 paper size, even when Letter is set as a default in all system and
- KDE preferences. After changing manually, Letter-size pages print
- correctly, but the setting does not stick. The issue also affects other
- print settings, e.g. margins, though the aforementioned patch does not
- deal with these. A similar issue regarding the duplex setting was
- reported as Launchpad bug 1776173, and subsequently fixed, but other
- print settings continue to cause problems.
+ [Impact]
+ In Qt5 applications, print dialog (Printer Properties) always defaults to A4 
paper size, even when Letter is set as a default in all system and KDE 
preferences. After changing manually, Letter-size pages print correctly, but 
the setting does not stick.
  
- Behavior expected: Print dialog would default to Letter paper size,
- which is set in all available system and KDE preferences, and that was
- selected for previous prints.
+ This impacts users of Qt applications who print things and live in
+ countries where ISO 216 is not default, most notably the United States.
  
- Behavior observed: Print dialog always defaults to A4, and page size
- needs to be changed manually before every print.
+ [Test Case]
+ 1) Use system settings (KDE preferences, gnome-control-center or 
system-config-printer) to set the printer size to Letter.
+ 2) Open any Qt application (e.g. KWrite or Falkon).
+ 3) Open a print dialog.
+ 4) Behavior expected: Print dialog would default to Letter paper size and not 
A4.
+ 
+ [Regression Potential]
+ Two possibilities for regressions that I can imagine are:
+ - crashes because something is not defined;
+ - wrong default paper size (A4 wanted but CUPS returns something else).
+ 
+ [Additional Information]
+ The issue also affects other print settings, e.g. margins, though the 
aforementioned patch does not deal with these. A similar issue regarding the 
duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, 
but other print settings continue to cause problems.
  
  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  [Impact]
  In Qt5 applications, print dialog (Printer Properties) always defaults to A4 
paper size, even when Letter is set as a default in all system and KDE 
preferences. After changing manually, Letter-size pages print correctly, but 
the setting does not stick.

  This impacts users of Qt applications who print things and live in
  countries where ISO 216 is not default, most notably the United
  States.

  [Test Case]
  1) Use system settings (KDE preferences, gnome-control-center or 
system-config-printer) to set the printer size to Letter.
  2) Open any Qt application (e.g. KWrite or Falkon).
  3) Open a print dialog.
  4) Behavior expected: Print dialog would default to Letter paper size and not 
A4.

  [Regression Potential]
  Two possibilities for regressions that I can imagine are:
  - crashes because something is not defined;
  - wrong default paper size (A4 wanted but CUPS returns something else).

  [Additional Information]
  The issue also affects other print settings, e.g. margins, though the 
aforementioned patch does not deal with these. A similar issue regarding the 
duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, 
but other print settings continue to cause problems.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1848784] Re: Crash in Qt 5.12.2

[Dmitry Shachnev]

** Information type changed from Public to Public Security

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

Can you please test the packages in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3833?

The patch did not apply to 5.9 branch so I had to make some changes to
it.

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  In Qt5 applications, print dialog (Printer Properties) always defaults
  to A4 paper size, even when Letter is set as a default in all system
  and KDE preferences. After changing manually, Letter-size pages print
  correctly, but the setting does not stick. The issue also affects
  other print settings, e.g. margins, though the aforementioned patch
  does not deal with these. A similar issue regarding the duplex setting
  was reported as Launchpad bug 1776173, and subsequently fixed, but
  other print settings continue to cause problems.

  Behavior expected: Print dialog would default to Letter paper size,
  which is set in all available system and KDE preferences, and that was
  selected for previous prints.

  Behavior observed: Print dialog always defaults to A4, and page size
  needs to be changed manually before every print.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1848784] [NEW] Crash in Qt 5.12.2

[Dmitry Shachnev]

Public bug reported:

Originally reported by Robert Loehning in
:

Every application based on Qt will crash when opening a crafted plain
text file. Could you please add the patch below to your builds to fix
this?

https://codereview.qt-project.org/c/qt/qtbase/+/271889

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

The fix is included in Qt 5.11, so I am marking it as affecting only
Bionic.

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => 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/1846821

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  In Qt5 applications, print dialog (Printer Properties) always defaults
  to A4 paper size, even when Letter is set as a default in all system
  and KDE preferences. After changing manually, Letter-size pages print
  correctly, but the setting does not stick. The issue also affects
  other print settings, e.g. margins, though the aforementioned patch
  does not deal with these. A similar issue regarding the duplex setting
  was reported as Launchpad bug 1776173, and subsequently fixed, but
  other print settings continue to cause problems.

  Behavior expected: Print dialog would default to Letter paper size,
  which is set in all available system and KDE preferences, and that was
  selected for previous prints.

  Behavior observed: Print dialog always defaults to A4, and page size
  needs to be changed manually before every print.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf

[Dmitry Lapshin]

Any progress here? systemd-resolved has plus that it's integrated with
DNS options from systemd-networkd, but for end user it has many issues,
especially related to DNSSEC.

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

Title:
  systemd-resolved can't resolve at all, need to add nameservers to
  resolve.conf

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 (upgraded from 17.10) on a machine with both
  ethernet and wifi interfaces. When I boot, my ethernet connection
  enp0s31f6 is brought up by Network Manager and given three nameserver
  addresses via DHCP, 10.1.13.10, 10.1.141.10, 10.1.13.36. Running nmcli
  shows the three nameservers under "DNS configuration". Running
  "systemd-resolve --status" shows them under a "Link 2 (enp0s31f6)"
  section. I can do a "ip route get to X" and ping each one
  successfully. No other connection is active.

  testuser ☼ systemd-resolve --status
  Global
DNS Domain: orgsdomain.net
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 3 (wlp4s0)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  Link 2 (enp0s31f6)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 10.1.13.10
10.1.141.10
10.1.13.36
DNS Domain: orgsdomain.net

  However, when I actually try to resolve a name, even the name of one
  of the nameservers, dig claims that "connection timed out: no servers
  could be reached".

  testuser ☼ dig dcpdc001.orgsdomain.net +nocookie

  ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> dcpdc001.orgsdomain.net +nocookie
  ;; global options: +cmd
  ;; connection timed out; no servers could be reached

  Note that this name should resolve to 10.1.13.10, the first
  nameserver. The "+nocookie" option is there to work around an issue
  with Windows DNS servers. But other than that, the servers themselves
  work fine if I tell dig where to look:

  testuser ☼ dig dcpdc001.orgsdomain.net +nocookie @10.1.13.10

  ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> dcpdc001.orgsdomain.net +nocookie 
@10.1.13.10
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61294
  ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4000
  ;; QUESTION SECTION:
  ;dcpdc001.orgsdomain.net.  IN  A

  ;; ANSWER SECTION:
  dcpdc001.orgsdomain.net.   3600IN  A   10.1.13.10

  ;; Query time: 2 msec
  ;; SERVER: 10.1.13.10#53(10.1.13.10)
  ;; WHEN: Fri Jul 20 10:56:27 AEST 2018
  ;; MSG SIZE  rcvd: 65

  I have configured resolvconf to use dynamic updates. /etc/resolv.conf
  points to /run/resolvconf/resolv.conf. This file contains only (non-
  comments):

  nameserver 127.0.0.53
  search orgsdomain

  If I add "nameserver 10.1.13.10" to this file manually, suddenly dig
  can resolve again (without the @...), and anything else that needs to
  resolve names can do so. Removing the nameserver breaks that again.

  I don't know much about the servers. They're part of a Windows-based
  network, but since I can use them if I edit resolv.conf or give dig
  the address, I don't think they're the issue (except in the sense that
  maybe they require a feature that systemd-resolved doesn't support?).

  I increased the logging level of systemd-resolved to "debug" and
  "journalctl -f -u systemd-resolved" shows this during a failed query:

  Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Got DNS stub UDP query 
packet for id 19836
  Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Looking up RR for 
dcpdc001.orgsdomain.net IN A.
  Jul 

[Touch-packages] [Bug 1833536] Re: QuiteRSS crashes intermittently

[Dmitry Shachnev]

And now I have verified the fix for Disco using the same steps.

** Attachment added: "VirtualBox_Ubuntu 19.04_01_09_2019_15_28_44.png"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+attachment/5286070/+files/VirtualBox_Ubuntu%2019.04_01_09_2019_15_28_44.png

** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco

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

Title:
  QuiteRSS crashes intermittently

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.

  [Test Case]
  1. Open QuiteRSS.
  2. Leave it running for several hours.
  3. It should not crash.

  [Proposed Fix]
  The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db

  [Regression Potential]
  This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.

  [Original Description]
  After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.

  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
  at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
  this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
  #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
  e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
  () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
     from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
  receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
  at kernel/qcoreapplication.cpp:1024
  #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
  receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
  #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
  event_type=event_type@entry=0, data=0x7fff60008e90)
  at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
  receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
  at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
  this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
  #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
  flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
  at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
  at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
  at pthread_create.c:463
  #18 0x719ec88f in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1833536] Re: QuiteRSS crashes intermittently

[Dmitry Shachnev]

So the original reporter does not respond, and we need to somehow verify
the fix to make it reach bionic-updates.

I created a fresh Bionic VM, installed qtbase from -proposed, quiterss
and qbittorrent and left them running for several hours (as you can see
in the attached screenshot).

No crash occurred, so I think we can treat this bug as verified for
bionic.

I will do the same thing for disco a bit later.

** Attachment added: "VirtualBox_Ubuntu 18.04.3 LTS_31_08_2019_15_30_53.png"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+attachment/5285953/+files/VirtualBox_Ubuntu%2018.04.3%20LTS_31_08_2019_15_30_53.png

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  QuiteRSS crashes intermittently

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.

  [Test Case]
  1. Open QuiteRSS.
  2. Leave it running for several hours.
  3. It should not crash.

  [Proposed Fix]
  The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db

  [Regression Potential]
  This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.

  [Original Description]
  After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.

  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
  at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
  this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
  #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
  e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
  () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
     from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
  receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
  at kernel/qcoreapplication.cpp:1024
  #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
  receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
  #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
  event_type=event_type@entry=0, data=0x7fff60008e90)
  at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
  receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
  at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
  this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
  #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
  flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
  at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
  at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
  at pthread_create.c:463
  #18 0x719ec88f in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1834333] Re: Scaling problem with Qt apps

[Dmitry Shachnev]

It is an upstream fix that is not yet released. Note that the bug status
is “In progress”.

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

Title:
  Scaling problem with Qt apps

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Hi
  I have problem with scaling for Qt apps.
  when i open Kolourpaint scaling is too small 
  i have Ubuntu 18.04 and install from snap and apt
  i first report to bugs.kde.org and they tell me to report here 
  https://bugs.kde.org/show_bug.cgi?id=407668

  Kolourpaint its not only app with problem , anydesk , filezilla ,
  pylon viewer ,  dukto , stacer , vmware horizon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1834333/+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 1834333] Re: Scaling problem with Qt apps

[Dmitry Shachnev]

This should be fixed by https://codereview.qt-
project.org/c/qt/qtbase/+/265653, which will be included in Qt 5.12.5.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => In Progress

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

Title:
  Scaling problem with Qt apps

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Hi
  I have problem with scaling for Qt apps.
  when i open Kolourpaint scaling is too small 
  i have Ubuntu 18.04 and install from snap and apt
  i first report to bugs.kde.org and they tell me to report here 
  https://bugs.kde.org/show_bug.cgi?id=407668

  Kolourpaint its not only app with problem , anydesk , filezilla ,
  pylon viewer ,  dukto , stacer , vmware horizon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1834333/+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 1832019] Re: Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in Spyder3 in Bionic

[Dmitry Shachnev]

Thanks for the additional information. Still it is a bug in Spyder, not
in Qt:

1) Cleanlooks and Plastique styles are inheriting from QProxyStyle.
2) So in Spyder’s HTMLDelegate.paint method, options.widget.style() returns a 
QProxyStyle.
3) In QProxyStyle.subElementRect method, the third argument is not optional, so 
should be specified: https://doc.qt.io/qt-5/qproxystyle.html#subElementRect

In C++, if the two-argument call is used, the compiler would ignore
QProxyStyle::subElementRect and fall back to
QCommonStyle::subElementRect. However, in Python there is no concept of
overloading methods so this is not possible.

So Qt and PyQt behave according to their documentation.

Replacing style.subElementRect(QStyle.SE_ItemViewItemText, options) with
style.subElementRect(QStyle.SE_ItemViewItemText, options, None) in
Spyder code seems to help.

With regards to crash when using GTK2, it is a different and known
issue. Qt uses GTK3 platformtheme (i.e. dialogs) by default, and it is
incompatible with GTK2. If you want to use GTK2 then you should export
QT_QPA_PLATFORMTHEME=gtk2. But I recommend against using GTK2 as it is
deprecated.

** Changed in: qtstyleplugins-src (Ubuntu)
   Status: New => Invalid

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

Title:
  Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in
  Spyder3 in Bionic

Status in pyqt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtstyleplugins-src package in Ubuntu:
  Invalid
Status in spyder package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 LTS
  Steps:

  1. Install spyder3 and qt5-style-plugins (sudo apt install spyder3 
qt5-style-plugins)
  2. Run spyder3
  3. Go to Tools → Preferences → General → Appearance
  4. Change the Qt window style to cleanlooks, gtk2 or plastique
  5. Go to Tools → Preferences → Keyboard shortcuts
  6. Error (or crash in case of gtk2)

  Keyboard shortcuts are not accessible.

  Here is the error:

    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
 

[Touch-packages] [Bug 1838891] Re: qt5 applications crash when opening file chooser in gtk desktops

[Dmitry Shachnev]

I just managed to reproduce the crash locally. Just before the crash,
the following lines are printed to stderr:

(AppImageLauncherSettings:27871): Gtk-WARNING **: 21:45:01.935: Could not load 
a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/usr/share/icons/Adwaita/16x16/status/image-missing.png: Fatal error reading 
PNG image file: bad parameters to zlib (gdk-pixbuf-error-quark, 0)

I think most important part here is “bad parameters to zlib”.
AppImageLauncher uses its own static zlib
(lib/AppImageUpdate/lib/zsync2/lib/zlib/libzsync2_libz.a) which is
incompatible with public zlib (/lib/x86_64-linux-gnu/libz.so.1) that GTK
was compiled against.

Recompiling AppImageLauncher with system zlib should help, but I haven’t
found a way to do that. I suggest you to ask AppImageLauncher developer
about that.

Attaching a stacktrace for future reference.

** Attachment added: "stacktrace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1838891/+attachment/5283815/+files/stacktrace.txt

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  qt5 applications crash when opening file chooser in gtk desktops

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Issue is apparently related to qt5-gtk-platformtheme. When you're in a
  non-Qt desktop environment and you open a file selection dialog from a
  Qt app it crashes.

  See also:
  https://bugzilla.redhat.com/show_bug.cgi?id=1392605
  https://bugs.archlinux.org/task/57984
  https://github.com/TheAssassin/AppImageLauncher/issues/218

  In my opinion this is a very serious issue and if newer Qt releases
  have fixed this it should be backported.

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