[Desktop-packages] [Bug 1993306] Re: wireplumber fails to uninstall pipewire-media-session
Closing because pipewire-media-session was removed since Ubuntu 23.10. All dependencies to pipewire-media-session were removed. ** Changed in: wireplumber (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire-media-session in Ubuntu. https://bugs.launchpad.net/bugs/1993306 Title: wireplumber fails to uninstall pipewire-media-session Status in pipewire-media-session package in Ubuntu: Opinion Status in wireplumber package in Ubuntu: Fix Released Bug description: kubuntu 22.10 and there are no audio devices in the kubuntu sound menu lspci 00:00.0 Host bridge: Intel Corporation Device 3e0f (rev 08) 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT1 [UHD Graphics 610] 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0) 00:1c.5 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #6 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a308 (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) pipewire-media-session [W][00635.699104] mod.rt | [ module-rt.c: 297 translate_error()] RTKit error: org.freedesktop.DBus.Error.AccessDenied [W][00635.699340] mod.rt | [ module-rt.c: 843 impl_acquire_rt()] could not make thread 32285 realtime using RTKit: Permission denied aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 dpkg -l | grep pipewire ii gstreamer1.0-pipewire:amd64 0.3.58-2ubuntu1 amd64GStreamer 1.0 plugin for the PipeWire multimedia server ii libpipewire-0.3-0:amd64 0.3.58-2ubuntu1 amd64libraries for the PipeWire multimedia server ii libpipewire-0.3-common 0.3.58-2ubuntu1 all libraries for the PipeWire multimedia server - common files ii libpipewire-0.3-modules:amd640.3.58-2ubuntu1 amd64libraries for the PipeWire multimedia server - modules ii pipewire:amd64 0.3.58-2ubuntu1 amd64audio and video processing engine multimedia server ii pipewire-bin 0.3.58-2ubuntu1 amd64PipeWire multimedia server - programs ii pipewire-media-session 0.4.1-4 amd64example session manager for PipeWire ii pipewire-pulse 0.3.58-2ubuntu1 amd64PipeWire PulseAudio daemon ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Oct 18 09:53:37 2022 SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2022-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1993306/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 2046001] Re: PipeWire: Too many open files
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3406 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3406 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3406 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2046001 Title: PipeWire: Too many open files Status in PipeWire: Unknown Status in pipewire package in Ubuntu: New Bug description: Starting with Ubuntu 23.10 , PipeWire regularly started running into a file descriptor limits likely to a known leak which is already fixed upstream, therefore either updating or fix backporting would be required. Symptoms vary: - Media playback may not start - Media playback may start but without sound - Media playback may suppress the audio output of another source Sample log output: ``` mod.access: 0x560d8eda5270: client 0x560d8f26fa50 sandbox check failed: Too many open files mod.access: 0x560d8eda5270: client 0x560d8f26fa50 sandbox check failed: Too many open files mod.client-node: can't create node: Too many open files mod.protocol-native: connection 0x560d8f270390: could not recvmsg on fd:0: Bad file descriptor mod.protocol-native: 0x560d8ed941a0: connection_data: client 0x560d8f26fa50 error -9 (Bad file descriptor) ``` More info: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3406 To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2046001/+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 2047046] Re: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-b
pipewire-bin 1.0.0-1~ubuntu23.10 comes from a PPA, it's not a package from Ubuntu repo. Your issue comes from this package, please report it to the PPA maintainer. The manpage of pipewire-pulse is in the wrong package pipewire-bin whereas it should be in pipewire-pulse ** Changed in: pipewire (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2047046 Title: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 Status in pipewire package in Ubuntu: Invalid Bug description: crashed when changing appearance ProblemType: Package DistroRelease: Ubuntu 24.04 Package: pipewire-pulse 1.0.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 17 03:57:20 2023 ErrorMessage: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 InstallationDate: Installed on 2023-07-08 (165 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.1ubuntu5 apt 2.7.6 SourcePackage: pipewire Title: package pipewire-pulse 1.0.0-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 1.0.0-1~ubuntu23.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2047046/+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 2046944] [NEW] Sync wireplumber 0.4.17-1 (main) from Debian testing (main)
Public bug reported:
Please sync wireplumber 0.4.17-1 from Debian.
The Ubuntu delta was merged in Debian:
wireplumber (0.4.17-1) unstable; urgency=medium
* New upstream version
-- Dylan Aïssi Mon, 04 Dec 2023 10:18:53 +0100
wireplumber (0.4.16-1) unstable; urgency=medium
[ Dylan Aïssi ]
* New upstream version
* Drop patch included in upstream release:
- policy-dsp: add ability to hide parent nodes
* Bump minimum pipewire to 0.3.68
* Update symbols file
[ Andreas Henriksson ]
* Use ${gir:Depends} and ${gir:Provides}
-- Dylan Aïssi Wed, 22 Nov 2023 17:59:06 +0100
wireplumber (0.4.15-2) unstable; urgency=medium
* Team upload.
* Cherry-pick upstream patch for ability to hide parent nodes
-- Andreas Henriksson Mon, 13 Nov 2023 18:14:25
+0100
wireplumber (0.4.15-1) unstable; urgency=medium
[ Dylan Aïssi ]
* New upstream version
* Install zsh completions file
* Update symbols file
[ Lena Voytek ]
* d/control: Upgrade lua build dependency to 5.4
-- Dylan Aïssi Fri, 13 Oct 2023 12:06:12 +0200
** Affects: wireplumber (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wireplumber in Ubuntu.
https://bugs.launchpad.net/bugs/2046944
Title:
Sync wireplumber 0.4.17-1 (main) from Debian testing (main)
Status in wireplumber package in Ubuntu:
New
Bug description:
Please sync wireplumber 0.4.17-1 from Debian.
The Ubuntu delta was merged in Debian:
wireplumber (0.4.17-1) unstable; urgency=medium
* New upstream version
-- Dylan Aïssi Mon, 04 Dec 2023 10:18:53 +0100
wireplumber (0.4.16-1) unstable; urgency=medium
[ Dylan Aïssi ]
* New upstream version
* Drop patch included in upstream release:
- policy-dsp: add ability to hide parent nodes
* Bump minimum pipewire to 0.3.68
* Update symbols file
[ Andreas Henriksson ]
* Use ${gir:Depends} and ${gir:Provides}
-- Dylan Aïssi Wed, 22 Nov 2023 17:59:06 +0100
wireplumber (0.4.15-2) unstable; urgency=medium
* Team upload.
* Cherry-pick upstream patch for ability to hide parent nodes
-- Andreas Henriksson Mon, 13 Nov 2023 18:14:25
+0100
wireplumber (0.4.15-1) unstable; urgency=medium
[ Dylan Aïssi ]
* New upstream version
* Install zsh completions file
* Update symbols file
[ Lena Voytek ]
* d/control: Upgrade lua build dependency to 5.4
-- Dylan Aïssi Fri, 13 Oct 2023 12:06:12 +0200
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2046944/+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 2020621] Re: "wpctl status" causes line wrap with big PID values
** Package changed: pipewire-media-session (Ubuntu) => wireplumber (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wireplumber in Ubuntu. https://bugs.launchpad.net/bugs/2020621 Title: "wpctl status" causes line wrap with big PID values Status in wireplumber package in Ubuntu: New Bug description: /usr/bin/wpctl is in package "wireplumber" cat /proc/sys/kernel/pid_max 4194304 Ubuntu 22.04LTS has PID value up to 4Mi (7 digit decimal) on a std terminal with 80 colomns it wraps lines if more then 5 digits for PID in my case. please fix the output of "wpctl status" for 7 digit PID value without line wrap. I see 8 SPACE characters at begin_of_line which can be reduced. └─ Clients: 31. pipewire[0.3.68, bernie@prod, pid:1434] 33. WirePlumber [0.3.68, bernie@prod, pid:1432] 34. WirePlumber [export][0.3.68, bernie@prod, pid:1432] 46. GNOME Shell Volume Control [0.3.68, bernie@prod, pid:3162] 47. GNOME Volume Control Media Keys [0.3.68, bernie@prod, pid:3336] 48. xdg-desktop-portal [0.3.68, bernie@prod, pid:6040] 49. gnome-shell [0.3.68, bernie@prod, pid:3162] 50. Terminal[0.3.68, bernie@prod, pid:3555] 51. Mutter [0.3.68, bernie@prod, pid:3162] 52. gjs [0.3.68, bernie@prod, pid:3502] 53. Firefox [0.3.68, bernie@prod, pid:215299] 57. wpctl [0.3.68, bernie@prod, pid:330390] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2020621/+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 2012745] [NEW] IPA modules are not resigned after dh_strip
Public bug reported: [ Reason ] Open source IPA (Image Processing Algorithms) modules are signed at build time allowing them to be trusted. However, IPA binaries are modified by dh_strip invalidating the signatures. Thus IPA modules provided in the package are not trusted anymore and need to be re-signed after the dh_strip step. This fix is applied in 0.0.4-3. [ Impact ] Not resigning IPA modules will make them untrusted, they will be isolated inside a Sandbox environment with restricted access to the system (like any closed-source module). Provided IPA modules won't work as expected. [ Risks ] The risk is low since we only regenerate signatures after dh_strip, i.e. /usr/lib/*/libcamera/ipa_.so.sign files. ** Affects: libcamera (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: libcamera (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1033118 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033118 ** Also affects: libcamera (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033118 Importance: Unknown Status: Unknown ** Changed in: libcamera (Ubuntu) Status: New => Confirmed ** Changed in: libcamera (Ubuntu) Milestone: None => ubuntu-23.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcamera in Ubuntu. https://bugs.launchpad.net/bugs/2012745 Title: IPA modules are not resigned after dh_strip Status in libcamera package in Ubuntu: Confirmed Status in libcamera package in Debian: Unknown Bug description: [ Reason ] Open source IPA (Image Processing Algorithms) modules are signed at build time allowing them to be trusted. However, IPA binaries are modified by dh_strip invalidating the signatures. Thus IPA modules provided in the package are not trusted anymore and need to be re-signed after the dh_strip step. This fix is applied in 0.0.4-3. [ Impact ] Not resigning IPA modules will make them untrusted, they will be isolated inside a Sandbox environment with restricted access to the system (like any closed-source module). Provided IPA modules won't work as expected. [ Risks ] The risk is low since we only regenerate signatures after dh_strip, i.e. /usr/lib/*/libcamera/ipa_.so.sign files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2012745/+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 2008525] Re: Both cam and qcam are terminated by signal SIGSEGV (Address boundary error)
*** This bug is a duplicate of bug 1999300 *** https://bugs.launchpad.net/bugs/1999300 ** This bug has been marked a duplicate of bug 1999300 crash in global constructor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcamera in Ubuntu. https://bugs.launchpad.net/bugs/2008525 Title: Both cam and qcam are terminated by signal SIGSEGV (Address boundary error) Status in libcamera package in Ubuntu: New Bug description: gdb bt #0 0x77f22456 in libcamera::ThreadData::current() () from /lib/x86_64-linux-gnu/libcamera.so.0 #1 0x77f22b9d in libcamera::Thread::currentId() () from /lib/x86_64-linux-gnu/libcamera.so.0 #2 0x77f17f37 in libcamera::LogOutput::write(libcamera::LogMessage const&) () from /lib/x86_64-linux-gnu/libcamera.so.0 #3 0x77f19402 in libcamera::Logger::write(libcamera::LogMessage const&) () from /lib/x86_64-linux-gnu/libcamera.so.0 #4 0x77f1a2f0 in libcamera::LogMessage::~LogMessage() () from /lib/x86_64-linux-gnu/libcamera.so.0 #5 0x77f07637 in libcamera::ControlInfoMap::generateIdmap() () from /lib/x86_64-linux-gnu/libcamera.so.0 #6 0x77f07841 in libcamera::ControlInfoMap::ControlInfoMap(std::initializer_list >) () from /lib/x86_64-linux-gnu/libcamera.so.0 #7 0x77ee9548 in ?? () from /lib/x86_64-linux-gnu/libcamera.so.0 #8 0x77eea364 in ?? () from /lib/x86_64-linux-gnu/libcamera.so.0 #9 0x77fc947e in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffde08, env=env@entry=0x7fffde18) at ./elf/dl-init.c:70 #10 0x77fc9568 in call_init (env=0x7fffde18, argv=0x7fffde08, argc=1, l=) at ./elf/dl-init.c:33 #11 _dl_init (main_map=0x77ffe2e0, argc=1, argv=0x7fffde08, env=0x7fffde18) at ./elf/dl-init.c:117 #12 0x77fe32ea in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #13 0x0001 in ?? () #14 0x7fffe184 in ?? () #15 0x in ?? () Package: libcamera0 Version: 0~git20200629+e7aa92a-9 Package: libcamera-tools Version: 0~git20200629+e7aa92a-9 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2008525/+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 1999300] Re: crash in global constructor
The libcamera version in Jammy is a almost 3 years old snaptshot of
libcamera because at this time, there was no release of libcamera.
libcamera is in active development with an API not yet stabilized that
means development around libcamera should at least target a released
version of libcamera, so the version in Jammy is probably is unusable.
Moreover, in Ubuntu repositories, libcamera is only used by pipewire but
only since Lunar. It is more likely that this bug won't be fixed in
Jammy. You should consider another way to get a more recent libcamera.
** Also affects: libcamera (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: libcamera (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: libcamera (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcamera in Ubuntu.
https://bugs.launchpad.net/bugs/1999300
Title:
crash in global constructor
Status in libcamera package in Ubuntu:
Fix Released
Status in libcamera source package in Jammy:
Confirmed
Bug description:
An application built with libcamera-dev crashes instantly on start in
a global constructor. This can be reproduced by the 'cam' example in
package libcamera-tools (run 'cam -l') or via this simple example;
#include
int main(int argc, char **argv) {
libcamera::CameraManager camera_manager;
}
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libcamera0 0~git20200629+e7aa92a-9
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 10 01:21:46 2022
InstallationDate: Installed on 2022-06-25 (167 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
SourcePackage: libcamera
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/1999300/+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 1999300] Re: crash in global constructor
Fixed in Lunar with libcamera 0.0.2.
cam -l doesn't crash anymore.
** Changed in: libcamera (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcamera in Ubuntu.
https://bugs.launchpad.net/bugs/1999300
Title:
crash in global constructor
Status in libcamera package in Ubuntu:
Fix Released
Bug description:
An application built with libcamera-dev crashes instantly on start in
a global constructor. This can be reproduced by the 'cam' example in
package libcamera-tools (run 'cam -l') or via this simple example;
#include
int main(int argc, char **argv) {
libcamera::CameraManager camera_manager;
}
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libcamera0 0~git20200629+e7aa92a-9
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 10 01:21:46 2022
InstallationDate: Installed on 2022-06-25 (167 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
SourcePackage: libcamera
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/1999300/+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 1991934] Re: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #1069 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1069 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1069 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1991934 Title: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic Status in PipeWire: Unknown Status in pipewire package in Ubuntu: Confirmed Status in pipewire package in Debian: New Bug description: Started PipeWire Multimedia Service. mod.rt: Can't find xdg-portal: (null) mod.rt: found session bus but no portal mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied mod.rt: could not make thread 4909 realtime using RTKit: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1991934/+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 1993357] Re: cannot find xdg-portal on every boot
*** This bug is a duplicate of bug 1991934 *** https://bugs.launchpad.net/bugs/1991934 ** This bug is no longer a duplicate of bug 1991673 mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied with Pipewire on Ubuntu kinetic 22.10 ** This bug has been marked a duplicate of bug 1991934 mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993357 Title: cannot find xdg-portal on every boot Status in pipewire package in Ubuntu: Confirmed Bug description: fresh kinetic install pipewire cannot find xdg-portal, why is it looking it for it? is it supposed to be there? why is it a warning? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1993357/+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 1993358] Re: pipewire pactl no such file or directory
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #2385 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2385 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2385 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993358 Title: pipewire pactl no such file or directory Status in PipeWire: Unknown Status in pipewire package in Ubuntu: Confirmed Bug description: fresh kinetic install pw.conf execvp error pactl no such file or directory is it supposed to be there? error from pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993358/+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 1992101] Re: No sound devices listed in Settings
RTKit error messages is a known bug [1], pipewire services are started before rtkit service thus pipewire fails to received the requested priority for realtime stuff. I confirm this is not related to the "no device shown" symptom. This "no device shown" symptom is due to a race condition between pipewire-pulse and wireplumber services [2]. The pipewire-pulse service is ready before wireplumber, thus wireplumber doesn't report any available device to pipewire-pulse. I proposed a debdiff in [3] to avoid this issue. I attach the debdiff here again. [1] https://bugs.debian.org/995357 [2] https://bugs.debian.org/1020575 [3] https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1990313/comments/5 ** Bug watch added: Debian Bug tracker #995357 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995357 ** Bug watch added: Debian Bug tracker #1020575 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020575 ** Patch added: "pipewire_0.3.57-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1992101/+attachment/5621965/+files/pipewire_0.3.57-1ubuntu1.debdiff ** Also affects: pipewire (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020575 Importance: Unknown Status: Unknown ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid ** Changed in: pipewire (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1992101 Title: No sound devices listed in Settings Status in gnome-control-center package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Confirmed Status in pipewire package in Debian: Unknown Bug description: Hi, in ubuntu 22.10 beta, there is no sound (only dummy output device is present in Settings->Sound). The systemctl --user status pipewire is: Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled) Active: active (running) since Thu 2022-10-06 22:51:13 CEST; 27min ago TriggeredBy: ● pipewire.socket Main PID: 10075 (pipewire) Tasks: 2 (limit: 115618) Memory: 4.7M CPU: 65ms CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service └─10075 /usr/bin/pipewire Oct 06 22:51:13 testosteron systemd[10061]: Started PipeWire Multimedia Service. Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: Can't find xdg-portal: (null) Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: found session bus but no portal Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: could not make thread 10106 realtime using RTKit: Permission denied The installed pipewire packages are: ii gstreamer1.0-pipewire:amd64 0.3.57-1 amd64GStreamer 1.0 plugin for the PipeWire multimedia server ii libpipewire-0.3-0:amd64 0.3.57-1 amd64libraries for the PipeWire multimedia server ii libpipewire-0.3-common0.3.57-1 all libraries for the PipeWire multimedia server - common files ii libpipewire-0.3-dev:amd64 0.3.57-1 amd64libraries for the PipeWire multimedia server - development ii libpipewire-0.3-modules:amd64 0.3.57-1 amd64libraries for the PipeWire multimedia server - modules ii pipewire:amd640.3.57-1 amd64audio and video processing engine multimedia server ii pipewire-alsa:amd64 0.3.57-1 amd64PipeWire ALSA plugin ii pipewire-audio-client-libraries 0.3.57-1 all transitional package for pipewire-alsa and pipewire-jack ii pipewire-bin 0.3.57-1 amd64PipeWire multimedia server - programs ii pipewire-jack:amd64 0.3.57-1 amd64PipeWire JACK plugin ii pipewire-media-session0.4.1-4 amd64example session manager for PipeWire ii pipewire-pulse0.3.57-1 amd64PipeWire PulseAudio daemon ii pipewire-tests0.3.57-1 amd64PipeWire multimedia server - tests and examples ii
[Desktop-packages] [Bug 1991936] Re: No AAC codec for Pipewire on Ubuntu Kinetic
** Bug watch added: Debian Bug tracker #1021370 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021370 ** Also affects: pipewire (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021370 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1991936 Title: No AAC codec for Pipewire on Ubuntu Kinetic Status in pipewire package in Ubuntu: Confirmed Status in pipewire package in Debian: Unknown Bug description: The AAC codec is not showing up in the sound settings when a device that is capable of that codec is connected, but other supported codecs do work.Tested using the Sony WH1000XM4 and other bluetooth devices that support the codec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1991936/+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 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing
Basically, pipewire-pulse.service wants pipewire-session-manager.service. pipewire-session-manager.service is an alias from both wireplumber.service and pipewire-media-session.service. To avoid this conflict, we need to remove pipewire-media-session.service during the remove step of the package, not only at the purge step. I am thinking about applying this fix. And a similar patch for wireplumber, just in case a user wants to move from wireplumber to pipewire-media-session for whatever reason. ** Patch added: "0001-Remove-pipewire-media-session.service-when-the-packa.patch" https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/1977564/+attachment/5595684/+files/0001-Remove-pipewire-media-session.service-when-the-packa.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1977564 Title: wireplumber conflicts with pipewire-media-session & needs fixing Status in pipewire-media-session package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Triaged Status in wireplumber package in Ubuntu: Triaged Status in pipewire-media-session package in Debian: Confirmed Bug description: This issue was reported on IRC and we should probably fix it before installing wireplumber by default so I'm setting the block-proposed tag. https://i.imgur.com/L5VFZO8.png wireplumber is apparently too forceful in how it enables PipeWire. Both Arch Linux and Debian had to https://archlinux.org/news/undone-replacement-of-pipewire-media- session-with-wireplumber/ Is it necessary for wireplumber to conflict with pipewire-media- session? Should we add Replaces? What files does pipewire-media-session need to clean up when it is removed? See https://salsa.debian.org/gnome-team/gnome-remote- desktop/-/commit/52799cfd for an example of how files that aren't technically conffiles can be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+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 1963836] Re: package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipe
This is a packaging bug with pipewire-pulse and pipewire-bin from the PPA, not with official packages. Please report it to the PPA maintainer. The manpage should be installed in pipewire-pulse where the related bin is, not in pipewire-bin. ** Changed in: pipewire (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1963836 Title: package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 Status in pipewire package in Ubuntu: Invalid Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 pipewire-pulse: Installed: 0.3.47-3~ubuntu22.04 Candidate: 0.3.48-1ubuntu1 Version table: 0.3.48-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages *** 0.3.47-3~ubuntu22.04 500 500 http://ppa.launchpad.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 22.04 Package: pipewire-pulse 0.3.47-3~ubuntu22.04 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Mar 6 20:05:39 2022 DpkgTerminalLog: Preparing to unpack .../00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb ... Unpacking pipewire-pulse (0.3.48-1ubuntu1) over (0.3.47-3~ubuntu22.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-tiBpp8/00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 DuplicateSignature: package:pipewire-pulse:0.3.47-3~ubuntu22.04 Unpacking pipewire-pulse (0.3.48-1ubuntu1) over (0.3.47-3~ubuntu22.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-tiBpp8/00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 ErrorMessage: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 InstallationDate: Installed on 2022-02-13 (20 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220116) Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu1 apt 2.3.15build1 SourcePackage: pipewire Title: package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1963836/+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 1966433] Re: Pipewire services start up on remote (ssh) logins
** Bug watch added: Debian Bug tracker #1005047 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005047 ** Also affects: pipewire (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005047 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1966433 Title: Pipewire services start up on remote (ssh) logins Status in pipewire package in Ubuntu: New Status in pipewire package in Debian: Unknown Bug description: This concern pipewire 0.3.48-1ubuntu1 in Ubuntu jammy. I log into an installed system via ssh, and I see skunk@darkstar:~$ ps auxww | grep skunk root 13771 0.5 0.1 19772 12224 ?Ss 07:35 0:00 sshd: skunk [priv] skunk 13774 5.4 0.1 17160 9940 ?Ss 07:35 0:00 /lib/systemd/systemd --user skunk 13775 0.0 0.0 25600 5292 ?S07:35 0:00 (sd-pam) skunk 13782 0.4 0.0 34460 6360 ?Ssl 07:35 0:00 /usr/bin/pipewire skunk 13783 0.4 0.0 18632 6856 ?Ssl 07:35 0:00 /usr/bin/pipewire-media-session skunk 13801 0.0 0.0 8412 4340 ?Ss 07:35 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only skunk 13831 0.0 0.0 19932 8052 ?S07:35 0:00 sshd: skunk@pts/0 skunk 13832 0.0 0.0 5256 4124 pts/0Ss 07:35 0:00 -bash skunk 13854 0.0 0.0 7692 3328 pts/0R+ 07:35 0:00 ps auxww skunk 13855 0.0 0.0 4024 2144 pts/0S+ 07:35 0:00 grep --color=auto skunk Pipewire is a multimedia service. It should not be running in a remote, non-graphical login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1966433/+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 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package
** Changed in: libimobiledevice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1721398 Title: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package Status in libimobiledevice package in Ubuntu: Fix Released Status in libimobiledevice package in Debian: Fix Released Bug description: Currently all of the other important utilities are included for installation on Ubuntu. However currently though a Ubuntu Linux user, is unable to perform an iOS device restore. In order to do so currently the user needs to have some way of running an up to date iTunes software with a usb connection to the iPhone, iPad or iPod Touch. Which is quite a hassle to go through in order to completely reload the device's iOS software. It would be much better if a binary compiled version of the software (idevicerestore and libirecovery) could be included in the utilities package. It would allow the Ubuntu user to be able to quickly and easily perform software update or device restore functions. Without the need for a virtual machine running a compatible version of Windows and iTunes etc. While also saving them from having to run Wine, its dependencies, iTunes and its own software requirements. All the would need is what is required to install idevicerestore and run its actions (the appropriate iOS release download image file). The code for idevice restore is available here (https://cgit.sukimashita.com/idevicerestore.git/) and the library from here (https://cgit.sukimashita.com/libirecovery.git/). Running Ubuntu 16.04.3 libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1721398/+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 1900679] Re: [snap] chromium spams dmesg
** Package changed: snap (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg Status in chromium-browser package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: [T okt 20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 Things like these just get repeated endlessly and very often, making any potential debugging very annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+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 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package
** Bug watch added: Debian Bug tracker #963042 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963042 ** Also affects: libimobiledevice (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963042 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1721398 Title: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package Status in libimobiledevice package in Ubuntu: Confirmed Status in libimobiledevice package in Debian: Unknown Bug description: Currently all of the other important utilities are included for installation on Ubuntu. However currently though a Ubuntu Linux user, is unable to perform an iOS device restore. In order to do so currently the user needs to have some way of running an up to date iTunes software with a usb connection to the iPhone, iPad or iPod Touch. Which is quite a hassle to go through in order to completely reload the device's iOS software. It would be much better if a binary compiled version of the software (idevicerestore and libirecovery) could be included in the utilities package. It would allow the Ubuntu user to be able to quickly and easily perform software update or device restore functions. Without the need for a virtual machine running a compatible version of Windows and iTunes etc. While also saving them from having to run Wine, its dependencies, iTunes and its own software requirements. All the would need is what is required to install idevicerestore and run its actions (the appropriate iOS release download image file). The code for idevice restore is available here (https://cgit.sukimashita.com/idevicerestore.git/) and the library from here (https://cgit.sukimashita.com/libirecovery.git/). Running Ubuntu 16.04.3 libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1721398/+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 1883457] Re: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.
** Package changed: snap (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1883457 Title: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else. Status in gimp package in Ubuntu: New Status in gnome-xcf-thumbnailer package in Ubuntu: New Status in gthumb package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in nemo package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Hi, On Ubuntu ( Budgie ) 20.04 when using Gimp as a snap, you’ll see thumbnails for .xcf files only « inside » Gimp and nowhere else ( Nemo, Nautilus, gThumb… ) I did a messy workaround for .xcf thumbnails to appear anywhere expected : I put all of my user’s thumbnails into ~/snap/gimp/common/.cache/thumbnails/ and now ~/.cache/thumbnails/ is a symlink targeting the first. You’d agree it’s absolutely a bad idea to store all of an user’s thumbnails into a particular subfolder of a particular snap. How tell my session to look for thumbnails not only in ~/.cache/thumbnails/ but also in any thumbnails folder inside ~/snap/ ? For references : ⋅ https://askubuntu.com/questions/1250031/gimp-snap-and-thumbnails-for-xcf-files ⋅ https://discourse.ubuntubudgie.org/t/gimp-as-a-snap-no-thumbnails-for-xcf-files-in-nemo-gthumb/3799 ⋅ https://forum.snapcraft.io/t/gimp-and-thumbnails-for-xcf-files/18131/3?u=coeur-noir ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2053949 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1883457/+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 1828664] Re: [snap] Broken link in theme directory
** Package changed: snap (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/1828664
Title:
[snap] Broken link in theme directory
Status in gnome-characters package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
New
Bug description:
Reproduce steps
---
1. $ snap install gnome-characters communitheme
2. logoff and select communitheme session at the greeter (probably needs a
reload of GDM or reboot, I'm running the wayland session but it also happened
of X)
3. $ snap run gnome-characters
Affected snaps:
gnome-characters
gnome-calculator
gnome-logs
gnome-system-monitor
libreoffice
evince
gnome-contacts
eog
Symptoms
I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which
broke at some point about two month ago. Screenshots are here:
https://askubuntu.com/q/1142291/40581
I found that ~/snap/gnome-characters/current/themes is a broken link
even when removing the respective snap folder for the app, removing
and then reinstalling the gnome-characters snap. This has worked
before, please take a look at this.
In the meantime I fixed this with the following commands, according
the the error message:
rm ~/snap/gnome-characters/current/.themes
cp -av /snap/communitheme/current/share/themes
~/snap/gnome-characters/current/.themes
Version
---
```
$ snap info {gnome-characters,communitheme} | grep -vE
"^(summary|license|contact|description|commands):"
name: gnome-characters
publisher: Canonical*
Characters is a simple utility application to find and
insert unusual characters.
- gnome-characters
snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
tracking: stable
refresh-date: heute um 04:19 CEST
channels:
stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
beta: ^
edge: v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
installed: v3.32.1+git1.2050bba(258) 15MB -
---
name: communitheme
publisher: Didier Roche (didrocks)
Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
package allows you to try out the theme on Ubuntu 18.04 LTS.
To try out the theme, install this package on Ubuntu 18.04 LTS, restart
your computer and select the "Ubuntu with communitheme snap" session from
the login screen.
More information is available at
https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
snap-id: Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
tracking: stable
refresh-date: 59 days ago, at 17:46 CET
channels:
stable:0.1 2019-03-13 (1768) 16MB -
candidate: ^
beta: ^
edge: 0.1 2019-05-08 (1799) 17MB -
installed: 0.1(1768) 16MB -
```
---
Further investigation
-
I'm also seeing broken links on an 19.04 machine where I'm not using
the Communitheme snap but the preinstalled Yaru packages. I'm trying
out the dark theme but all snaps launch with Adwaita instead.
```
$ snap list
Name Version Rev Tracking Publisher
Notes
android-studio 3.4.0.1875stablesnapcrafters
classic
canonical-livepatch 9.3.0 77stablecanonical*
-
core 16-2.38.1 6818 stablecanonical*
core
core18 20190409941 stablecanonical*
base
gedit3.30.2+git14.bed83e929 89stablecanonical*
-
gnome-3-26-1604 3.26.0.20190228 82stable/… canonical*
-
gnome-3-28-1804 3.28.0-10-gaa70833.aa70833 40stablecanonical*
-
gnome-calculator 3.32.1 406 stable/… canonical*
-
gnome-characters v3.32.1+git1.2050bba258 stablecanonical*
-
gnome-logs 3.32.0-4-ge8f3f37ca861stable/… canonical*
-
gtk-common-themes0.1-16-g2287c87 1198 stable/… canonical*
-
$ find snap/gnome-characters -xtype l
snap/gnome-characters/common/.cache/immodules/im-fcitx.so
snap/gnome-characters/common/.cache/immodules/im-wayland.so
snap/gnome-characters/common/.cache/immodules/im-broadway.so
snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
snap/gnome-characters/common/.cache/immodules/im-cedilla.so
snap/gnome-characters/common/.cache/immodules/im-ipa.so
snap/gnome-characters/common/.cache/immodules/im-xim.so
snap/gnome-characters/common/.cache/immodules/im-thai.so
snap/gnome-characters/common/.cache/immodules/im-multipress.so
[Desktop-packages] [Bug 1401126] Re: MTP phone does not mount
Support of Vodafone Smart 4 Turbo was added in libmtp 1.1.9 which is available since Xenial. https://github.com/libmtp/libmtp/commit/6d717c28417d5e674ed48f5346b6f12f52010b94 ** Package changed: mtp (Ubuntu) => libmtp (Ubuntu) ** Changed in: libmtp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1401126 Title: MTP phone does not mount Status in libmtp package in Ubuntu: Fix Released Bug description: My Android phone does not mount under Ubuntu 14.04 and I think its because MTP doesn't support it. The phone is a Vodafone Smart 4 Turbo: http://www.gsmarena.com/vodafone_smart_4_turbo-6507.php To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1401126/+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 874293] Re: Spyder color 3 not being connected (USB)
ColorSpyder devices are blacklisted from mtp-probe since a long time. This issue should not appear anymore. Please reopen otherwise. ** Changed in: libmtp (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/874293 Title: Spyder color 3 not being connected (USB) Status in libmtp package in Ubuntu: Fix Released Bug description: Since Oneiric now has the "color profile" thing prominently displayed as a feature, it's bad to see that a ColorSpyder 3 is not being "connected". This is what dmesg gives me: [ 40.901432] usb 2-1.3: USB disconnect, device number 59 [ 41.098439] usb 2-1.3: new full speed USB device number 60 using ehci_hcd [ 41.412572] usb 2-1.3: USB disconnect, device number 60 [ 41.614162] usb 2-1.3: new full speed USB device number 61 using ehci_hcd [ 41.924151] usb 2-1.3: USB disconnect, device number 61 [ 42.122027] usb 2-1.3: new full speed USB device number 62 using ehci_hcd [ 42.435650] usb 2-1.3: USB disconnect, device number 62 [ 42.633680] usb 2-1.3: new full speed USB device number 63 using ehci_hcd [ 42.947175] usb 2-1.3: USB disconnect, device number 63 [ 43.145420] usb 2-1.3: new full speed USB device number 64 using ehci_hcd [ 43.458660] usb 2-1.3: USB disconnect, device number 64 [ 43.656995] usb 2-1.3: new full speed USB device number 65 using ehci_hcd [ 43.970093] usb 2-1.3: USB disconnect, device number 65 [ 44.168804] usb 2-1.3: new full speed USB device number 66 using ehci_hcd And it just goed on and on as long as the Spyder is connected. It runs fine under Windows also using argyll and dispalgui, and it also runs fine using the 11.04 live cd environment (On the same machine). So that kinda rules out the spyder or the machine. If more is needed, let me know. This is a syslog excerpt: Oct 14 16:40:46 tribble mtp-probe: checking bus 2, device 32: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.3" Oct 14 16:40:46 tribble mtp-probe: bus: 2, device: 32 was not an MTP device Oct 14 16:40:46 tribble kernel: [ 410.420747] usb 2-1.3: USB disconnect, device number 32 Oct 14 16:40:47 tribble kernel: [ 410.620346] usb 2-1.3: new full speed USB device number 33 using ehci_hcd Oct 14 16:40:47 tribble mtp-probe: checking bus 2, device 33: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.3" Oct 14 16:40:47 tribble mtp-probe: bus: 2, device: 33 was not an MTP device Oct 14 16:40:47 tribble kernel: [ 410.931740] usb 2-1.3: USB disconnect, device number 33 Oct 14 16:40:47 tribble kernel: [ 411.131809] usb 2-1.3: new full speed USB device number 34 using ehci_hcd Oct 14 16:40:47 tribble mtp-probe: checking bus 2, device 34: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.3" Oct 14 16:40:47 tribble mtp-probe: bus: 2, device: 34 was not an MTP device Oct 14 16:40:47 tribble kernel: [ 411.443454] usb 2-1.3: USB disconnect, device number 34 Oct 14 16:40:48 tribble kernel: [ 411.643659] usb 2-1.3: new full speed USB device number 35 using ehci_hcd Oct 14 16:40:48 tribble mtp-probe: checking bus 2, device 35: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.3" Oct 14 16:40:48 tribble mtp-probe: bus: 2, device: 35 was not an MTP device Oct 14 16:40:48 tribble kernel: [ 411.954806] usb 2-1.3: USB disconnect, device number 35 Oct 14 16:40:48 tribble kernel: [ 412.155400] usb 2-1.3: new full speed USB device number 36 using ehci_hcd Oct 14 16:40:48 tribble mtp-probe: checking bus 2, device 36: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.3" Oct 14 16:40:48 tribble mtp-probe: bus: 2, device: 36 was not an MTP device Oct 14 16:40:48 tribble kernel: [ 412.466318] usb 2-1.3: USB disconnect, device number 36 Oct 14 16:40:49 tribble kernel: [ 412.663100] usb 2-1.3: new full speed USB device number 37 using ehci_hcd Oct 14 16:40:49 tribble mtp-probe: checking bus 2, device 37: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.3" Oct 14 16:40:49 tribble mtp-probe: bus: 2, device: 37 was not an MTP device ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: argyll 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:36:49 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: argyll UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/874293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1518866] Re: I am problem using my android device through mtp . whenever i connect it to pc it connects without issues . But whenever I tried opening a file such as pictures ,
** Changed in: libmtp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1518866 Title: I am problem using my android device through mtp . whenever i connect it to pc it connects without issues . But whenever I tried opening a file such as pictures , videos etc. it ended up in libmtp : unknown error . I am using ubuntu 15.10 . Status in libmtp package in Ubuntu: Invalid Bug description: I am having problem using my android device through mtp . whenever i connect it to pc it connects without issues . But whenever I tried opening a file such as pictures , videos etc. it ended up in libmtp : unknown error . I am using ubuntu 15.10 . And whenever I transfer the file to my pc's hard disk it works like it has to . Is there any way out or work-around for this ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1518866/+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 1813429] Re: Attempting to copy music (m4a) files from laptop to external device (LG G7 phone connected via usb cable) via mass copy-paste of a list of directories. Randomly, c
I'm wondering if it could be related to https://sourceforge.net/p/libmtp/bugs/1797/. Newer Linux kernels require an updated udev rule which is only available with libmtp 1.1.16 (not in cosmic). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1813429 Title: Attempting to copy music (m4a) files from laptop to external device (LG G7 phone connected via usb cable) via mass copy-paste of a list of directories. Randomly, copy/paste will stop and error reported. Status in libmtp package in Ubuntu: New Bug description: Steps to reproduce: 1) Plug phone into computer. 2) Copy a large number of directories with nested file structures to phone from computer hard drive, via Nautilus: [highlight files on computer, then ctrl-c; go to directory on phone, then ctrl-v]. Expected outcome: No copy errors. Actual Outcome: Usually, the expected outcome; randomly, Error: "Error while copying .m4a>. There was an error copying the file into mtp://LGE_LG-G710_LGG710PMd4...". Show more details : "File not found". Options: ["Cancel","Skip All","Skip"]. I can't force reproducibility, sometimes it won't complain, but larger copy/paste datasets correlate to more likely ending up with an error. Workarounds: At error, select 'Cancel'; delete the offending subdirectory/file from the phone; restart the copy-paste operation from the point of failure; repeat as necessary. lsb_release -rd: "Ubuntu 18.10" apt-cache policy nautilus: "nautilus: Installed: 1:3.26.4-0ubuntu7.1 Candidate: 1:3.26.4-0ubuntu7.1 Version table: *** 1:3.26.4-0ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.4-0ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages" ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 14:01:47 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+67+30'" InstallationDate: Installed on 2019-01-10 (16 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1813429/+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 1560452] Re: DUALi mtp-probe causes loop
3 years after, fixed: https://github.com/libmtp/libmtp/commit/ffa21bc17e
** Changed in: libmtp (Ubuntu)
Status: New => Fix Committed
** Changed in: libmtp (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/1560452
Title:
DUALi mtp-probe causes loop
Status in libmtp package in Ubuntu:
In Progress
Bug description:
Connecting a DUALi NFC reader causes a never ending loop of mtp-probe
operations, seen in the syslog
The following udev blacklist stops the problem:
/etc/udev/rules.d/10-duali-mtp-ignore.rules
ATTR{idVendor}=="1db2", ATTR{idProduct}=="0601", ENV{MTP_NO_PROBE}="1"
ATTR{idVendor}=="1db2", ATTR{idProduct}=="0600", ENV{MTP_NO_PROBE}="1"
# Don't mtp-probe any DUALi
#ATTR{idVendor}=="1db2", ENV{MTP_NO_PROBE}="1"
product 0601 is of a USB with a VENDOR interface that provides PCSC with a
driver
product 0600 is of a USB with a VENDOR interface.
There may be other products with this vendor Id that exhibit the
problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1560452/+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
