[Touch-packages] [Bug 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working

2022-10-10 Thread bricobrac
I also have a MAG X570S TOMAHAWK MAX WIFI motherboard and am having the
same problem.

For me, the card number seems to vary whenever I reboot, so I have to
use a command like this

pacmd load-module module-alsa-sink device=hw:`aplay -l | grep "USB
Audio" | head -n 1 | cut -d " " -f 2 | cut -d ":" -f 1`,1

I have to run thie manually and running it automatically doesn't work.
For example, it doesn't work properly in /etc/crontab or /etc/profile.d
because pulse audio isn't loaded in time.

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

Title:
  [USB-Audio - ALC4080] Front panel: Headphone output not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard
  'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio
  chip) controller that has a weird mapping via USB audio (see bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar
  configuration).

  Sound via line-out works fine without any interventions.

  Headphone output however does not, while Ubuntu correctly detects the
  headphones as being plugged in when selected sound is still output via
  line-out, instead of via the front panel headphone jack-out.

  After some debugging I figured the headphones are connected to a seperate 
Alsa device on the same card as the line-out.
  Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working 
audio output that plays just via the headphone out.

  I guess a quirk needs to be written for the configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gijs   2129 F pulseaudio
   /dev/snd/pcmC2D1p:   gijs   2129 F...m pulseaudio
   /dev/snd/controlC0:  gijs   2129 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 09:28:19 2021
  InstallationDate: Installed on 2020-12-06 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
  Symptom_Card: USB Audio - USB Audio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [USB-Audio - USB Audio, playback] Playback problem
  UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.00
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D54
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode

2022-10-10 Thread Muralidharan
Hi All,

Please ignore my comment #5 as only ModemManager and libmbim commits are
needed for FM350 integration.

Thanks and Best Regards,
Murali

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

Title:
  Fibcom FM350-GL not able connect to network with 5G mode

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  Fibcom FM350-GL can support 5G network
  (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu
  22.04, system can only connect to mobile network with 4G mode.


General  | path: /org/freedesktop/ModemManager1/Modem/0
 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e

Hardware | manufacturer: generic
 |model: MBIM [14C3:4D75]
 |firmware revision: 81600..00.29.18.01_GC
 |   C01
 | h/w revision: V1.0.6
 |supported: gsm-umts, lte
 |  current: gsm-umts, lte
 | equipment id: 352750140002001

System   |   device: 
/sys/devices/pci:00/:00:1c.0/:73:00.0
 |  drivers: mtk_t7xx
 |   plugin: generic
 | primary port: wwan0mbim0
 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 
(mbim)

Status   |   unlock retries: sim-pin (3), sim-pin2 (3)
 |state: connected
 |  power state: on
 |  access tech: lte
 |   signal quality: 74% (recent)

Modes|supported: allowed: 3g, 4g; preferred: none
 |  current: allowed: 3g, 4g; preferred: none

IP   |supported: ipv4, ipv6, ipv4v6

3GPP | imei: 352750140002001
 |enabled locks: sim, fixed-dialing
 |  operator id: 46692
 |operator name: Chunghwa Telecom
 | registration: home

3GPP EPS | ue mode of operation: csps-2
 |  initial bearer path: /org/freedesktop/ModemManager1/Bearer/0

SIM  | primary sim path: /org/freedesktop/ModemManager1/SIM/0

Bearer   |paths: /org/freedesktop/ModemManager1/Bearer/1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-15 (26 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: modemmanager 1.18.6-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9
  Tags:  jammy
  Uname: Linux 5.17.0-9012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1992346] Re: Fractional scaling settings lost on VM window resizing or logout

2022-10-10 Thread Daniel van Vugt
I think this was fixed in:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2479

** Summary changed:

- Fractional scaling settings lost on logout
+ Fractional scaling settings lost on VM window resizing or logout

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

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

** Tags added: fixed-in-43.rc fixed-upstream

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Fractional scaling settings lost on VM window resizing or logout

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  I'm running Ubuntu 22.04.1 on VirtualBox latest release for quite some
  time. Recently switched from 2560x1440 to 3840x2160 monitor
  resolution, which forced me to enable 125% fractional scaling. Using
  default wayland server, the scaling will be reset to 100% every time I
  do a logout or change the resolution, e.g. (dis-) connecting the
  external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 10 14:56:52 2022
  DistUpgraded: 2022-08-14 13:03:40,111 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2021-08-22 (413 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f4feeb72-92ed-4dd4-b498-dd6006b2c61c ro quiet splash ipv6.disable=1
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-08-14 (57 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1992346/+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 344814] Re: Synthetic emboldening/italic/italic-bold fails for single-styled fonts

2022-10-10 Thread Bug Watch Updater
** Changed in: firefox
   Importance: Medium => Unknown

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

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

2022-10-10 Thread Daniel Holbert
That sounds like this bug, I think.

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

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

2022-10-10 Thread Laszlo-bialis
Hi!

I've encountered the following issue on Ubuntu 16.04 x32, printing the
following attachment:
https://bug1318845.bmoattachments.org/attachment.cgi?id=8816724 the
print preview looks ok, but when printing the file with a physical
printer or to a .pdf file the fonts from the bold column don't seem to
be bolded anymore (see also "print prev vs pdf.png" attachment), whereas
the fonts from the column header seem to bee bold even after print.

Is the above issue related to this bug or should I file a new one?

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

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

2022-10-10 Thread Laszlo-bialis
Created attachment 9005195
print prev vs pdf.png

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

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

2022-10-10 Thread Daniel Holbert
Murz: Thanks for the report -- but I think it's actually a different
issue from this bug, though.

This bug is about bold text being rendered as non-bold (and only when
printed), whereas it looks like your issue is about bold text being
*completely missing* (based on your first screenshot), which is
different and quite bad.  (Also, it sounds like this bug may be fixed,
per comment 24... not sure)

Could you file a new bug on the PDF rendering issue issue, here:
 
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox=PDF%20Viewer
Thanks!

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

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

2022-10-10 Thread Murz
I have the same problem with displaying Bold fonts in PDF in Firefox 38.0 on 
Ubuntu 14.10, here is screenshots of PDF file (attached):
PDF view on tab: http://i.imgur.com/mptr8fd.png
Print preview: http://i.imgur.com/zr90wox.png

On Windows 8 all looks normally.

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

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

2022-10-10 Thread Murz
On Google Chrome (Chromium) on same Ubuntu Linux system this PDF file
displays normally.

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

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

2022-10-10 Thread Murz
Created attachment 8636477
132782.pdf

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

Title:
  Synthetic emboldening/italic/italic-bold fails for single-styled fonts

Status in Mozilla Firefox:
  Confirmed
Status in The Gimp:
  New
Status in Scribus:
  New
Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Ubuntu 9.10,  firefox 3.5.3 is unable to print bold Chinese sans
  characters.

  Steps to duplicate:
  1. if you set desktop language to Chinese, ttf-wqy-zenhei will be 
automatically installed as the default Sans Serif font, if you use other 
languages, simply install ttf-wqy-zenhei via atp-get first

  2. in firefox, select Edit\Preference\Content\Font & Color, select the
  default font as "sans-serif"

  3. browse any Chinese web page with bold face, for example
  http://forum.ubuntu.org.cn/

  4. print page

  Expected results:
  the emboldened titles shall be printed in bold face

  Actual results:
  both the titles and text are printed with the same weight. English bold 
characters look fine on the print though.
  Bold Chinese characters prints ok with OpenOffice 3.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/344814/+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 1332959] Re: When you press the "print screen" key Firefox shows the full-screen message, making impossible to take screen-shots from videos without this notification

2022-10-10 Thread Bug Watch Updater
** Changed in: firefox
   Importance: Low => Unknown

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

Title:
  When you press the "print screen" key Firefox shows the full-screen
  message, making impossible to take screen-shots from videos without
  this notification

Status in Mozilla Firefox:
  New
Status in Light Display Manager:
  Invalid
Status in Unity:
  Invalid
Status in firefox package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  
  HOW TO REPRODUCE
  

  1. In the Firefox browser, open a video played using an HTML 5 web-player 
(for example: http://youtu.be/wWC_WZ7gd6g)
  2. Click on the full screen button.
  3. Press the "print screen" key.

  
  **
  EXPECTED BEHAVIOUR
  **

  - To have taken an screen-shot of how the screen looked at that
  moment.

  **
  REAL BEHAVIOUR
  **

  - A message telling you went full screen appears in the screen-shot.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 30.0+build1-0ubuntu0.14.04.3
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  es20490446e   1959 F pulseaudio
   /dev/snd/controlC1:  es20490446e   1959 F pulseaudio
   /dev/snd/controlC0:  es20490446e   1959 F pulseaudio
  BuildID: 20140608211622
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Jun 22 15:37:57 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2013-05-21 (397 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static 
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.130  metric 
1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-a226e310-01ec-4d7b-9bf6-29cc52140606
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=30.0/20140608211622 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.2-0ubuntu2
   icedtea-7-plugin  1.5-1ubuntu1
   totem-mozilla 3.10.1-1ubuntu4
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-a226e310-01ec-4d7b-9bf6-29cc52140606
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to trusty on 2014-04-14 (69 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1332959/+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 1283309] Re: bash built-in read timeout (-t) doesn't work

2022-10-10 Thread Charles Evans
Still fails randomly 
@ jammy bash 5.1-6ubuntu1
Read -t 60 failure can often be triggered by changing the system clock 
slightly. It often fails if waiting when ntp runs.

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Ian! D. Allen
I'm not familiar with your SRU process, debdiff, dput, the "General
Requirements" document, the "security policy document", or your upload
process, and I'm not into learning about all that and filling out your
special form and making your special upload when there is no guarantee
that Ubuntu will actually fix the problem.

If all the info you need for your SRU process isn't already in this bug
report (or in the bug report upstream linked above), I don't know what
else to say.  I certainly don't have the experience to answer "Where
problems could occur" in a Ubuntu package management context, other than
to say the obvious "people may have already written scripts that depend
on the buggy behaviour".

You're already running a fixed version of rsync in Kinetic, so at some
level someone at Ubuntu already approved of a much more modern rsync
(3.2.5 was released August 14 2022) -- please use it.

I've documented the bug; someone else found the upstream fix; your
Ubuntu internals of adopting the fix are more reading than I want to do.
I will download the current source and update my own rsync -- I know how
to do that and I know it will solve the problem for me.  I hope Ubuntu
solves the problem for everyone else.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1982583] Comment bridged from LTC Bugzilla

2022-10-10 Thread bugproxy
--- Comment From i...@de.ibm.com 2022-10-10 19:01 EDT---
Thanks! With

https://ppa.launchpadcontent.net/fheimes/lp1990379+lp1982583/ubuntu
kinetic/main s390x zlib1g s390x 1:1.2.11.dfsg-4.1ubuntu2

the following command:

python3 -c 'import zlib; zlib.crc32(b"X"*50)'

begins to work ~2x faster.

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

Title:
  Fix for zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * There were two issues identified in the current
     zlib CRC32 optimization for s390x implementation:

   * 1) s390_crc32_vx() signature mismatch
    which causes a warning

   * 2) '-DS390_CRC32_VX' was not added to SFLAGS
    which results in vectorization being enabled only in the static library.

   * The fixes are quite small and affect each only one line:

   * 1) by using unsigned longs instead of uint32_t in s390_crc32_vx
  declaration

   * 2) by add line 'SFLAGS="$SFLAGS -DS390_CRC32_VX"'

  [ Test Plan ]

   * An affected Ubuntu release ([20.04], 22.04 and 22.10) installed
     on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
     of a small test program (in C) that checks for
     s390_crc32_vx() signature mismatches.

   * The bug reporter has a set of s390x-specific tests that will be
  executed.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The fixes are each limited to one line, hence there are
     not many issues to expect, other than:

   * Typos (e.g. in the flags), mixing of CFLAGS and SFLAGS,

   * in case the changed data type in s390_crc32_vx is causing issues
     inside of s390_crc32_vx or in other parts of the code.

   * Structural and syntactical issues can be identified with a test build
     that was done for all affected Ubuntu releases and for all major archs:
     https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379+lp1982583

  [ Other Info ]

   * This bug (LP#1982583) is solved in combination with LP#1990379,
     so that only one package update is needed.
     However, LP#1990379 also affects Focal, but this bug only Jammy and 
Kinetic.

   * To fix LP#1990379 also for focal the debdiff mentioned there is needed, 
too.
  __

  'zlib CRC32 optimization for s390x works only in a static library'

  I've discovered two issues in lp1932010-ibm-z-add-vectorized-
  crc32-implementation.patch:

  1) s390_crc32_vx() signature mismatch, resulting in a warning.
  2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being 
enabled only in the static library.

  I've attached the updated patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982583/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Simon Déziel
If you can fill out the SRU template, that'd be great! I see that you
worked with upstream to ID which commit corrected the problem, that will
be useful to whoever creates a debdiff! If you need a hand with the
debdiff, please let me know and I'll set some time aside. Thanks!

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Ian! D. Allen
I knew nothing about your SRU process until now; the man page for
`ubuntu-bug` makes no mention of it.  Who fills out the SRU Bug Template
and makes the fix actually happen?  Is there anything more I need to do
here?

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-10 Thread Dave Chiluk
In case anyone is curious conversation is on-going on the kernel-team mailing 
list 
https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-10 Thread Dimitri John Ledkov
@juliank please test initrd-less boot; for example lxc launch --vm which
uses linux-kvm flavour booted without initrd.

There are differences of the mount options as applied by initramfs-
tools; systemd; and kernel itself.

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-10 Thread Dave Chiluk
@juliank, is this an aws system?  If not there's a good chance that you
are using an initramfs to mount the filesystems.  That's definited in
either /etc/init.d/udev or directly out of the init that lives in the
initramfs.

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken

2022-10-10 Thread Stephan Walter
Added screenshot from Libreoffice, showing it affects multiple
applications and font sizes

** Attachment added: "Screenshot from Libreoffice"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+attachment/5622811/+files/Screenshot_2022-10-10_20-42-54.png

** Description changed:

  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
- looks quite broken. At least the letters EFHIKLMNT and the digits 1 and
- 4 are affected
+ looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4
+ are affected
  
  Please see the attached screenshot. This was obtained from `gnome-font-
  viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`
  
  As the font is the default for me in Firefox, it's quite noticeable.
  
- 
- $ dpkg -l gnome-font-viewer fonts-dejavu-extra 
+ $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fonts-dejavu package in Ubuntu:
  New

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1992369] [NEW] DejaVu Serif Italic capital letters and digits broken

2022-10-10 Thread Stephan Walter
Public bug reported:

After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
looks quite broken. At least the letters EFHIKLMNT and the digits 1 and
4 are affected

