[Desktop-packages] [Bug 1941752]

2021-12-27 Thread Nicolas-fella
*** Bug 447585 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Fix Released
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1327801] Re: Bightness and contrast settings have no effect

2021-12-27 Thread Bug Watch Updater
** Changed in: sane-backends (Debian)
   Status: Unknown => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1327801

Title:
  Bightness and contrast settings have no effect

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  Confirmed
Status in simple-scan package in Ubuntu:
  Invalid
Status in sane-backends package in Debian:
  Confirmed

Bug description:
  Scanner: Canon, Inc. CanoScan N1240U/LiDE 30
  Ubuntu 14.04, Simple Scan version 3.12.1.

  Adjusting the settings of brightness and contrast has no effect.

  With the default for scanning in "text" mode being too bright, this makes 
"Simple Scan" in text mode unusable for me.
  Brightness and contrast settings don't work in "foto" mode, too. But the 
default of the foto mode is usable.

  Brightness setting does work in program "Skanlite".

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1327801/+subscriptions


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


[Desktop-packages] [Bug 1955862] [NEW] Headphones have a faint square/triangle wave sound when unmuted

2021-12-27 Thread Donovan Drews
Public bug reported:

This issue can be replicated on both Ubuntu 21.10 and 22.04 installs,
but is not present on the live USB version of either. It is also not an
issue on Fedora 35 (using aplay directly to device) nor Windows 10. The
issue can be resolved until reboot by unplugging and replugging several
times, as well as switching between speaker and headphones. I am not
sure of a deterministic way to replicate this workaround.

Alsamixer reports the chipset as ALC287, but according to specs it is
actually an ALC3306. I am not sure if this is related.

I can do any additional testing as necessary to narrow down the issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.0+dfsg1-1ubuntu6
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 27 20:28:31 2021
InstallationDate: Installed on 2021-12-28 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211227)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful
Symptom_Card: Tiger Lake-H HD Audio Controller - sof-hda-dsp
Symptom_Jack: Black Headphone Out, Right
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: High background noise, or volume is too low
Title: [20YQ004JUS, Realtek ALC287, Black Headphone Out, Right] Background 
noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2021
dmi.bios.release: 1.15
dmi.bios.vendor: LENOVO
dmi.bios.version: N37ET34W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20YQ004JUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnLENOVO:bvrN37ET34W(1.15):bd09/01/2021:br1.15:efr1.8:svnLENOVO:pn20YQ004JUS:pvrThinkPadP15Gen2i:skuLENOVO_MT_20YQ_BU_Think_FM_ThinkPadP15Gen2i:rvnLENOVO:rn20YQ004JUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P15 Gen 2i
dmi.product.name: 20YQ004JUS
dmi.product.sku: LENOVO_MT_20YQ_BU_Think_FM_ThinkPad P15 Gen 2i
dmi.product.version: ThinkPad P15 Gen 2i
dmi.sys.vendor: LENOVO

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


** Tags: impish jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1955862

Title:
  Headphones have a faint square/triangle wave sound when unmuted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This issue can be replicated on both Ubuntu 21.10 and 22.04 installs,
  but is not present on the live USB version of either. It is also not
  an issue on Fedora 35 (using aplay directly to device) nor Windows 10.
  The issue can be resolved until reboot by unplugging and replugging
  several times, as well as switching between speaker and headphones. I
  am not sure of a deterministic way to replicate this workaround.

  Alsamixer reports the chipset as ALC287, but according to specs it is
  actually an ALC3306. I am not sure if this is related.

  I can do any additional testing as necessary to narrow down the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu6
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 27 20:28:31 2021
  InstallationDate: Installed on 2021-12-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211227)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-H HD Audio Controller - sof-hda-dsp
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: High background noise, or volume is too low
  Title: [20YQ004JUS, Realtek ALC287, Black Headphone Out, Right] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N37ET34W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20YQ004JUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  

[Desktop-packages] [Bug 1935669] Re: Gnome calendar app doesn't start

2021-12-27 Thread Launchpad Bug Tracker
[Expired for gnome-calendar (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-calendar (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1935669

Title:
  Gnome calendar app doesn't start

Status in gnome-calendar package in Ubuntu:
  Expired

Bug description:
  I installed the gnome-calendar app through snap and it doesn't start.

  Output of `dmesg -w`

  
  ```
  [632748.772120] audit: type=1400 audit(1625822731.031:18470): 
apparmor="DENIED" operation="open" profile="snap.gnome-calendar.gnome-calendar" 
name="/var/lib/snapd/hostfs/usr/lib/x86_64-linux-gnu/libGL.so.1.7.0" pid=726971 
comm="gnome-calendar" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [632748.772122] audit: type=1400 audit(1625822731.031:18471): 
apparmor="DENIED" operation="open" profile="snap.gnome-calendar.gnome-calendar" 
name="/var/lib/snapd/hostfs/usr/lib/x86_64-linux-gnu/libEGL.so.1.1.0" 
pid=726971 comm="gnome-calendar" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
  [632748.774023] audit: type=1400 audit(1625822731.031:18472): 
apparmor="DENIED" operation="open" profile="snap.gnome-calendar.gnome-calendar" 
name="/var/lib/snapd/hostfs/usr/lib/x86_64-linux-gnu/libGLX.so.0.0.0" 
pid=726971 comm="gnome-calendar" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
  [632748.774025] audit: type=1400 audit(1625822731.031:18473): 
apparmor="DENIED" operation="open" profile="snap.gnome-calendar.gnome-calendar" 
name="/var/lib/snapd/hostfs/usr/lib/x86_64-linux-gnu/libGLdispatch.so.0.0.0" 
pid=726971 comm="gnome-calendar" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1935669/+subscriptions


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


[Desktop-packages] [Bug 1948704] Re: segfault with gnome-shell

2021-12-27 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1948704

Title:
  segfault with gnome-shell

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Using Ubuntu 20.04.3 LTS with 5.11.0-38-generic #42~20.04.1-Ubuntu,
  gnome-shell/focal-updates,now 3.36.9-0ubuntu0.20.04.2 amd64 
[installed,automatic]
  gnome-shell/focal-security 3.36.4-1ubuntu1~20.04.2 amd64
  gnome-shell/focal 3.36.1-5ubuntu1 amd64
  gnome-session/focal,focal 3.36.0-2ubuntu1 all

  Oct 22 19:41:09 ourserver kernel: [15260.574496] show_signal_msg: 29 
callbacks suppressed
  Oct 22 19:41:09 ourserver kernel: [15260.574503] gnome-shell[1475]: segfault 
at 11390db8 ip 7f3fd36f716c sp 7ffe50e6d788 error 4 in 
libmozjs-68.so.68.6.0[7f3fd3234000+843000]
  Oct 22 19:41:09 ourserver kernel: [15260.574525] Code: 50 10 85 d2 75 d0 0f 
b6 40 14 83 e8 01 3c 01 41 0f 96 c0 44 89 c0 c3 0f 1f 80 00 00 00 00 48 89 f0 
45 31 c0 48 25 00 00 f0 ff <48> 8b 90 f8 ff 0f 00 48 39 17 74 08 44 89 c0 c3 0f 
1f 40 00 48 85
  Oct 22 19:41:09 ourserver kernel: [15260.619146] apport[2636]: segfault at 3 
ip 0003 sp 7fffe172cb48 error 14 in python3.8[40+23000]
  Oct 22 19:41:09 ourserver kernel: [15260.619165] Code: Unable to access 
opcode bytes at RIP 0xffd9.
  Oct 22 19:41:09 ourserver kernel: [15260.619186] Process 2636(apport) has 
RLIMIT_CORE set to 1
  Oct 22 19:41:09 ourserver kernel: [15260.619189] Aborting core
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: message repeated 3 times: [ 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable']
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7d7860' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80f8e0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e811b20' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80e0a0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd938006460' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e82c1e0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7fc320' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd934004a60' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80ff60' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e8317a0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e8145e0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x7fd934005020' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e82c420' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e80fea0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7c05e0' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e7dfc20' of type 'GCancellable'
  Oct 22 19:41:09 ourserver NetworkManager[1049]: 
../../../gobject/gsignal.c:2595: signal 'cancelled' is invalid for instance 
'0x562e9e761320' of type 'GCancellable'
  Oct 22 19:41:09 ourserver gnome-session[1446]: 

[Desktop-packages] [Bug 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.

2021-12-27 Thread Launchpad Bug Tracker
[Expired for gnome-calendar (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-calendar (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1938658

Title:
  Week view goes blank when changing weeks or when user screen focus
  changes.

Status in gnome-calendar package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  gnome-calendar:
Installed: 3.36.2-0ubuntu1
Candidate: 3.36.2-0ubuntu1
Version table:
   *** 3.36.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Week view goes blank when changing weeks or when user screen focus changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+subscriptions


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


[Desktop-packages] [Bug 1327801] Re: Bightness and contrast settings have no effect

2021-12-27 Thread Gunnar Hjalmarsson
** Bug watch added: Debian Bug tracker #971725
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971725

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1327801

Title:
  Bightness and contrast settings have no effect

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  Confirmed
Status in simple-scan package in Ubuntu:
  Invalid
Status in sane-backends package in Debian:
  Unknown

Bug description:
  Scanner: Canon, Inc. CanoScan N1240U/LiDE 30
  Ubuntu 14.04, Simple Scan version 3.12.1.

  Adjusting the settings of brightness and contrast has no effect.

  With the default for scanning in "text" mode being too bright, this makes 
"Simple Scan" in text mode unusable for me.
  Brightness and contrast settings don't work in "foto" mode, too. But the 
default of the foto mode is usable.

  Brightness setting does work in program "Skanlite".

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1327801/+subscriptions


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


[Desktop-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster

2021-12-27 Thread ThomasE
** Also affects: pipewire
   Importance: Undecided
   Status: New

** Also affects: pulseaudio
   Importance: Undecided
   Status: New

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

Title:
  [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x
  faster

Status in PipeWire:
  New
Status in PulseAudio:
  New
Status in sound-2.6 (alsa-kernel):
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recording applications (audacity, arecord, gnome-sound-recorder)
  record extremely slowly (at what seems to be 0,1x speed), which means
  that at playback the sound is played at a very high pitch and much
  faster than the original.

  To help you understand the issue, I've attached an archive containing two 
files recorded at the same time, one with arecord -f cd and the other with a 
stand-alone Olympus recorder.
  A video of Audacity's behavior when trying to record is also available: 
https://youtu.be/Fe20eQNvZVA
  Look at the seconds hand of the xclock and how much it is moving before 
Audacity is done recording one second of audio.

  Things I've already tried:
  *  Purging and reinstalling Audacity
  *  Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki
  *  Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 
audacity as suggested on AskUbuntu
  *  Reinstalling Ubuntu on a new hard disk
  *  Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 
daily and Xubuntu 17.10.1, 18.04)

  The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard.

  The problem can be reproduced as follows:

  * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've 
tested with)
  * Install audacity via the terminal
  * Start recording, microphone is connected to the rear microphone jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacopo 2417 F pulseaudio
   /dev/snd/controlC0:  jacopo 2417 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 18 09:35:50 2018
  InstallationDate: Installed on 2018-03-03 (45 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Desktop-packages] [Bug 1955850] [NEW] /etc/X11/Xresources no longer loaded, error in patch

2021-12-27 Thread Matthijs Kooijman
Public bug reported:

After upgrading from 21.04 to 21.10, my /etc/X11/Xresources/ directory
no longer loads on login.

Looking at the sources, I think this can be traced to:
 - Switching from a custom Xsession file to the upstream Xsession file in 
3.38.0-1ubuntu1, combined with
 - An oversight in `debian/patches/ubuntu/xresources_is_a_dir.patch`

Looking at [that patch](https://salsa.debian.org/gnome-
team/gdm/-/blob/ubuntu/master/debian/patches/ubuntu/xresources_is_a_dir.patch),
it has:

```diff
--- a/data/Xsession.in
+++ b/data/Xsession.in
@@ -122,6 +122,13 @@ fi
 
 if [ -f "$sysresources" ]; then
 xrdb -nocpp -merge "$sysresources"
+elif [ -d "$sysresources" ]; then
+# directory of Xresources files on Debian/Ubuntu
+for i in `ls "$sysresources"` ; do
+if [ -r "$sysresources/$i"  -a -f "$sysresources/$i" ] && expr "$i" : 
'^[[:alnum:]_-]\+$' > /dev/null; then
+xrdb -nocpp -merge "$sysresources/$i"
+fi
+done
 fi
 
 if [ -f "$userresources" ]; then
```

However, looking a few lines further up in [the original Xsession.in
file](https://salsa.debian.org/gnome-
team/gdm/-/blob/ubuntu/master/data/Xsession.in#L97), I see:

```sh
if [ -f /etc/X11/Xresources ]; then
sysresources=/etc/X11/Xresources
else
sysresources=/usr/etc/X11/Xresources
fi
```

In other words, if `/etc/X11/Xresources` is a directory, the
`sysresources` variable is never set correctly, so the patch should also
modify this part of the script.

I have observed this broken behavior on version 41~rc-0ubuntu2, but
looking at the ubuntu/master branch (as linked above), it still seems
broken there.

I'm currently testing this patch:

```diff
--- Xsession.orig   2021-12-27 22:05:09.038863375 +0100
+++ Xsession2021-12-27 22:05:33.143057433 +0100
@@ -111,7 +111,7 @@
 usermodmap="$HOME/.Xmodmap"
 userxkbmap="$HOME/.Xkbmap"
 
-if [ -f /etc/X11/Xresources ]; then
+if [ -e /etc/X11/Xresources ]; then
 sysresources=/etc/X11/Xresources
 else
 sysresources=/usr/etc/X11/Xresources
```

I don't know if it works yet, since I need to log out for that, and
close my browser, so need to submit this report first ;-)

```
$ lsb_release -rd
Description:Ubuntu 21.10
Release:21.10
$ apt-cache policy gdm3
gdm3:
  Installed: 41~rc-0ubuntu2
  Candidate: 41~rc-0ubuntu2
  Version table:
 *** 41~rc-0ubuntu2 500
500 http://nl.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status
```

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1955850

Title:
  /etc/X11/Xresources no longer loaded, error in patch

Status in gdm3 package in Ubuntu:
  New

Bug description:
  After upgrading from 21.04 to 21.10, my /etc/X11/Xresources/ directory
  no longer loads on login.

  Looking at the sources, I think this can be traced to:
   - Switching from a custom Xsession file to the upstream Xsession file in 
3.38.0-1ubuntu1, combined with
   - An oversight in `debian/patches/ubuntu/xresources_is_a_dir.patch`

  Looking at [that patch](https://salsa.debian.org/gnome-
  
team/gdm/-/blob/ubuntu/master/debian/patches/ubuntu/xresources_is_a_dir.patch),
  it has:

  ```diff
  --- a/data/Xsession.in
  +++ b/data/Xsession.in
  @@ -122,6 +122,13 @@ fi
   
   if [ -f "$sysresources" ]; then
   xrdb -nocpp -merge "$sysresources"
  +elif [ -d "$sysresources" ]; then
  +# directory of Xresources files on Debian/Ubuntu
  +for i in `ls "$sysresources"` ; do
  +if [ -r "$sysresources/$i"  -a -f "$sysresources/$i" ] && expr "$i" 
: '^[[:alnum:]_-]\+$' > /dev/null; then
  +xrdb -nocpp -merge "$sysresources/$i"
  +fi
  +done
   fi
   
   if [ -f "$userresources" ]; then
  ```

  However, looking a few lines further up in [the original Xsession.in
  file](https://salsa.debian.org/gnome-
  team/gdm/-/blob/ubuntu/master/data/Xsession.in#L97), I see:

  ```sh
  if [ -f /etc/X11/Xresources ]; then
  sysresources=/etc/X11/Xresources
  else
  sysresources=/usr/etc/X11/Xresources
  fi
  ```

  In other words, if `/etc/X11/Xresources` is a directory, the
  `sysresources` variable is never set correctly, so the patch should
  also modify this part of the script.

  I have observed this broken behavior on version 41~rc-0ubuntu2, but
  looking at the ubuntu/master branch (as linked above), it still seems
  broken there.

  I'm currently testing this patch:

  ```diff
  --- Xsession.orig   2021-12-27 22:05:09.038863375 +0100
  +++ Xsession2021-12-27 22:05:33.143057433 +0100
  @@ -111,7 +111,7 @@
   usermodmap="$HOME/.Xmodmap"
   userxkbmap="$HOME/.Xkbmap"
   
  -if [ -f /etc/X11/Xresources ]; then
  +if [ -e /etc/X11/Xresources ]; then
   sysresources=/etc/X11/Xresources
   else
   sysresources=/usr/etc/X11/Xresources
  ```

  I don't know if it works yet, since 

[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

2021-12-27 Thread Bug Watch Updater
** Changed in: pygobject (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1954649

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  Fix Released
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  New
Status in python-taskflow package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in skimage package in Ubuntu:
  Invalid
Status in supysonic package in Ubuntu:
  New
Status in vorta package in Ubuntu:
  New
Status in ipywidgets package in Debian:
  New
Status in pygobject package in Debian:
  Fix Released
Status in pytest-twisted package in Debian:
  New
Status in python-b2sdk package in Debian:
  New
Status in python-hypothesis package in Debian:
  New
Status in supysonic package in Debian:
  New
Status in vorta package in Debian:
  Confirmed

Bug description:
  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.

  All packages are in universe except pygobject and python-taskflow in
  main.

  All packages have RC bugs in Debian except python-taskflow which is
  based on a newer upstream version.

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


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


[Desktop-packages] [Bug 1951698] Re: [upstream] under wayland items in menu bar sub-menus cannot be moved

2021-12-27 Thread Bug Watch Updater
** Changed in: firefox
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1951698

Title:
  [upstream] under wayland items in menu bar sub-menus cannot be moved

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  New

Bug description:
  When running firefox on wayland, it appears to be impossible to move
  bookmark items in the menu bar sub menus.

  How to reproduce:

  * haver a gnome session with wayland
  * have the menu bar toolbar activated
  * have a folder in the menu bar 
  * have multiple bookmarks in that folder
  * click on the folder icon in the menu bar, when it opens, try to drag and 
drop the item to put it into another position - e.g. from the last to the first

  Expected result:

  * the bookmark item is move to the new position - this is waht happens
  when doing these steps with firefox on gnome with an xorg sessions.

  
  Actual result: the item stays where it was.

  similarly, i cannot drag and drop a new bookmark into a folder and out
  it into the position where I want to have it.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 94.0+build3-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  henning   63267 F pulseaudio
   /dev/snd/controlC1:  henning   63267 F pulseaudio
  BuildID: 20211028161635
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
  Date: Sat Nov 20 21:21:03 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-12 (586 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=84.0.2/20210105180113 (Out of date)
   Profile0 - LastVersion=94.0/20211028161635 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to impish on 2021-11-14 (5 days ago)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET53W (1.40 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET53W(1.40):bd08/17/2021:br1.40:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QV00CEGE
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

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


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


[Desktop-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network

2021-12-27 Thread Till Kamppeter
Mathias Weyland (launchpad-weyland), thanks for the link to the patched
GTK, thispatch is generally a good idea as it is not a good idea of a
print dialog talking directly to IPP printers, circumventing CUPS.

The problems are the following:

1. A typical desktop application sends the data to get printed in PDF
format, but not all IPP printers understand PDF. The driverless IPP
standards only require one of the four print data formats PDF, Apple
Raster, PWG Raster, and PCLm. As PDF is a complex vector graphics format
and the other 3 are simple raster formats, cheap printers usually do not
understand PDF, so the dialog sending a job directly to the printer
would not work here. When printing through a CUPS queue, CUPS detects
which format the printer understands and converts if needed.

2. An essential functionality when printing from a desktop application
is spooling, storing the print job on disk when receiving it, so the the
dialog can close quickly and allow the user continuing to work in his
application. Many, especially cheaper IPP printers do not have such
capability, the dialog itself also does not spool AFAIK. Spooling is
usually a task of CUPS (CUPS is a so-called print spooler). Therefoe
printing should always go through CUPS.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1753509

Title:
  avahi-daemon adds/installs every printer on network

Status in cups-filters package in Ubuntu:
  Expired

Bug description:
  When connected to a network, avahi-daemon adds & installs all printer
  on a network without being prompted.  This is not desired behaviour.
  Discovery of the printers is good, but not automatic installation &
  addition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  5 09:29:05 2018
  InstallationDate: Installed on 2017-09-29 (157 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+subscriptions


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


[Desktop-packages] [Bug 1955044] Re: /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token

2021-12-27 Thread Nicholas Guriev
This is already fixed in upstream. Please apply their patch.
https://gitlab.gnome.org/GNOME/glibmm/-/merge_requests/50/diffs

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glibmm2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1955044

Title:
  /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected
  unqualified-id before ‘)’ token

Status in glibmm2.4 package in Ubuntu:
  New

Bug description:
  There are compilation errors when I try to include the  header 
under C++20.
  This is reproducible in Ubuntu 21.10 (Impish Indri) or Ubuntu devel (Jammy 
Jellyfish) but not in Ubuntu 21.04 (Impish Indri) or Debian unstable. And this 
is effecting building of the telegram-desktop package.

  mymedia@barberry:~$ g++ -x c++ -std=gnu++20 -include glibmm.h - <<< 'int 
main(){}' `pkg-config --cflags --libs glibmm-2.4` -o /dev/null 
  In file included from 
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
   from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
   from /usr/include/glibmm-2.4/glibmm.h:92,
   from :
  /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected 
unqualified-id before ‘)’ token
956 |   Variant();
|^
  /usr/include/glibmm-2.4/glibmm/variant.h:1017:25: error: expected 
unqualified-id before ‘)’ token
   1017 |   Variant< Variant >();
| ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1070:26: error: expected 
unqualified-id before ‘)’ token
   1070 |   Variant();
|  ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1240:24: error: expected 
unqualified-id before ‘)’ token
   1240 |   Variant();
|^
  /usr/include/glibmm-2.4/glibmm/variant.h:1286:30: error: expected 
unqualified-id before ‘)’ token
   1286 |   Variant< std::pair >()
|  ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1335:29: error: expected 
unqualified-id before ‘)’ token
   1335 |   Variant< std::vector >()
| ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1404:41: error: expected 
unqualified-id before ‘)’ token
   1404 |   Variant< std::vector >();
| ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1530:39: error: expected 
unqualified-id before ‘)’ token
   1530 |   Variant< std::vector >();
|   ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1606:29: error: expected 
unqualified-id before ‘)’ token
   1606 |   Variant< std::map >()
| ^
  /usr/include/glibmm-2.4/glibmm/variant.h:1679:33: error: expected 
unqualified-id before ‘)’ token
   1679 |   Variant>()
| ^
  In file included from /usr/include/glibmm-2.4/glibmm/variant.h:1742,
   from 
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
   from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
   from /usr/include/glibmm-2.4/glibmm.h:92,
   from :
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:23:17: error: expected 
unqualified-id before ‘)’ token
 23 |   Variant()
| ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:66:26: error: expected 
unqualified-id before ‘)’ token
 66 |   Variant()
|  ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:109:19: error: expected 
unqualified-id before ‘)’ token
109 |   Variant()
|   ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:152:20: error: expected 
unqualified-id before ‘)’ token
152 |   Variant()
|^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:195:19: error: expected 
unqualified-id before ‘)’ token
195 |   Variant()
|   ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:244:20: error: expected 
unqualified-id before ‘)’ token
244 |   Variant()
|^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:287:19: error: expected 
unqualified-id before ‘)’ token
287 |   Variant()
|   ^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:330:20: error: expected 
unqualified-id before ‘)’ token
330 |   Variant()
|^
  /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:373:19: error: expected 
unqualified-id before ‘)’ token
373 |   Variant()
|   ^
  In file included from 
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
   from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
   from /usr/include/glibmm-2.4/glibmm.h:92,
   from :
  /usr/include/glibmm-2.4/glibmm/variant.h:1751:1: error: no declaration 
matches 

[Desktop-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network

2021-12-27 Thread Mathias Weyland
lp:1477106 is another bug where this is being discussed (but didn't get
much attention). I agree that this is due to somewhat broken behaviour
of gtk3 and not cups-filter or avahi. In any case, an updated GTK 3
patch for Focal is available in the following for those who came here
with this problem:

https://launchpad.net/~launchpad-weyland/+archive/ubuntu/libgtk3-no-
avahi/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1753509

Title:
  avahi-daemon adds/installs every printer on network

Status in cups-filters package in Ubuntu:
  Expired

Bug description:
  When connected to a network, avahi-daemon adds & installs all printer
  on a network without being prompted.  This is not desired behaviour.
  Discovery of the printers is good, but not automatic installation &
  addition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  5 09:29:05 2018
  InstallationDate: Installed on 2017-09-29 (157 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+subscriptions


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


[Desktop-packages] [Bug 1955833] [NEW] Crash on the update of the local ICS calendar file

2021-12-27 Thread Mikhail Skorzhinskii
Public bug reported:

I start reproducing the crash after my upgrade to Ubuntu 21.10. The
crash happens if I setup local ICS calendar file and change something in
it outside of evolution. Then the whole evolution calendar service
crashes.

There is an upstream bug reported which fixes that crash:
https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/365

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: evolution-data-server 3.40.4-1
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
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Mon Dec 27 16:42:59 2021
InstallationDate: Installed on 2021-08-18 (130 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: evolution-data-server
UpgradeStatus: Upgraded to impish on 2021-12-26 (1 days ago)

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  Crash on the update of the local ICS calendar file

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

Bug description:
  I start reproducing the crash after my upgrade to Ubuntu 21.10. The
  crash happens if I setup local ICS calendar file and change something
  in it outside of evolution. Then the whole evolution calendar service
  crashes.

  There is an upstream bug reported which fixes that crash:
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/365

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: evolution-data-server 3.40.4-1
  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
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Dec 27 16:42:59 2021
  InstallationDate: Installed on 2021-08-18 (130 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to impish on 2021-12-26 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1955833/+subscriptions


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


[Desktop-packages] [Bug 1955827] Re: Firefox without 'TitleBar' alters the look of MATE buttons

2021-12-27 Thread Norbert
** Also affects: firefox (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1955827

Title:
  Firefox without 'TitleBar' alters the look of MATE buttons

Status in Ubuntu MATE:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I was testing Ubuntu MATE 20.04, and when I was configuring Firefox [95.0.1] 
I noticed that when I customized the toolbar and left it without 'Title Bar' 
the window buttons were cut off.
  I thought it might be a Firefox theme issue but when I changed the theme the 
problem persisted.

  https://subirimagenes.s3.eu-
  central-1.wasabisys.com/subirimagenes/2kYiAJh1dw.png

  https://subirimagenes.s3.eu-
  central-1.wasabisys.com/subirimagenes/uJZed9mBAC.png

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


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


[Desktop-packages] [Bug 1955826] [NEW] screen tearing

2021-12-27 Thread MONISH
Public bug reported:

screen was tearing while watching videos

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 27 18:46:54 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
InstallationDate: Installed on 2021-12-04 (22 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e360 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 5986:06b1 Acer, Inc EasyCamera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80SL
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=dbf98c46-2c30-46b7-9d28-b94843baabd5 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2018
dmi.bios.release: 1.45
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.ec.firmware.release: 1.45
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80SL:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80SL_BU_idea_FM_Lenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80SL
dmi.product.sku: LENOVO_MT_80SL_BU_idea_FM_Lenovo ideapad 310-14ISK
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug impish ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1955826

Title:
  screen tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  screen was tearing while watching videos

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 27 18:46:54 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
  InstallationDate: Installed on 2021-12-04 (22 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e360 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 5986:06b1 Acer, Inc EasyCamera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80SL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=dbf98c46-2c30-46b7-9d28-b94843baabd5 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  

[Desktop-packages] [Bug 1955820] [NEW] Arabic Text under scrolled by one character is not connected with other word characters

2021-12-27 Thread Islam Alshaikh إسلام الشيخ
Public bug reported:

Hello,

All Text with alt action _ are not connected.

You can add 'ـ' after some characters , this will keep small space but will not 
effect of reading.
Or under scrolled character viewing when press Alt only.

Err Examples in command buttons text:

حسناً viewed as ح سناً
موافق viewed as م وافق


Arabic Firefox is not have this problem. (ملف viewed as ملف)
In Arabic Kate (or other KDE application) text menu ملف viewed as م لف

This problem in all Alt under scrolled Arabic Text in almost all KDE
Applications. Arabic Firefox is not have like this bug.

This bug is in Kubuntu Groovy 20.10 too.
This bug will not accepted by almost Arabic users.

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Dec 27 15:25:07 2021
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 
00 [VGA controller])
   Subsystem: VMware VirtualBox Graphics Adapter [15ad:0405]
InstallationDate: Installed on 2021-12-26 (1 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211226)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 LANGUAGE=ar_SA:ar
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ar_SA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=db743c87-a1e6-4345-a978-33c5cd5a65ec ro quiet splash
SourcePackage: xorg
Symptom: display
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:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
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.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug has-workaround jammy kubuntu regression 
single-occurrence ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1955820

Title:
  Arabic Text under scrolled by one character is not connected with
  other word characters

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,

  All Text with alt action _ are not connected.

  You can add 'ـ' after some characters , this will keep small space but will 
not effect of reading.
  Or under scrolled character viewing when press Alt only.

  Err Examples in command buttons text:

  حسناً viewed as ح سناً
  موافق viewed as م وافق


  Arabic Firefox is not have this problem. (ملف viewed as ملف)
  In Arabic Kate (or other KDE application) text menu ملف viewed as م لف

  This problem in all Alt under scrolled Arabic Text in almost all KDE
  Applications. Arabic Firefox is not have like this bug.

  This bug is in Kubuntu Groovy 20.10 too.
  This bug will not accepted by almost Arabic users.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec 27 15:25:07 2021
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 

[Desktop-packages] [Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.

2021-12-27 Thread Ubuntu Foundations Team Bug Bot
The attachment ".debdiff for focal" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  [SRU] network-manager can’t modify MTU automatically based on what
  ModemManager exposes for WWAN modems.

Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some 4G/5G mobile networks(for ex., AT) requires a specific MTU
  setting, this setting will be exposed by the ModemManager for network-
  manger to configure the MTU of the modem network interface .

  The current modem-manager v1.22.10-1ubuntu2.2  in focal can’t pass
  AT’s modem system certification.

  [Fix]

  This upstream patch can resolve this bug:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631

  [Test Plan]

  1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an
  AT SIM card in US

  2. Enable 4G modem and connect to AT apn

  $ sudo mmcli -i 0 --pin=
  $ sudo mmcli --modem 0 --enable
  $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome"
  $ sudo nmcli radio wwan on
  $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn 
emome
  $ sudo nmcli connection up id mymodem

  3. Check if the MTU got from the following results are the same:

  $ sudo mmcli --bearer 5 | mtu
  $ ifconfig mhi_mbim0 | grep mtu

  * Expected result:
  Both MTUs are the same value 1430
  * Actual tested result:
  Different values (one is 1430 , another is 1500)

  [Where problems could occur]

  Very low.
  This is a simple fix: network-manager gets the MTU from the ModemManager then 
sets the MTU of the modem interface.

  [Other info]

  1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions


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


[Desktop-packages] [Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.

2021-12-27 Thread Jerry Lee
The .debdiff file “network-manager_1-1.22.10-1ubuntu2.3-focal.debdiff”
is attached for focal(20.04).

** Description changed:

  [Impact]
  
  Some 4G/5G mobile networks(for ex., AT) requires a specific MTU
  setting, this setting will be exposed by the ModemManager for network-
  manger to configure the MTU of the modem network interface .
  
  The current modem-manager v1.22.10-1ubuntu2.2  in focal can’t pass
  AT’s modem system certification.
  
  [Fix]
  
  This upstream patch can resolve this bug:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631
  
  [Test Plan]
  
  1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an
  AT SIM card in US
  
  2. Enable 4G modem and connect to AT apn
  
  $ sudo mmcli -i 0 --pin=
  $ sudo mmcli --modem 0 --enable
  $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome"
  $ sudo nmcli radio wwan on
  $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn 
emome
  $ sudo nmcli connection up id mymodem
  
  3. Check if the MTU got from the following results are the same:
  
  $ sudo mmcli --bearer 5 | mtu
  $ ifconfig mhi_mbim0 | grep mtu
  
- * Expected result: 
- Both MTUs are the same value 1430
- * Actual tested result: 
- Different values (one is 1430 , another is 1500)
+ * Expected result:
+ Both MTUs are the same value 1430
+ * Actual tested result:
+ Different values (one is 1430 , another is 1500)
  
  [Where problems could occur]
  
  Very low.
  This is a simple fix: network-manager gets the MTU from the ModemManager then 
sets the MTU of the modem interface.
  
  [Other info]
  
- $ lsb_release -rd
- Description:  Ubuntu 20.04.3 LTS
- Release:  20.04
+ 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix.

** Patch added: ".debdiff for focal"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+attachment/5549698/+files/network-manager_1-1.22.10-1ubuntu2.3-focal.debdiff

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

Title:
  [SRU] network-manager can’t modify MTU automatically based on what
  ModemManager exposes for WWAN modems.

Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some 4G/5G mobile networks(for ex., AT) requires a specific MTU
  setting, this setting will be exposed by the ModemManager for network-
  manger to configure the MTU of the modem network interface .

  The current modem-manager v1.22.10-1ubuntu2.2  in focal can’t pass
  AT’s modem system certification.

  [Fix]

  This upstream patch can resolve this bug:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631

  [Test Plan]

  1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an
  AT SIM card in US

  2. Enable 4G modem and connect to AT apn

  $ sudo mmcli -i 0 --pin=
  $ sudo mmcli --modem 0 --enable
  $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome"
  $ sudo nmcli radio wwan on
  $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn 
emome
  $ sudo nmcli connection up id mymodem

  3. Check if the MTU got from the following results are the same:

  $ sudo mmcli --bearer 5 | mtu
  $ ifconfig mhi_mbim0 | grep mtu

  * Expected result:
  Both MTUs are the same value 1430
  * Actual tested result:
  Different values (one is 1430 , another is 1500)

  [Where problems could occur]

  Very low.
  This is a simple fix: network-manager gets the MTU from the ModemManager then 
sets the MTU of the modem interface.

  [Other info]

  1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions


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


[Desktop-packages] [Bug 270479] Re: Debian/Ubuntu netpbm is many years out-of-date with upstream

2021-12-27 Thread Maxim Leyenson
This bug is still critical, with current (obsolete!) Ubuntu's version of
netpbm missing the 'pamthreshold'

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to netpbm-free in Ubuntu.
https://bugs.launchpad.net/bugs/270479

Title:
  Debian/Ubuntu netpbm is many years out-of-date with upstream

Status in netpbm-free package in Ubuntu:
  Confirmed
Status in netpbm-free package in Debian:
  Fix Released

Bug description:
  I'm having a little trouble following the difference between netpbm-
  free and the upstream version of netpbm available at
  http://netpbm.sourceforge.net, so I'm not sure if the version numbers
  are comparable, but it appears that the netpbm-free package is
  woefully out of date with upstream.

  I'm trying to use the -data option of pnmmontage which is was
  introduced into (upstream) version 10.06 of pnmmontage in 2002 (see
  
http://netpbm.svn.sourceforge.net/viewvc/netpbm/stable/doc/HISTORY?view=markup).

  While I'm not sure if the version numbers can be compared easily, it
  appears that Ubuntu is at 10.0 while the upstream netpbm libraries are
  at 10.35.51, which is  6 years covering 40 or so releases ahead of
  Ubuntu/Debian's version.

  What can be done to bring Ubuntu (and Debian) back up to date with the
  upstream versions of netpbm? Are there some licensing issues that are
  holding the repackaging up?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/270479/+subscriptions


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


[Desktop-packages] [Bug 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam

2021-12-27 Thread Chaoqi Zhang
OMG! It still exists on 2021-12-27, Ubuntu 20.02 LTS 64-bits.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1104476

Title:
  Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi
  networks without CA_Certificate, like Eduroam

Status in NetworkManager:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Triaged
Status in wpasupplicant package in Ubuntu:
  Triaged
Status in network-manager-applet source package in Trusty:
  Triaged
Status in wpasupplicant source package in Trusty:
  Triaged
Status in network-manager package in Debian:
  New
Status in Fedora:
  Fix Released
Status in Gentoo Linux:
  Fix Released
Status in network-manager package in openSUSE:
  Won't Fix

Bug description:
  HOW TO REPRODUCE:
  Connect to a MPA2/PEAP/MSCHAPv2 enterprise wifi network that doesn't use a CA 
Certificate, like Eduroam.

  RESULT:
  The computer doesn't connect, as the certificate verification fails.

  WORKAROUNDS:
  (http://askubuntu.com/questions/279762/cant-connect-to-wpa2-enterprise-peap)

  RELEASE NOTES TEXT:
  When connecting to MPA2/PEAP/MSCHAPv2 enterprise wifi networks that doesn't 
use a CA Certificate, like Eduroam, the connection fails 
(http://askubuntu.com/questions/279762/cant-connect-to-wpa2-enterprise-peap)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1104476/+subscriptions


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


[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2021-12-27 Thread Chaoqi Zhang
Still not fixed on 2022-12-27. Ubuntu 20.04 LTS 64-bits. NetworkManager
version 1.22.10.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions


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


[Desktop-packages] [Bug 1955797] [NEW] [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.

2021-12-27 Thread Jerry Lee
Public bug reported:

[Impact]

Some 4G/5G mobile networks(for ex., AT) requires a specific MTU
setting, this setting will be exposed by the ModemManager for network-
manger to configure the MTU of the modem network interface .

The current modem-manager v1.22.10-1ubuntu2.2  in focal can’t pass
AT’s modem system certification.

[Fix]

This upstream patch can resolve this bug:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631

[Test Plan]

1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an
AT SIM card in US

2. Enable 4G modem and connect to AT apn

$ sudo mmcli -i 0 --pin=
$ sudo mmcli --modem 0 --enable
$ sudo mmcli -m 0 --simple-connect="pin=,apn=emome"
$ sudo nmcli radio wwan on
$ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn 
emome
$ sudo nmcli connection up id mymodem

3. Check if the MTU got from the following results are the same:

$ sudo mmcli --bearer 5 | mtu
$ ifconfig mhi_mbim0 | grep mtu

* Expected result: 
Both MTUs are the same value 1430
* Actual tested result: 
Different values (one is 1430 , another is 1500)

[Where problems could occur]

Very low.
This is a simple fix: network-manager gets the MTU from the ModemManager then 
sets the MTU of the modem interface.

[Other info]

$ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority

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

Title:
  [SRU] network-manager can’t modify MTU automatically based on what
  ModemManager exposes for WWAN modems.

Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some 4G/5G mobile networks(for ex., AT) requires a specific MTU
  setting, this setting will be exposed by the ModemManager for network-
  manger to configure the MTU of the modem network interface .

  The current modem-manager v1.22.10-1ubuntu2.2  in focal can’t pass
  AT’s modem system certification.

  [Fix]

  This upstream patch can resolve this bug:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631

  [Test Plan]

  1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an
  AT SIM card in US

  2. Enable 4G modem and connect to AT apn

  $ sudo mmcli -i 0 --pin=
  $ sudo mmcli --modem 0 --enable
  $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome"
  $ sudo nmcli radio wwan on
  $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn 
emome
  $ sudo nmcli connection up id mymodem

  3. Check if the MTU got from the following results are the same:

  $ sudo mmcli --bearer 5 | mtu
  $ ifconfig mhi_mbim0 | grep mtu

  * Expected result: 
  Both MTUs are the same value 1430
  * Actual tested result: 
  Different values (one is 1430 , another is 1500)

  [Where problems could occur]

  Very low.
  This is a simple fix: network-manager gets the MTU from the ModemManager then 
sets the MTU of the modem interface.

  [Other info]

  $ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions


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


[Desktop-packages] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()

2021-12-27 Thread Paul Menzel
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1279
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1279

** Also affects: xorg-server via
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1279
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1751508

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("Couldn't add screen\n") from InitOutput()

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashed with VS Code.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Feb 24 18:28:10 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:3820]
  InstallationDate: Installed on 2018-02-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  MachineType: LENOVO 80NE
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=0beb58c8-0bf5-4e01-95dd-ae78f4ce0dea ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   InitOutput ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/09/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: BDCN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Yoga 500-14IBD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 500-14IBD
  dmi.modalias: 
dmi:bvnLenovo:bvrBDCN61WW:bd09/09/2015:svnLENOVO:pn80NE:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80NE
  dmi.product.version: Lenovo Yoga 500-14IBD
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1751508/+subscriptions


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