[Bug 1804166] Re: Asks for "unnamed" key instead of real name
** Description changed: Hello, Whenever I try to ssh into a server for the first time, a GUI popup asks for the key password: "An application wants access to the private key "Unnamed", but it is locked:" + + + Processes: + + + ``` + 2340 ?SLl0:00 /usr/bin/gnome-keyring-daemon --daemonize --login + 6660 ?S 0:00 \_ /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh + 23894 ?Ss 0:00 \_ /usr/bin/ssh-add /home/philippe/.ssh/sysadmin + 23895 ?SL 0:00 \_ /usr/lib/gcr/gcr-ssh-askpass Enter passphrase for /home/philippe/.ssh/sysadmin: + + ``` I can then enter my password, but I have to guess which key it is: ``` -rw--- 1 philippe philippe 1.7K Jan 27 2015 id_rsa -rw-rw-r-- 1 philippe philippe 10 Jan 27 2015 id_rsa.keystore -rw-r--r-- 1 philippe philippe 407 Jan 27 2015 id_rsa.pub -rw--- 1 philippe philippe 228K Nov 14 14:01 known_hosts -rw--- 1 philippe philippe 228K Nov 9 16:46 known_hosts.old -rw--- 1 philippe philippe 1.8K Jan 27 2015 support -rw--- 1 philippe philippe 381 Jan 27 2015 support.pub -rw--- 1 philippe philippe 1.8K Jan 27 2015 sysadmin -rw--- 1 philippe philippe 381 Jan 27 2015 sysadmin.pub ``` I could be the "support" or the "sysadmin" key, but because the dialog only diplay "Unnamed" I have to remember which server uses which. I think it should display "sysadmin" or "support" instead of "Unnamed". ``` philippe@pv-desktop:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic philippe@pv-desktop:~$ uname -a Linux pv-desktop 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux philippe@pv-desktop:~$ gnome-keyring version gnome-keyring: 3.28.0.2 ``` I tried using `seahorse` to see if there was a way to edit this "Unnamed" information, but there is not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804166 Title: Asks for "unnamed" key instead of real name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1804166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804166] [NEW] Asks for "unnamed" key instead of real name
Public bug reported: Hello, Whenever I try to ssh into a server for the first time, a GUI popup asks for the key password: "An application wants access to the private key "Unnamed", but it is locked:" I can then enter my password, but I have to guess which key it is: ``` -rw--- 1 philippe philippe 1.7K Jan 27 2015 id_rsa -rw-rw-r-- 1 philippe philippe 10 Jan 27 2015 id_rsa.keystore -rw-r--r-- 1 philippe philippe 407 Jan 27 2015 id_rsa.pub -rw--- 1 philippe philippe 228K Nov 14 14:01 known_hosts -rw--- 1 philippe philippe 228K Nov 9 16:46 known_hosts.old -rw--- 1 philippe philippe 1.8K Jan 27 2015 support -rw--- 1 philippe philippe 381 Jan 27 2015 support.pub -rw--- 1 philippe philippe 1.8K Jan 27 2015 sysadmin -rw--- 1 philippe philippe 381 Jan 27 2015 sysadmin.pub ``` I could be the "support" or the "sysadmin" key, but because the dialog only diplay "Unnamed" I have to remember which server uses which. I think it should display "sysadmin" or "support" instead of "Unnamed". ``` philippe@pv-desktop:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic philippe@pv-desktop:~$ uname -a Linux pv-desktop 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux philippe@pv-desktop:~$ gnome-keyring version gnome-keyring: 3.28.0.2 ``` I tried using `seahorse` to see if there was a way to edit this "Unnamed" information, but there is not. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, Whenever I try to ssh into a server for the first time, the gnome ssh- askpass displays this: - `An application wants access to the private key "Unnamed", but it is - locked:` + "An application wants access to the private key "Unnamed", but it is + locked:" I can then enter my password, but I have to guess which key it is: ``` -rw--- 1 philippe philippe 1.7K Jan 27 2015 id_rsa -rw-rw-r-- 1 philippe philippe 10 Jan 27 2015 id_rsa.keystore -rw-r--r-- 1 philippe philippe 407 Jan 27 2015 id_rsa.pub -rw--- 1 philippe philippe 228K Nov 14 14:01 known_hosts -rw--- 1 philippe philippe 228K Nov 9 16:46 known_hosts.old -rw--- 1 philippe philippe 1.8K Jan 27 2015 support -rw--- 1 philippe philippe 381 Jan 27 2015 support.pub -rw--- 1 philippe philippe 1.8K Jan 27 2015 sysadmin -rw--- 1 philippe philippe 381 Jan 27 2015 sysadmin.pub ``` I could be the "support" or the "sysadmin" key, but because the dialog only diplay "Unnamed" I have to remember which server uses which. I think it should display "sysadmin" or "support" instead of "Unnamed". ``` philippe@pv-desktop:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic philippe@pv-desktop:~$ uname -a Linux pv-desktop 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux philippe@pv-desktop:~$ gnome-keyring version gnome-keyring: 3.28.0.2 ``` ** Description changed: Hello, - Whenever I try to ssh into a server for the first time, the gnome ssh- - askpass displays this: + Whenever I try to ssh into a server for the first time, the a GUI popup + asks for the key password: "An application wants access to the private key "Unnamed", but it is locked:" I can then enter my password, but I have to guess which key it is: ``` -rw--- 1 philippe philippe 1.7K Jan 27 2015 id_rsa -rw-rw-r-- 1 philippe philippe 10 Jan 27 2015 id_rsa.keystore -rw-r--r-- 1 philippe philippe 407 Jan 27 2015 id_rsa.pub -rw--- 1 philippe philippe 228K Nov 14 14:01 known_hosts -rw--- 1 philippe philippe 228K Nov 9 16:46 known_hosts.old -rw--- 1 philippe philippe 1.8K Jan 27 2015 support -rw--- 1 philippe philippe 381 Jan 27 2015 support.pub -rw--- 1 philippe philippe 1.8K Jan 27 2015 sysadmin -rw--- 1 philippe philippe 381 Jan 27 2015 sysadmin.pub ``` I could be the "support" or the "sysadmin" key, but because the dialog only diplay "Unnamed" I have to remember which server uses which. I think it should display "sysadmin" or "support" instead of "Unnamed". ``` philippe@pv-desktop:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic philippe@pv-desktop:~$ uname -a Linux pv-desktop 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux philippe@pv-desktop:~$ gnome-keyring version gnome-keyring: 3.28.0.2 ``` ** Description changed: Hello, - Whenever I try to ssh into a server for the first time, the a GUI popup - asks for the key password:
[Bug 1793937] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3
Duplicate of https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1791542 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793937 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804166] Re: Asks for "unnamed" key instead of real name
Ok, with seahorse you can actually rename the key, but it's original name is not "Unnamed" it is "Secure Shell Key". ** Changed in: gnome-keyring (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804166 Title: Asks for "unnamed" key instead of real name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1804166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853977] [NEW] nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Public bug reported: Hello, When installing `nvidia-340` there is an error is the postinst script: philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340 Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade. Need to get 0 B/51.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 309892 files and directories currently installed.) Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. (snip) Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-340-340.107 DKMS files... Building for 4.15.0-70-generic Building for architecture x86_64 Building initial module for 4.15.0-70-generic Done. The comment at https://askubuntu.com/questions/969352/uninstalling-and- then-reinstalling-nvidia-384-kills-colord tells us that /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as expected. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: - Hello, When installing `nvidia-340` there is an error is the postinst script: philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340 Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade. Need to get 0 B/51.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 309892 files and directories currently installed.) Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. - Removing all DKMS Modules - Done. - Stopping previous nvidia-persistenced - nvidia-persistenced: no process found - Done. - diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 - diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 - diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/x86_64-linux-gnu/libGL.so.distrib by nvidia-340 - diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/i386-linux-gnu/libGL.so.distrib by nvidia-340 - diversion of /usr/lib/x86_64-linux-gnu/libEGL.so.1 to /usr/lib/x86_64-linux-gnu/libEGL.so.1.distrib by nvidia-340 - diversion of /usr/lib/i386-linux-gnu/libEGL.so.1 to /usr/lib/i386-linux-gnu/libEGL.so.1.distrib by nvidia-340 - diversion of /usr/lib/x86_64-linux-gnu/libEGL.so to /usr/lib/x86_64-linux-gnu/libEGL.so.distrib by nvidia-340 - diversion of /usr/lib/i386-linux-gnu/libEGL.so to /usr/lib/i386-linux-gnu/libEGL.so.distrib by nvidia-340 - diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so to /usr/lib/x86_64-linux-gnu/libGLESv2.so.distrib by nvidia-340 - diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to /usr/lib/i386-linux-gnu/libGLESv2.so.distrib by nvidia-340 - diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.distrib by nvidia-340 - diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/i386-linux-gnu/libGLESv2.so.2.distrib by nvidia-340 - diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.distrib by nvidia-340 - diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to /usr/lib/i386-linux-gnu/libGLESv1_CM.so.distrib by nvidia-340 - diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.distrib by nvidia-340 - diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.distrib by nvidia-340 - Unpacking nvidia-340 (340.107-0ubuntu0.18.04.4) over (340.107-0ubuntu0.18.04.4) ... + (snip) Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-34
[Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Note that the fix was mentionned in the original report. I usually don't comment for this but I thought if there was more comments more people would notice :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853977 Title: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614080] [NEW] PATH contains dot when PATH is unset before running bash
Public bug reported: On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - bash PATH contains dot when PATH is unset + PATH contains dot when PATH is unset before running bash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1614080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
The problem seems to have been introduced in 14.04 philippe@pv-desktop:~$ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i; docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'"; done 12.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 12.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.04 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 13.10 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 14.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 14.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 15.10 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. 16.04 /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1614080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
** Package changed: ubuntu => bash (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
** Tags removed: trusyt ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
Ah, found the same bug in Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=781367 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
For information this bug does not happen on Fedora/CentOS philippe@pv-desktop:~$ docker run -it --rm fedora:latest bash -c "unset PATH; /bin/bash -c 'echo \$PATH'" /usr/local/bin:/usr/bin ** Bug watch added: Debian Bug tracker #781367 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781367 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436979] Re: BQ-Ubuntuphone: can not copy Text from SMS
This is very annoying, it makes it very hard to forward SMSes to someone else. This is the bare minimum to provide if you don't supply a "forward" option when listing the messages options (only "delete" is available at the moment). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436979 Title: BQ-Ubuntuphone: can not copy Text from SMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1436979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5
Same in Switzerland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439101 Title: impossible receive MMS any operator on bq aquaris E4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1439101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453538] Re: Invisible mouse pointer
FWIW, ever since I installed the correct NVIDIA drivers this bug stopped happening. I doubt it's related but who knows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453538 Title: Invisible mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1453538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1363314] Re: Remove dependency of qtmultimedia on gst0.10
Just to be clear, the package currently causing problems in trusty and above is "libqt5multimedia5-plugins": philippe@philippe-desktop:~$ apt-cache rdepends libgstreamer0.10-0 | grep qt qtgstreamer-plugins libqtmultimediakit1 libqtgstreamerutils-0.10-0 libqtgstreamer-0.10-0 libqt5multimedia5-plugins This bug prevents any Qt app using both QtWebkit and QtMultimedia to function. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363314 Title: Remove dependency of qtmultimedia on gst0.10 To manage notifications about this bug go to: https://bugs.launchpad.net/dropping-letters/+bug/1363314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