Please see the attached screenshot. This was obtained from `gnome-font-
viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

As the font is the default for me in Firefox, it's quite noticeable.


$ dpkg -l gnome-font-viewer fonts-dejavu-extra 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==>
ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate with>
ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

** Affects: fonts-dejavu (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot_2022-10-10_20-29-45.png"
   
https://bugs.launchpad.net/bugs/1992369/+attachment/5622810/+files/Screenshot_2022-10-10_20-29-45.png

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

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fonts-dejavu package in Ubuntu:
  New

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHIKLMNT and the digits 1
  and 4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  
  $ dpkg -l gnome-font-viewer fonts-dejavu-extra 
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Simon Déziel
@Ian, the back and forth on status was apparently due to a simple
mistake on which distro version was affected. The good news is that
thanks to comment #7, we now know that Kinetic is fixed which is one of
the required step to do a SRU
(https://wiki.ubuntu.com/StableReleaseUpdates) to have the fix land in
Jammy.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1898207] Re: package logsave (not installed) failed to install/upgrade: no package named 'logsave' is installed, cannot configure

2022-10-10 Thread Rubisel Prieto
I have same issue and could not fix with "apt-get install -f". Here my
output for "apt-get install -f"

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libip4tc2 libperl5.26
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  console-setup e2fsprogs logsave
Suggested packages:
  gpart fuse2fs e2fsck-static
Recommended packages:
  e2fsprogs-l10n
The following NEW packages will be installed:
  logsave
The following packages will be upgraded:
  console-setup e2fsprogs
2 upgraded, 1 newly installed, 0 to remove and 492 not upgraded.
Need to get 0 B/637 kB of archives.
After this operation, 346 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Preconfiguring packages ...
(Reading database ... 156633 files and directories currently installed.)
Preparing to unpack .../e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb ...
Unpacking e2fsprogs (1.45.5-2ubuntu1.1) over (1.44.1-1ubuntu1.4) ...
dpkg: error processing archive 
/var/cache/apt/archives/e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb (--unpack):
 unable to create '/etc/cron.d/e2scrub_all.dpkg-new' (while processing 
'./etc/cron.d/e2scrub_all'): Operation not permitted
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
update-initramfs: deferring update (trigger activated)
dpkg: considering deconfiguration of e2fsprogs, which would be broken by 
installation of logsave ...
dpkg: no, e2fsprogs is essential, will not deconfigure
 it in order to enable installation of logsave
dpkg: error processing archive 
/var/cache/apt/archives/logsave_1.45.5-2ubuntu1.1_amd64.deb (--unpack):
 installing logsave would break existing software
Errors were encountered while processing:
 /var/cache/apt/archives/e2fsprogs_1.45.5-2ubuntu1.1_amd64.deb
 /var/cache/apt/archives/logsave_1.45.5-2ubuntu1.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package logsave (not installed) failed to install/upgrade: no package
  named 'logsave' is installed, cannot configure

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  updating crashes
  as suggested I did apt-get install -f
  now everything is working fine.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: logsave (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  2 12:45:08 2020
  DpkgTerminalLog:
   dpkg: error processing package logsave (--configure):
no package named 'logsave' is installed, cannot configure
  ErrorMessage: no package named 'logsave' is installed, cannot configure
  InstallationDate: Installed on 2016-02-08 (1697 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: e2fsprogs
  Title: package logsave (not installed) failed to install/upgrade: no package 
named 'logsave' is installed, cannot configure
  UpgradeStatus: Upgraded to focal on 2020-10-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1898207/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Ian! D. Allen
The problem was marked as Confirmed by Paride back on March 17.
Then today it gets marked Invalid.
Then later today it gets marked Confirmed again.
I don't understand your process.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1992364] [NEW] package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-10-10 Thread Дмитрий
Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Oct 10 19:26:40 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2022-10-09 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Oct 10 19:26:40 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992364/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Simon Déziel
I can confirm the problem affects rsync 3.2.3-8ubuntu3 as shipped in
22.04.

** Changed in: rsync (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1973830] Re: Error upgrading from Ubuntu 20.04 to 22.04

2022-10-10 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Importance: Undecided => High

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

Title:
  Error upgrading from Ubuntu 20.04 to 22.04

Status in apt package in Ubuntu:
  Triaged

Bug description:
  ERROR Dist-upgrade failed: 'The package 'update-manager' is marked for
  removal but it is in the removal deny list.'

  Inside log file /var/log/dist-upgrade/main.log after trying:
  sudo do-release-upgrade -d

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.38
  ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
  Uname: Linux 5.4.0-110-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 17 23:44:43 2022
  InstallationDate: Installed on 2020-05-16 (731 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2022-05-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1973830/+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 1988819] Re: When apt keeps back packages due to phased updates, it should say so

2022-10-10 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Importance: Undecided => Medium

** Changed in: apt (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: apt (Ubuntu)
   Importance: Medium => High

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  When apt keeps back packages due to phased updates, it should say so

Status in apt package in Ubuntu:
  Triaged

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+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 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed

2022-10-10 Thread Julian Andres Klode
** Tags removed: foundations-todo

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

Title:
  grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but
  2.06-2ubuntu10 is to be installed

Status in apt package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Phased updates with interdependencies can become uninstallable, breaking the 
upgrade command (and presumably dist-upgrade), so it cannot upgrade
  anything anymore, for example, see the original bug report below.

  [Test plan]
  We cannot reproduce the exact failure here, but we have included a minimal 
test case that triggers the same error in the integration test 
test-phased-updates-upgrade.

  The test suite is exhaustive and covers more than a human reasonably
  can, especially since we also cannot publish broken updates again to
  get people to test the fix.

  [Where problems could occur]
  This is a one word fix in the solver. When deciding whether a depends could 
be kept back, we accidentally looked at the package declaring the dependency 
instead of the package we depend upon.

  Of course this might unearth other fancy solver bugs. There is one
  limitation in that this only applies to "Protected" packages (not in the 
Protected field sense, but if you "Protect" the change in the solver), which is 
*mostly* triggered only if you have held packages or phased updates, so 
workarounds should always be easy.

  [Original bug report]

  # apt clean

  # apt update
  Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease
  Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates 
InRelease
  Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports 
InRelease
  Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  24 packages can be upgraded. Run 'apt list --upgradable' to see them.

  # apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  The following packages have unmet dependencies:
   grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 
2.06-2ubuntu10 is to be installed
  E: Broken packages

  # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:"
  Version: 2.06-2ubuntu10
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports 
jammy-updates/main arm64 Packages
  Version: 2.06-2ubuntu7
  APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main 
arm64 Packages

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu7)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu7)

  # curl -s 
"http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/main/binary-arm64/Packages.gz;
 | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:"
  Package: grub-efi-arm64-dbg
  Depends: grub-efi-arm64-bin (= 2.06-2ubuntu10)
  Package: grub-efi-arm64-signed
  Depends: grub-efi-arm64 (= 2.06-2ubuntu10)

  [[Workaround]]
  echo "APT::Get::Never-Include-Phased-Updates: 1;" > 
/etc/apt/apt.conf.d/99phased-updates

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-arm64-signed 1.180+2.06-2ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Sep 23 13:12:07 2022
  Ec2AMI: ami-092d30890417a55e5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ca-central-1d
  Ec2InstanceType: t4g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: grub2-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1990684/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2022-10-10 Thread iPadGuy
I just upgraded from Ubuntu 20.04 to 22.04.1, and this bug now affects
me.

I first encountered it in Brave Browser, then tested Google Chrome, and
neither one will let me enter a filename--instead, it jumps to the
filter box, and clears the directory.  Renaming files after they're
downloaded seems to be the only way to save the files, and is not an
acceptable workaround.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Ian! D. Allen
Your incorrect statement "seems the issue does not actually exist" is
wrong.  I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release.  I gave you the link to the upstream bug that Wayne
fixed over two years ago.  This two-year-old bug does exist and it
exists in your most recent Ubuntu 22.04.1 LTS release.  Here's another
way to show the bug:

$ touch foo
$ rsync --update --info=skip foo foo
foo is newer

Obviously a file should not be listed as newer than itself.  This rsync
is broken.

The real bug appears to be that Ubuntu is shipping a broken two-year-old
year 3.2.3 version of rsync in its latest 22.04.1 LTS release and won't
update it to get rid of the bug.  I've added a comment to the github bug
number 98 warning people about the broken Ubuntu LTS.

All my scripts that depend on an accurate "is newer" indicator from
rsync are broken.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Invalid

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Ian! D. Allen
Your incorrect statement "seems the issue does not actually exist" is
wrong.  I told you exactly how to reproduce the problem on your latest
22.04.1 LTS release.  You were also given the link to the upstream bug
that Wayne fixed over two years ago.  This two-year-old bug does exist
and it exists in your most recent Ubuntu 22.04.1 LTS release.  Here's
another way to show the bug:

$ touch foo
$ rsync --update --info=skip foo foo
foo is newer

Obviously a file should not be listed as newer than itself.  This rsync
is broken.

The real bug appears to be that Ubuntu is shipping a broken two-year-old
year 3.2.3 version of rsync in its latest 22.04.1 LTS release and won't
update it to get rid of the bug.

All my scripts that depend on an accurate "is newer" indicator from
rsync are broken.

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Invalid

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

2022-10-10 Thread Mlocik97
I use one installation in both physical and VM environments, then I require it 
to work.
I also often clone systems from VM to HW and viceversa.

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Opinion
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  [ Workaround ]

  1. Install *without* the third-party option.

  2. sudo apt install ubuntu-restricted-extras

  3. sudo apt remove gstreamer1.0-vaapi

  
  [ Original Description ]

  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1969901] Re: network-manager fails to renew ipv6 address

2022-10-10 Thread Håkan Kvist
I have tested the new version of the debdiff including the fix and the
fix of the fix.

Using it daily on my laptop and also tested it in the test setup described in 
the description.
No issues seen so far.

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

Title:
  network-manager fails to renew ipv6 address

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Incomplete

Bug description:
  [Impact]

   * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
  used.

   * Network manager might kill dhclient(6) and fail to start it again
     causing the IPv6 address to be lost on a network that uses mixed
     IPv4/IPV6.
     The network status will still be seen as online in gnome since ipv4
     is still active.
     The user then have to manually remove the dhcpv6 lease files and
     restart ipv6 connection/restart network manager to regain IPv6
     connectivity.

   * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
     is based on 1.10.6):
     
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f

   * Upstream bug:
     https://bugzilla.gnome.org/show_bug.cgi?id=783391

  [Test Plan]

  The test requires three computers
  * one computer runing isc dhcpd server (with network configured static)
  * one computer running patched network manager
  * one computer running vanilla ubuntu

  The idea is to execute on an isolated network and trigger the error by 
changing
  ip range handed out by the dhcp-server to force a nack response back to the
  clients.

  Expected result
  * patched network keeps dhclient6 alive
  * vanilla network manager will fail to keep dhclient6 alive
in network manager logs dhcp6 will expire and not be restarted

  ON THE SERVER
  # Disable app-armor, as it has rules restricting dhcpd
  aa-teardown

  # install isc dhcpserver
  isc-dhcp-server

  # configure network static
  sudo nmcli connection modify "${CONNECTION_NAME}" \
   ipv4.method "manual" \
   ipv4.addresses "192.168.1.1/24" \
   ipv4.gateway "192.168.1.254" \
   ipv4.dns "192.168.1.1" \
   ipv6.method "manual" \
   ipv6.addresses "2001:db8:0:1::1/64" \
   ipv6.gateway "2001:db8:0:1::ffbb" \
   ipv6.dns "2001:db8:0:1::1/64"

  mkdir -p tmp
  touch tmp/dhcpd4_a.leases
  touch tmp/dhcpd4_b.leases
  touch tmp/dhcpd6_a.leases
  touch tmp/dhcpd6_b.leases

  Then it is time to execute dhcpd
  -f - run in foreground
  -d - print errors to stderr instead of syslog

  # Start in separate terminals
  dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
  dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6

  Press ctrl-C to kill servers, then restart with the b configurations

  dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
  dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6

  Then leases to expire (check for clients that kills dhclient)
  Press ctrl-C to kill servers, then restart with the a configurations

  ON THE CLIENTS
  Setup:
  Configure ipv6 network in settings to use dhcp (using the gui)

  Test:
  check that dhcp clients are still running:
  ps aux|grep dhclient

  Expected in output
  one client for dhcpv4
  one client for dhcpv6

  Also check network manager status :
  journalctl -u NetworkManager.service
  journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
  journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4

  if dhclient is not running:
  stop network in gui
  remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the 
lease for the client not running.
  start network in gui

  if dhclients are running:
  wait additional ten minutes, repeat from beginning of test

  [Where problems could occur]

   * The change is in the dchp lease expiration handling so verify that
  there is no regression in dhcp renewals on different type of
  configuration include IPv6

  [Other Info]
   * We have tested this patch on a couple of clients where we have seen this
     this problem. If this patch is feasible to include in Ubuntu 18.04 we
     could request more users to test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+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 1992346] [NEW] Fractional scaling settings lost on logout

2022-10-10 Thread Andreas Kemper
Public bug reported:

I'm running Ubuntu 22.04.1 on VirtualBox latest release for quite some
time. Recently switched from 2560x1440 to 3840x2160 monitor resolution,
which forced me to enable 125% fractional scaling. Using default wayland
server, the scaling will be reset to 100% every time I do a logout or
change the resolution, e.g. (dis-) connecting the external monitor.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 10 14:56:52 2022
DistUpgraded: 2022-08-14 13:03:40,111 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2021-08-22 (413 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f4feeb72-92ed-4dd4-b498-dd6006b2c61c ro quiet splash ipv6.disable=1
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-08-14 (57 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  Fractional scaling settings lost on logout

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 22.04.1 on VirtualBox latest release for quite some
  time. Recently switched from 2560x1440 to 3840x2160 monitor
  resolution, which forced me to enable 125% fractional scaling. Using
  default wayland server, the scaling will be reset to 100% every time I
  do a logout or change the resolution, e.g. (dis-) connecting the
  external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 10 14:56:52 2022
  DistUpgraded: 2022-08-14 13:03:40,111 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2021-08-22 (413 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 

[Touch-packages] [Bug 1978738] Re: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded"

2022-10-10 Thread Oibaf
@eugenesan

Is there a plan to merge your update version into the official Ubuntu
package?

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

Title:
  systemd-oomd and zram-config services: "Swap is currently not
  detected; memory pressure usage will be degraded"

Status in systemd package in Ubuntu:
  Invalid
Status in zram-config package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  New
Status in zram-config source package in Jammy:
  New

Bug description:
  Problem summary:
  
  I've installed the zram-config package. By default it creates a zram swap 
device with half the physical memory size of the system. For instance, in an 
8GB RAM system:

  # swapon
  NAME   TYPE  SIZE USED PRIO
  /dev/zram0 partition 3,8G   1M5

  #zramctl
  NAME   ALGORITHM DISKSIZE  DATA COMPR TOTAL STREAMS MOUNTPOINT
  /dev/zram0 lzo-rle   3,8G  496K 74,9K  376K   4 [SWAP]

  The problem is that when systemd-oomd.service is started during boot
  it doesn't detect that zram swap device because zram-config.service is
  started later. So when systemd-oomd.service was started the zram
  device didn't exists yet. This is the message shown during boot:

  systemd-oomd[587]: Swap is currently not detected; memory pressure
  usage will be degraded

  If you restart systemd-oomd.service after boot it's correctly started
  because zram-config.service was previously loaded and zram device
  exists. So I think it's just a matter of dependencies during boot
  process; it's necessary to make zram-config.service be started before
  systemd-oomd.service (or to make systemd-oomd.service be restarted
  when zram-config.service is started).

  Aditional info:
  ---
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # apt-cache policy systemd-oomd
  systemd-oomd:
Instalados: 249.11-0ubuntu3.1
Candidato:  249.11-0ubuntu3.1
Tabla de versión:
   *** 249.11-0ubuntu3.1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

  # apt-cache policy zram-config
  zram-config:
Instalados: 0.7build1
Candidato:  0.7build1
Tabla de versión:
   *** 0.7build1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1978738/+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 1982583] Re: Fix for zlib CRC32 optimization for s390x

2022-10-10 Thread Julian Andres Klode
** Tags added: foundation-triage-discuss

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

Title:
  Fix for zlib CRC32 optimization for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * There were two issues identified in the current
     zlib CRC32 optimization for s390x implementation:

   * 1) s390_crc32_vx() signature mismatch
    which causes a warning

   * 2) '-DS390_CRC32_VX' was not added to SFLAGS
    which results in vectorization being enabled only in the static library.

   * The fixes are quite small and affect each only one line:

   * 1) by using unsigned longs instead of uint32_t in s390_crc32_vx
  declaration

   * 2) by add line 'SFLAGS="$SFLAGS -DS390_CRC32_VX"'

  [ Test Plan ]

   * An affected Ubuntu release ([20.04], 22.04 and 22.10) installed
     on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
     of a small test program (in C) that checks for
     s390_crc32_vx() signature mismatches.

   * The bug reporter has a set of s390x-specific tests that will be
  executed.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The fixes are each limited to one line, hence there are
     not many issues to expect, other than:

   * Typos (e.g. in the flags), mixing of CFLAGS and SFLAGS,

   * in case the changed data type in s390_crc32_vx is causing issues
     inside of s390_crc32_vx or in other parts of the code.

   * Structural and syntactical issues can be identified with a test build
     that was done for all affected Ubuntu releases and for all major archs:
     https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379+lp1982583

  [ Other Info ]

   * This bug (LP#1982583) is solved in combination with LP#1990379,
     so that only one package update is needed.
     However, LP#1990379 also affects Focal, but this bug only Jammy and 
Kinetic.

   * To fix LP#1990379 also for focal the debdiff mentioned there is needed, 
too.
  __

  'zlib CRC32 optimization for s390x works only in a static library'

  I've discovered two issues in lp1932010-ibm-z-add-vectorized-
  crc32-implementation.patch:

  1) s390_crc32_vx() signature mismatch, resulting in a warning.
  2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being 
enabled only in the static library.

  I've attached the updated patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982583/+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 1992246] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error

2022-10-10 Thread Julian Andres Klode
Your /boot partition ran out of space, consider increasing its size or
cleaning it up

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to
  install/upgrade: installed linux-firmware package post-installation
  script subprocess returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  I was performing an apt-get upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.5
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Sat Oct  8 11:20:24 2022
  Dependencies: firmware-sof-signed 2.0-1ubuntu3
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-05-20 (871 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp0s4no wireless extensions.
  Lsusb:
   Bus 002 Device 002: ID fb5d:0001 BHYVE HID Tablet
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
  MachineType: FreeBSD BHYVE
  PackageArchitecture: all
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sj5h4p@/vmlinuz-5.15.0-47-generic 
root=ZFS=rpool/ROOT/ubuntu_sj5h4p ro quiet splash vt.handoff=1
  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.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-07-12 (88 days ago)
  dmi.bios.date: 11/10/2020
  dmi.bios.release: 0.0
  dmi.bios.vendor: BHYVE
  dmi.bios.version: 13.0
  dmi.board.asset.tag: None
  dmi.board.name: BHYVE
  dmi.board.vendor: FreeBSD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 2
  dmi.chassis.vendor: FreeBSD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnBHYVE:bvr13.0:bd11/10/2020:br0.0:svnFreeBSD:pnBHYVE:pvr1.0:rvnFreeBSD:rnBHYVE:rvr1.0:cvnFreeBSD:ct2:cvr1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: BHYVE
  dmi.product.sku: None
  dmi.product.version: 1.0
  dmi.sys.vendor: FreeBSD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992246/+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 1992247] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-10-10 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1992246 ***
https://bugs.launchpad.net/bugs/1992246

** This bug has been marked a duplicate of bug 1992246
   package linux-firmware 20220329.git681281e4-0ubuntu3.5 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  occurred while running an apt-get upgrade after a fresh reboot

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Oct  8 11:25:32 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-05-20 (871 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-07-12 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992247/+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 1992206] Re: bash: non existent locale crashes bash

2022-10-10 Thread Julian Andres Klode
Sponsored.

** Changed in: bash (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  bash: non existent locale crashes bash

Status in bash package in Ubuntu:
  Fix Committed
Status in bash package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1021109:

  Package: libc6
  Version: 2.35-1
  Severity: grave
  Justification: renders package unusable
  X-Debbugs-Cc: kos...@debian.org

  Dear maintainer,

  After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent 
locale setting
  starts to crash the system.

  This is dangerous because a remote system might not always have the same 
locale installed.
  An auto update will soft-brick the system unless the sysadmin knows to set 
their LC_ALL=POSIX
  before attempting to ssh.

  Steps to reproduce:

  From a clean installed Debian sid, upgrade to libc6 2.35-1.
  Only install C locale and en_US.UTF-8.

  $ LC_ALL=ja_JP.UTF-8 bash
  bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
  Segmentation fault (core dumped)

  $ LC_ALL=ja_JP.UTF-8 gdb bash

  Fatal signal: Segmentation fault
  - Backtrace -
  0x55ed3e1e8dcf ???
  0x55ed3e2df312 ???
  0x55ed3e2df488 ???
  0x7f0b4a39ba9f ???
  0x7f0b4b412204 _rl_init_locale
  0x7f0b4b4122f1 _rl_init_eightbit
  0x7f0b4b3f10f2 rl_initialize
  ... snip ...

  Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
  state was invalidated when upgrading.

  Thanks,
  Kan-Ru

  
  -- System Information:
  Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)

  Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages libc6 depends on:
  ii  libgcc-s1  12.2.0-3

  Versions of packages libc6 recommends:
  ii  libidn2-0  2.3.3-1+b1

  Versions of packages libc6 suggests:
  ii  debconf [debconf-2.0]  1.5.79
  pn  glibc-doc  
  ii  libc-l10n  2.35-1
  pn  libnss-nis 
  pn  libnss-nisplus 
  ii  locales2.35-1

  -- debconf information:
glibc/kernel-too-old:
glibc/restart-failed:
glibc/disable-screensaver:
glibc/upgrade: true
  * libraries/restart-without-asking: false
  * glibc/restart-services: cron
glibc/kernel-not-supported:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1992206/+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 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el

2022-10-10 Thread Julian Andres Klode
** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu)
   Status: New => Triaged

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

Title:
  autopkgtest: upstream tests that run in qemu hang on ppc64el

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I believe this started early in the kinetic cycle, cf.
  https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs
  https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el.
  Timeouts in the upstream tests have been an issue for a while, but
  kinetic on ppc64el consistently times out with upstream tests that run
  in QEMU.

  Skipping individual tests does not help, because *which* tests time
  out appears to change with each build. For example, in 251.4-1ubuntu4
  the TEST-36-NUMAPOLICY test was consistently the culprit, but now in
  251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out.

  I have not been able to identify a root cause for this, but it seems
  that running tests in QEMU is very fragile on ppc64el, where as the
  tests that run in nspawn are more consistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992178/+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 1992025] Re: When sudo does not require a password, it alters stty as though it is reading a password

2022-10-10 Thread Julian Andres Klode
As this needs SRUing presumably, as it's broken in kinetic, this needs a
description of the impact. What does it mean that the state changed, how
does it impact the user?

Is this something security team wants to address, should foundations
address this?

** Also affects: sudo (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: sudo (Ubuntu)
   Status: Confirmed => Triaged

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

** Changed in: sudo (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: sudo (Ubuntu)
   Importance: Undecided => Medium

** Also affects: sudo (Ubuntu Kinetic)
   Importance: Medium
   Status: Triaged

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

Title:
  When sudo does not require a password, it alters stty as though it is
  reading a password

Status in sudo package in Ubuntu:
  Triaged
Status in sudo source package in Jammy:
  Confirmed
Status in sudo source package in Kinetic:
  Triaged

Bug description:
  Summary:
  Executing a sudo (that does not require a password) in a /bin/bash script 
leaves the terminal as though it is reading a password (-echo, -icrnl, -ixon, 
-opost, -isig, -icanon, -iexten)

  To recreate the problem: (See attached log)

  In a fresh install of 22.04.1 (desktop, minimal, do not load updates,
  no update done beyond iso data, running under Virtualbox on a Mac), I
  set up a new user that can run "sudo sleep" without a password.  In a
  Terminal, I demonstrate this, running "stty -a" before and after the
  "sudo sleep". Then I create a bash script with those same commands.
  When that script is run, the stty after the "sudo sleep" shows that
  the state of the terminal has been altered (-echo, etc.)

  The log starts immediately after the reboot after installing 22.04.1.
  I decline to do the update when it is offered. (The bug appears even
  if I do the update on 22.04.1, but I decline the update to make sure
  this is repeatable.)

  Basically, the steps are
Create user "testuser"
Add a file to /etc/sudoers.d that gives testuser sudo privs, with no 
password required for sleep.  (nor for "grep", but I dropped the use of grep in 
the demo)
su - testuser
Interactively, in the terminal, I show that "sudo sleep 30 &"  does not 
mess with the terminal settings.
I create a /bin/bash script that includes the same commands (stty -a; sudo 
sleep 10 &; sleep 3; stty -a)
I execute the script, which alters the terminal settings.(Quite visible on 
the Terminal; not as easily visible in the log file.)

  
  I expect the second "stty -a" to be the same as the first.

  I originally saw the bug in 20.04.5 (repeatable but on someone else's
  computer) for "sudo tcpdump" but wasn't able to reproduce it in a
  fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: sudo 1.9.9-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  6 10:40:03 2022
  InstallationDate: Installed on 2022-10-06 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   Error: command ['pkexec', '/usr/sbin/visudo', '-c'] failed with exit code 1: 
/etc/sudoers.d/testuser: bad permissions, should be mode 0440
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK
  modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: 
'/etc/sudoers']
  modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/README']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1992025/+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 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-10 Thread Julian Andres Klode
On my kinetic system, /dev has nosuid, but no noexec.

** Tags added: foundations-triage-discuss

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 1978738] Re: systemd-oomd and zram-config services: "Swap is currently not detected; memory pressure usage will be degraded"

2022-10-10 Thread Julian Andres Klode
** Also affects: systemd (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: zram-config (Ubuntu Jammy)
   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/1978738

Title:
  systemd-oomd and zram-config services: "Swap is currently not
  detected; memory pressure usage will be degraded"

Status in systemd package in Ubuntu:
  Invalid
Status in zram-config package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  New
Status in zram-config source package in Jammy:
  New

Bug description:
  Problem summary:
  
  I've installed the zram-config package. By default it creates a zram swap 
device with half the physical memory size of the system. For instance, in an 
8GB RAM system:

  # swapon
  NAME   TYPE  SIZE USED PRIO
  /dev/zram0 partition 3,8G   1M5

  #zramctl
  NAME   ALGORITHM DISKSIZE  DATA COMPR TOTAL STREAMS MOUNTPOINT
  /dev/zram0 lzo-rle   3,8G  496K 74,9K  376K   4 [SWAP]

  The problem is that when systemd-oomd.service is started during boot
  it doesn't detect that zram swap device because zram-config.service is
  started later. So when systemd-oomd.service was started the zram
  device didn't exists yet. This is the message shown during boot:

  systemd-oomd[587]: Swap is currently not detected; memory pressure
  usage will be degraded

  If you restart systemd-oomd.service after boot it's correctly started
  because zram-config.service was previously loaded and zram device
  exists. So I think it's just a matter of dependencies during boot
  process; it's necessary to make zram-config.service be started before
  systemd-oomd.service (or to make systemd-oomd.service be restarted
  when zram-config.service is started).

  Aditional info:
  ---
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # apt-cache policy systemd-oomd
  systemd-oomd:
Instalados: 249.11-0ubuntu3.1
Candidato:  249.11-0ubuntu3.1
Tabla de versión:
   *** 249.11-0ubuntu3.1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   249.11-0ubuntu3 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

  # apt-cache policy zram-config
  zram-config:
Instalados: 0.7build1
Candidato:  0.7build1
Tabla de versión:
   *** 0.7build1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1978738/+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 1992306] Re: Default to a2dp ldac_hq codec for bluethooth headset and sound distorted

2022-10-10 Thread Mårten Thornberg
Ok, created a new issue upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1400

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1400
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1400

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

Title:
  Default to a2dp ldac_hq codec for bluethooth headset and sound
  distorted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had some trouble getting my bluetooth headphones to work and I
  believe the culprit is the default codec that pulseaudio chooses. It
  appears to work ok when having no other Bluetooth devices connected,
  but when connecting a bluetooth mouse the audio gets distorted and
  begins to stutter. The offending codec is ldac_hq. I did some
  investigating today and found out you can change the codec in
  pavucontrol. Selecting ldac_sq seems to work without any issue.

  I don't know what the problem with ldac_hq is, maybe bandwidth? Wasn't
  able to find any obvious problems in the logs, even when enabling
  debugging in bluez.

  While investigating this I noticed others having the same issue, and
  it was difficult to find a way to change the codec, so maybe ldac_hq
  shouldn't be chosen as default?

  Headphones: Sony WF-1000XM
  Mouse: Logitech M590
  Computer: 
https://www.asus.com/Laptops/For-Home/Zenbook/Zenbook-S-UX391/techspec/

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5201 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
  Bus 001 Device 002: ID 13d3:56b9 IMC Networks USB2.0 HD UVC WebCam
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  description: Bluetooth wireless interface
 product: Bluetooth wireless interface
 vendor: Intel Corp.
 physical id: 8
 bus info: usb@1:8
 version: 0.10
 capabilities: bluetooth usb-2.00
 configuration: driver=btusb maxpower=100mA speed=12Mbit/s

  Ubuntu 22.04.1 LTS
  pulseaudio: 1:15.99.1+dfsg1-1ubuntu1
  bluez: 5.64-0ubuntu1
  pavucontrol: 5.0-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1992306/+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 1973830] Re: Error upgrading from Ubuntu 20.04 to 22.04

2022-10-10 Thread Julian Andres Klode
Likely same issue as bug 1974196, reassigning to apt for further
investigation.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Invalid => Triaged

** Package changed: ubuntu-release-upgrader (Ubuntu) => apt (Ubuntu)

** Tags added: foundations-todo

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

Title:
  Error upgrading from Ubuntu 20.04 to 22.04

Status in apt package in Ubuntu:
  Triaged

Bug description:
  ERROR Dist-upgrade failed: 'The package 'update-manager' is marked for
  removal but it is in the removal deny list.'

  Inside log file /var/log/dist-upgrade/main.log after trying:
  sudo do-release-upgrade -d

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.38
  ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
  Uname: Linux 5.4.0-110-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 17 23:44:43 2022
  InstallationDate: Installed on 2020-05-16 (731 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2022-05-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1973830/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

2022-10-10 Thread Julian Andres Klode
Adding a focal task as bug 1973830 seems to be caused by the same issue.

** Also affects: apt (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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1974196

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  New
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

2022-10-10 Thread Julian Andres Klode
** Tags removed: foundations-todo

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

Title:
  Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Invalid

Bug description:
  Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  While reporting Bug #1973469, I discovered that ubuntu-bug was unable
  to open Firefox at the very end of the process. Sadly, I closed the
  terminal window that contained the initial error, but I was able to
  easily reproduce it reporting this bug. The full console output of
  "ubuntu-bug apport" on Lubuntu Kinetic is:

  
  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  94%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

  I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
  just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
  is due to the Snap version of Firefox, but I don't know for sure.
  Since ubuntu-bug is what gave me the error, I'm filing this against
  Apport.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:41:07 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1973470/+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 1973830] [NEW] Error upgrading from Ubuntu 20.04 to 22.04

2022-10-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

ERROR Dist-upgrade failed: 'The package 'update-manager' is marked for
removal but it is in the removal deny list.'

Inside log file /var/log/dist-upgrade/main.log after trying:
sudo do-release-upgrade -d

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.38
ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
Uname: Linux 5.4.0-110-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue May 17 23:44:43 2022
InstallationDate: Installed on 2020-05-16 (731 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2022-05-17 (0 days ago)

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


** Tags: amd64 apport-bug dist-upgrade focal
-- 
Error upgrading from Ubuntu 20.04 to 22.04
https://bugs.launchpad.net/bugs/1973830
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt in Ubuntu.

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


[Touch-packages] [Bug 1968109] Re: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources

2022-10-10 Thread Julian Andres Klode
Qt frontend broken, seems to access self.cache[module_packages] where
module_packages is not a string or pair of strings, causing a TypeError.
Don't know if anyone actively  maintains that.

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu)
   Status: New => Triaged

** Tags added: foundations-triage-discuss

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

Title:
  "Apply changes" button remains disabled after selecting Wi-Fi driver
  in Software Sources

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009
  MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of
  the box.

  What I expect to happen is something I can do successfully in Ubuntu
  Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that
  version. In KDE Settings I click on "Driver Manager", which
  automatically opens Software Sources (that's the only way I know how
  to get there). It finds and shows my [proprietary Broadcom] Wi-Fi
  driver; I click on it, then the "Apply Changes" button is enabled
  after a second or two. I click that, wait about half a minute with a
  progress bar in action below, and then the Wi-Fi options appear the
  notification area, allowing me to connect.

  I attached a screen record of what actually happens in Ubuntu Studio
  22.04 beta (thankfully this distro comes with screen recording
  software out of the box). When I click on "Driver Manager", a "xterm"
  window (version 372-1ubuntu1 I think?) opens unexpectedly with some
  code showing up in it (the code is in the screen record), shortly
  before Software Sources (version 0.99.20) opens as expected. The same
  driver still appears on the list. When I click on the driver, it seems
  to still take that second or two to transition, with some more code
  appearing in "xterm", but the "Apply Changes" button never enables
  itself. It remains disabled so I can't click it. The "revert" button
  directly next to it is also disabled. Thus, I can't connect my
  computer to Wi-Fi in 22.04 beta.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.20
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: KDE
  Date: Fri Mar 18 17:00:53 2022
  LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968109/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself

2022-10-10 Thread Julian Andres Klode
I cannot reproduce the issue in kinetic's 3.2.5, seems the issue does
not actually exist. If the issue exists in any stable release, I believe
it is minor enough to not warrant a stable release update.

** Changed in: rsync (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  rsync --update incorrectly reports file "is newer" than itself

Status in rsync package in Ubuntu:
  Invalid

Bug description:
  rsync 3.2.3 has a broken "--update" option.See the examples below.
  The "--update" option incorrectly makes rsync say a file is newer than itself.
  Remove the "--update" option, and rsync correctly says the file is "uptodate".
  The right output should of course be "is uptodate" in all cases.
  This bug also shows up between machines if the source rsync is 3.1.3 and the 
destination is 3.2.3.
  The bug does not show up if the source rsync is 3.2.3 and the destination is 
3.1.3.

  $ touch foo
  $ rsync -avv --update foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is newer <=== THIS IS NOT CORRECT - A file can't be newer 
than itself.
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 38 bytes  received 96 bytes  268.00 bytes/sec
  total size is 0  speedup is 0.00

  $ rsync -avv foo .
  delta-transmission disabled for local transfer or --whole-file
  foo is uptodate  <=== THIS IS CORRECT
  total: matches=0  hash_hits=0  false_alarms=0 data=0
  sent 41 bytes  received 106 bytes  294.00 bytes/sec
  total size is 0  speedup is 0.00

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: rsync 3.2.3-4ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 22:47:44 2022
  InstallationDate: Installed on 2022-03-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1960383] Re: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2022-10-10 Thread Julian Andres Klode
This does not appear to be an Ubuntu system, but a pop os one. Neither
does it appear to be an upgrade to 21.04 for that matter as the bug
says. It also involves various downgrades. Either way this is all very
unsupported.

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  While installing 21.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  9 13:04:28 2022
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2022-02-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.1
   apt  2.0.6
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960383/+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 1992303] Re: [BOD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card. I have "dummy audio@ outout and no inputs. Please help

2022-10-10 Thread Sebastien Bacher
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but it is better to raise problems you are having in the
support tracker at https://answers.launchpad.net/ubuntu if you are
uncertain if they are bugs. If you would prefer live chat support, you
can find an IRC support channel for your flavor of Ubuntu here:
https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with
your problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs.

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

** Changed in: pulseaudio (Ubuntu)
   Status: New => Invalid

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

Title:
  [BOD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails
  to detect card. I have "dummy audio@ outout and no inputs. Please help

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I've tried some updates and upgrades but nothing changed. Accroding to
  forrums this question is not solved for my audiocard

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bari   1635 F pipewire-media-
   /dev/snd/seq:bari   1634 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  9 20:55:47 2022
  InstallationDate: Installed on 2022-10-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Digital Out, HDMI
  Title: [BOD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails 
to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2022
  dmi.bios.release: 2.29
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 2.29
  dmi.board.asset.tag: N/A
  dmi.board.name: BOD-WXX9-PCB-B3
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1010
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1010
  dmi.ec.firmware.release: 2.29
  dmi.modalias: 
dmi:bvnHUAWEI:bvr2.29:bd04/21/2022:br2.29:efr2.29:svnHUAWEI:pnBOD-WXX9:pvrM1010:rvnHUAWEI:rnBOD-WXX9-PCB-B3:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC171:
  dmi.product.family: MateBook D
  dmi.product.name: BOD-WXX9
  dmi.product.sku: C171
  dmi.product.version: M1010
  dmi.sys.vendor: HUAWEI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1992303/+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 1992306] Re: Problem with default a2dp codec for bluethooth headset

2022-10-10 Thread Sebastien Bacher
Thank you for your bug report, could you also register the problem
upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/ ? that's
probably a better place to suggest a such change

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

** Summary changed:

- Problem with default a2dp codec for bluethooth headset
+ Default to a2dp ldac_hq codec for bluethooth headset and sound distorted

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

Title:
  Default to a2dp ldac_hq codec for bluethooth headset and sound
  distorted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had some trouble getting my bluetooth headphones to work and I
  believe the culprit is the default codec that pulseaudio chooses. It
  appears to work ok when having no other Bluetooth devices connected,
  but when connecting a bluetooth mouse the audio gets distorted and
  begins to stutter. The offending codec is ldac_hq. I did some
  investigating today and found out you can change the codec in
  pavucontrol. Selecting ldac_sq seems to work without any issue.

  I don't know what the problem with ldac_hq is, maybe bandwidth? Wasn't
  able to find any obvious problems in the logs, even when enabling
  debugging in bluez.

  While investigating this I noticed others having the same issue, and
  it was difficult to find a way to change the codec, so maybe ldac_hq
  shouldn't be chosen as default?

  Headphones: Sony WF-1000XM
  Mouse: Logitech M590
  Computer: 
https://www.asus.com/Laptops/For-Home/Zenbook/Zenbook-S-UX391/techspec/

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5201 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
  Bus 001 Device 002: ID 13d3:56b9 IMC Networks USB2.0 HD UVC WebCam
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  description: Bluetooth wireless interface
 product: Bluetooth wireless interface
 vendor: Intel Corp.
 physical id: 8
 bus info: usb@1:8
 version: 0.10
 capabilities: bluetooth usb-2.00
 configuration: driver=btusb maxpower=100mA speed=12Mbit/s

  Ubuntu 22.04.1 LTS
  pulseaudio: 1:15.99.1+dfsg1-1ubuntu1
  bluez: 5.64-0ubuntu1
  pavucontrol: 5.0-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1992306/+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 1760106] Re: Enable configuring resume offset via sysfs

2022-10-10 Thread Julian Andres Klode
Is there anything left to do here?

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

** Changed in: klibc (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in klibc source package in Bionic:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in klibc source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760106/+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 1991771] Re: [FFe] Update to 3.0.6

2022-10-10 Thread Julian Andres Klode
** Changed in: openssl (Ubuntu)
   Status: New => Triaged

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

Title:
  [FFe] Update to 3.0.6

Status in openssl package in Ubuntu:
  Triaged

Bug description:
  There's an upcoming security release for OpenSSL according to
  https://mta.openssl.org/pipermail/openssl-
  users/2022-October/015477.html

  The timing is somewhat unfortunate given our own release schedule.

  The current version of openssl in kinetic, 3.0.5-2ubuntu1, is actually
  a snapshot of the 3.0 branch ahead of 3.0.5 (inherited from Debian
  during the last merge).

  Sadly, they don't have a proper changelog (even partial) for the
  upcoming release yet, but I'll attach the diff and shortlog between
  our current version and the current state of the branch to get an idea
  of what's to come. As usual for their 3.0 point releases, it's not
  just security fixes but general bugfixes as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1991771/+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 1990379] Re: [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used

2022-10-10 Thread Julian Andres Klode
I looked at the queues for focal and jammy but did not find any zlib
uploads as indicated by "in progress" per SRU policy, so reset the
status to "triaged".

** Changed in: zlib (Ubuntu Focal)
   Status: In Progress => Triaged

** Changed in: zlib (Ubuntu Jammy)
   Status: In Progress => Triaged

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

Title:
  [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if
  DFLTCC is used

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  Triaged
Status in zlib source package in Jammy:
  Triaged
Status in zlib source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:
  --

  [ Impact ]

   * The zlib function inflate() does not update strm.adler
     in case DFLTCC is used.

   * This issue was exposed by Java Certification Kit (JCK) running on z15
     hardware and newer and impacts all JDK versions (8,11,17, etc.)
     that use the system default settings.

   * The JCK failure impacts the ability to certify Java SDKs on this
     platform/Linux-distribution combination.

   * On top the incorrect alder32 result may cause functional issues with
     Java applications that depend on the result.

  [ Test Plan ]

   * An affected Ubuntu release (20.04, 22.04 and 22.10) installed
     on a z15/LinuxONE III or newer system is needed.

   * Then it's possible to test the updated package with the help
     of a small test program (in C) that makes use of the zlib1g library
     or run the Java Certification Kit.

   * Test will be done by IBM.

  [ Where problems could occur ]

   * The patch is a one-line change:
     https://launchpadlibrarian.net/626003193/410-lp1990379.patch
     and there are not many issues to expect.

   * There could be a potential problem with the adler field
     in the strm struct.
     For example in case the struct is not as assumed or contains
     and unexpected value, which would then ripple through
     the other fields, too.

   * Structural changes could be identified with a test build that was done
     for all affected Ubuntu releases and for all major architectures:
     https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379

  [ Other Info ]

   * The patch itself is the same for all zlib version in
     20.04, 22.04 and 22.10 - no further adjustments were needed.

   * This bug (LP#1990379) is solved in combination with LP#1982583,
 so that only one package update is needed.
 However, this bug affects Kinetic, jammy and Focal,
 but LP#1982583 only Jammy and Kinetic.

   * The debdiffs for Kinetic and Jammy should be taken from LP#1982583,
 and the remaining debdiff for Focal from here.

  __

  == Comment: #0 - Ilya Leoshkevich  - 2022-09-21 05:02:24 ==
  inflate() does not update strm.adler if DFLTCC is used.

  Found with a JDK test.

  zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349

  Updated zlib PR: https://github.com/madler/zlib/pull/410

  zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920

  zlib diff:
  
https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620

  Ubuntu 20.04 and later need to be fixed.

  ---
  External link: https://warthogs.atlassian.net/browse/PEI-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

2022-10-10 Thread Juerg Haefliger
Log entries from failure:


==
FAIL: test_no_failed (__main__.ServicesTest)
No failed units
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.fs4rtb/build.SVB/src/debian/tests/boot-and-services", 
line 68, in test_no_failed
self.assertEqual(failed, [])
AssertionError: Lists differ: ['systemd-remount-fs.service loaded failed[41 
chars]ems'] != []

First list contains 1 additional elements.
First extra element 0:
'systemd-remount-fs.service loaded failed failed Remount Root and Kernel File 
Systems'

+ []
- ['systemd-remount-fs.service loaded failed failed Remount Root and Kernel 
File '
-  'Systems']

--
Ran 23 tests in 5.022s

FAILED (failures=1, skipped=6)
autopkgtest [12:03:21]: test boot-and-services: ---]
autopkgtest [12:03:26]: test boot-and-services:  - - - - - - - - - - results - 
- - - - - - - - -
boot-and-servicesFAIL non-zero exit status 1

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

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1992235] Re: Xorg freeze

2022-10-10 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Tags added: amdgpu

** Summary changed:

- Xorg freeze
+ Screen freeze

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Screen freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Updated to 22.10 beta last week.

  When I return after screensaver activation, the display freezes.
  Sometimes the greeter fades in a little bit, sometimes it is just the
  background image. Every time, I can move the mouse and the cursor
  changes when hovering over the password box (or where it would have
  been). I can type my password and the session unlocks. I know this
  because the greeter process is gone, and the mouse cursor now changes
  as if it were my desktop (input boxes, buttons, etc) but the display
  still has never updated.

  This has happened about 5 times now, but reproducing it could be hard
  because it only seems to happen after an idle period when the screen
  locks itself. Manually locking/unlocking the screen works fine.
  Switching off the monitors with "xset dpms force off" also doesn't
  seem to trigger it.

  There doesn't appear to be anything useful in the log files, but I
  think apport has attached them anyway.

  Happy to do any debugging necessary.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  Uname: Linux 6.0.0-06-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Oct  8 11:12:25 2022
  DistUpgraded: 2022-10-05 00:54:56,716 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi/9904, 5.15.0-48-generic, x86_64: installed
   backport-iwlwifi/9904, 5.19.0-18-generic, x86_64: installed
   backport-iwlwifi/9904, 6.0.0-06-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:8760]
  InstallationDate: Installed on 2021-06-24 (470 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HP HP EliteBook 845 G7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to kinetic on 2022-10-04 (3 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 10.0
  dmi.bios.vendor: HP
  dmi.bios.version: S77 Ver. 01.10.00
  dmi.board.name: 8760
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 07.3A.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 7.58
  dmi.modalias: 
dmi:bvnHP:bvrS77Ver.01.10.00:bd07/15/2022:br10.0:efr7.58:svnHP:pnHPEliteBook845G7NotebookPC:pvr:rvnHP:rn8760:rvrKBCVersion07.3A.00:cvnHP:ct10:cvr:sku8VZ07AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 845 G7 Notebook PC
  dmi.product.sku: 8VZ07AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112-3ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 1992272] Re: hp manager tools

2022-10-10 Thread Daniel van Vugt
Please explain what the problem is you would like to discuss.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  hp  manager tools

Status in Ubuntu:
  Incomplete

Bug description:
  fix

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.141.03  Thu Jun 30 
18:45:31 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct  9 02:33:20 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/470.141.03, 5.15.0-48-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1495]
   NVIDIA Corporation GK107GL [Quadro K420] [10de:0ff3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GK107GL [Quadro K420] [10de:1106]
  InstallationDate: Installed on 2022-10-09 (0 days ago)
  InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=8329facb-efd9-458b-a74b-76ca724785f9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/04/2016
  dmi.bios.release: 2.29
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.29
  dmi.board.asset.tag: HPS7956
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: HPS7956
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.29:bd04/04/2016:br2.29:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:skuXL510AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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