[Touch-packages] [Bug 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing

2022-06-08 Thread Dylan Aïssi
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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

2021-11-25 Thread Dylan Aïssi
** Changed in: libimobiledevice (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1835604] Re: usbmuxd: libssl.so.1.0.0: cannot open shared object file

2020-07-12 Thread Dylan Aïssi
It seems you have installed usbmuxd from a ppa or manually. It's
installed in /usr/local/sbin/ whereas in official package the location
is /usr/sbin/

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

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

Title:
  usbmuxd: libssl.so.1.0.0: cannot open shared object file

Status in usbmuxd package in Ubuntu:
  Invalid

Bug description:
  After upgrading from xenial to disco, I got the follwing error:

  /usr/local/sbin/usbmuxd: error while loading shared libraries:
  libssl.so.1.0.0: cannot open shared object file: No such file or
  directory

  ldd -r /usr/local/sbin/usbmuxd
linux-vdso.so.1 (0x7fffa2f8a000)
libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 
(0x7f00e2d7a000)
libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6 
(0x7f00e2b57000)
libplist.so.3 => /usr/local/lib/libplist.so.3 (0x7f00e2948000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f00e2927000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f00e273c000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f00e2716000)
libssl.so.1.0.0 => not found
libcrypto.so.1.0.0 => not found
libusbmuxd.so.4 => /usr/local/lib/libusbmuxd.so.4 (0x7f00e250c000)
/lib64/ld-linux-x86-64.so.2 (0x7f00e31d4000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f00e2501000)
  undefined symbol: ERR_remove_thread_state, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_CTX_use_RSAPrivateKey, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: CRYPTO_cleanup_all_ex_data, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: EVP_PKEY_free, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: PEM_write_bio_X509, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: X509_set_notAfter, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: ASN1_INTEGER_set, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: X509_set_notBefore, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: RSA_new, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: BIO_s_mem, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: RSA_free, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_set_bio, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_COMP_get_compression_methods, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_read, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: X509V3_EXT_conf_nid, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: BN_new, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: CRYPTO_set_id_callback, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: BIO_new_mem_buf, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_write, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_shutdown, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: X509V3_EXT_cleanup, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: ASN1_TIME_free, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: EVP_cleanup, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: BIO_s_socket, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: EVP_PKEY_assign, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_set_verify, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: PEM_read_bio_X509, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: X509_free, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_set_connect_state, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: X509_EXTENSION_free, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_do_handshake, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: TLSv1_method, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined symbol: SSL_CTX_free, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
  undefined sym

[Touch-packages] [Bug 1363583] Re: usbmuxd is not compatible with libusbmuxd2 in ubuntu 14.10

2020-07-09 Thread Dylan Aïssi
Ubuntu 14.10 is EOL since July 2015. New versions of Ubuntu have new
versions of usbmuxd and libusbmuxd

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

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

Title:
  usbmuxd is not compatible with libusbmuxd2 in ubuntu 14.10

Status in usbmuxd package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 14.10, the version of libusbmuxd2 is 1.0.9, but usbmuxd is still 
1.0.8.
  usbmuxd 1.0.8 does not support the new commands used in libusbmuxd2 1.0.9
  Any program which use libusbmuxd2 will simply crash.

  $ ideviceinfo 
  ideviceinfo: plist.c:194: plist_copy_node: Assertion `data' failed.
  Aborted

  the debug output of usbmuxd:
  $ sudo usbmuxd -v -f -u
  [15:29:58.274][3] usbmuxd v1.0.8 starting up
  [15:29:58.274][4] Creating socket
  [15:29:58.274][4] Initializing USB
  [15:29:58.276][4] Found new device with v/p 05ac:129a at 2-7
  [15:29:58.276][4] Found interface 1 with endpoints 04/85 for device 2-7
  [15:29:58.277][4] Using wMaxPacketSize=512 for device 2-7
  [15:29:58.277][3] Connecting to new device on location 0x20007 as ID 1
  [15:29:58.277][4] 1 device detected
  [15:29:58.277][3] Initialization complete
  [15:29:58.278][3] Connected to v1.0 device 1 on location 0x20007 with serial 
number ***
  [15:30:07.646][4] New client on fd 14
  [15:30:07.646][1] Unexpected command 'ListDevices' received!
  [15:30:07.646][4] Client 14 connection closed
  [15:30:07.646][4] Disconnecting client fd 14
  [15:30:07.647][4] New client on fd 14
  [15:30:07.747][4] Client 14 connection closed
  [15:30:07.747][4] Disconnecting client fd 14
  [15:30:07.747][4] New client on fd 14
  [15:30:07.754][4] New client on fd 15
  [15:30:07.755][1] Unexpected command 'ReadPairRecord' received!
  [15:30:07.755][4] New client on fd 16
  [15:30:07.755][1] Unexpected command 'ReadPairRecord' received!
  [15:30:07.757][4] Disconnecting client fd 14
  [15:30:07.757][4] Client 15 connection closed
  [15:30:07.757][4] Disconnecting client fd 15
  [15:30:07.757][4] Client 16 connection closed
  [15:30:07.757][4] Disconnecting client fd 16

  I complied the latest source from 
https://github.com/libimobiledevice/usbmuxd, everything works.
  $ sudo usbmuxd -v -f -u
  [15:38:13.038][3] usbmuxd v1.0.9 starting up
  [15:38:13.038][4] Creating socket
  [15:38:13.038][4] Initializing USB
  [15:38:13.040][4] Found new device with v/p 05ac:129a at 2-7
  [15:38:13.041][4] Found interface 1 with endpoints 04/85 for device 2-7
  [15:38:13.042][4] Using wMaxPacketSize=512 for device 2-7
  [15:38:13.042][3] Connecting to new device on location 0x20007 as ID 1
  [15:38:13.042][4] 1 device detected
  [15:38:13.042][3] Initialization complete
  [15:38:13.042][3] Connected to v2.0 device 1 on location 0x20007 with serial 
number ***
  [15:38:13.042][4] preflight_worker_handle_device_add: Starting preflight on 
device ***...
  [15:38:13.043][4] New client on fd 16
  [15:38:13.045][4] device_control_input: 
AppleUSBDeviceMux::handleConnectResult new session 0x8bc4a000 established 
62078<-lo0->49706 62078<-usb->1
  [15:38:13.050][4] New client on fd 18
  [15:38:13.054][4] New client on fd 20
  [15:38:13.184][4] preflight_worker_handle_device_add: StartSession success 
for device ***
  [15:38:13.184][4] preflight_worker_handle_device_add: Finished preflight on 
device ***
  [15:38:13.188][4] Disconnecting client fd 16
  [15:38:13.189][4] device_control_input: void 
AppleUSBDeviceMux::handleMuxTCPInput(__mbuf*) received reset, closing 0x8bc4a000
  [15:38:30.383][4] New client on fd 15
  [15:38:30.383][4] New client on fd 16
  [15:38:30.383][4] Client 15 connection closed
  [15:38:30.383][4] Disconnecting client fd 15

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

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


[Touch-packages] [Bug 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

2020-07-07 Thread Dylan Aïssi
** 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1261459] Re: Unable to connect using explicit FTP over TLS

2019-05-06 Thread Dylan Aïssi
Fixed since filezilla 3.9.0.1-0.1 (at least since Xenial).

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

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

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

Title:
  Unable to connect using explicit FTP over TLS

Status in filezilla package in Ubuntu:
  Fix Released
Status in gnutls26 package in Ubuntu:
  Invalid

Bug description:
  Since saucy, i am unable to connect to FTPs with tls using "explicit FTP over 
TLS".
  error message:

  Command:  AUTH TLS
  Response: 234 AUTH TLS successful
  Status:   Initializing TLS...
  Error:GnuTLS error -89: Public key signature verification has failed.
  Error:Could not connect to server


  
  Other clients work well, also downloading the precompiled binary from the 
filezilla HP works, seems an ubuntu specific bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: filezilla 3.7.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Dec 16 18:10:59 2013
  InstallationDate: Installed on 2013-12-13 (2 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: filezilla
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1401126] Re: MTP phone does not mount

2019-04-22 Thread Dylan Aïssi
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 Ubuntu
Touch seeded packages, which is subscribed to mtp 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp