[Desktop-packages] [Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a
I guess there is only one case where the current "fix" would help. If
someone had some library providing libungif in a different place, the
broken symlinks in /usr/lib might take precedence, thus hiding the
correct files.
In my opinion, removing the dangling symlinks is a slight improvement on
the current situation and the risk of breaking something is very low. On
the hand, I do not know whethere there are other considerations
regarding a SRU in addition to the potential for regressions (which is
low in this case).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to giflib in Ubuntu.
https://bugs.launchpad.net/bugs/1337898
Title:
Invalid symlinks for libungif.so and libungif.a
Status in giflib package in Ubuntu:
Fix Released
Status in giflib source package in Trusty:
Fix Committed
Status in giflib package in Debian:
Unknown
Bug description:
Impact
==
Linking programs that need libungif ("-lungif") will fail.
Test Case
=
apt-get install build-essential libgif-dev
cat >>test.c EOF
int main(int argc, char **argv) {
return 0;
}
EOF
gcc -lungif test.c
GCC will fail with "/usr/bin/ld: cannot find -lungif" on affected
systems.
Regression Potential
None, just removing some dangling symlinks that couldn't work any way.
Original Bug Report
===
In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in
libgif-dev 4.1.6-11:
Symbol links for libungif.a, libungif.la, and libungif.so are created
in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6
respectively. However, these files are not in /usr/lib but in
/usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid.
I suggest fixing this by placing the symbol links in the same
directory as the target files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+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 1337898] Re: Invalid symlinks for libungif.so and libungif.a
I tested the package from trusty-proposed, but I am not sure whether the
issue can be considered fixed.
In fact, the dangling symlinks have been removed, but they have not been
added in the right place. This means that software depending on libungif
will still not compile.
The question is, whether this is by intention: Should libgif provide an
alias for libungif (because it effectively provides the functionality of
libungif) or is it an intentional choice not to provide libungif and
should all software depending on it be changed to depend on libgif
instead?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to giflib in Ubuntu.
https://bugs.launchpad.net/bugs/1337898
Title:
Invalid symlinks for libungif.so and libungif.a
Status in giflib package in Ubuntu:
Fix Released
Status in giflib source package in Trusty:
Fix Committed
Bug description:
Impact
==
Linking programs that need libungif ("-lungif") will fail.
Test Case
=
apt-get install build-essential libgif-dev
cat >>test.c EOF
int main(int argc, char **argv) {
return 0;
}
EOF
gcc -lungif test.c
GCC will fail with "/usr/bin/ld: cannot find -lungif" on affected
systems.
Regression Potential
None, just removing some dangling symlinks that couldn't work any way.
Original Bug Report
===
In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in
libgif-dev 4.1.6-11:
Symbol links for libungif.a, libungif.la, and libungif.so are created
in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6
respectively. However, these files are not in /usr/lib but in
/usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid.
I suggest fixing this by placing the symbol links in the same
directory as the target files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+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 1337898] Re: Invalid symlinks for libungif.so and libungif.a
I updated the Impact and Test Case sections of this bug's description. I
hope this better fits the purpose of describing the actual impact on
users.
** Description changed:
Impact
==
- libgif-dev in Ubuntu 14.04 LTS depends on libgif4 and has these symlinks:
- /usr/lib/libungif.a -> libgif.a
- /usr/lib/libungif.so -> libgif.so.4.1.6
- /usr/lib/x86_64-linux-gnu/libgif.so -> libgif.so.4.1.6
- /usr/lib/libungif.la -> libgif.la
-
- libgif4 has these files:
- /usr/lib/x86_64-linux-gnu/libgif.so.4.1.6
- /usr/lib/x86_64-linux-gnu/libgif.so.4 -> libgif.so.4.1.6
-
- Only the 3rd symlink (the multiarch one) in libgif-dev is correct. The
- others are dangling.
-
- This was caused by an obsolete debian/libgif-dev.links
+ Linking programs that need libungif ("-lungif") will fail.
Test Case
=
- Verify that libgif-dev only includes the one working symlink:
- /usr/lib/x86_64-linux-gnu/libgif.so -> libgif.so.4.1.6
+ apt-get install build-essential libgif-dev
+ cat >>test.c EOF
+ int main(int argc, char **argv) {
+ return 0;
+ }
+ EOF
+ gcc -lungif test.c
+
+ GCC will fail with "/usr/bin/ld: cannot find -lungif" on affected
+ systems.
Regression Potential
None, just removing some dangling symlinks that couldn't work any way.
Original Bug Report
===
In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in
libgif-dev 4.1.6-11:
Symbol links for libungif.a, libungif.la, and libungif.so are created in
/usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6
respectively. However, these files are not in /usr/lib but in
/usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid.
I suggest fixing this by placing the symbol links in the same directory
as the target files.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to giflib in Ubuntu.
https://bugs.launchpad.net/bugs/1337898
Title:
Invalid symlinks for libungif.so and libungif.a
Status in giflib package in Ubuntu:
Fix Released
Status in giflib source package in Trusty:
Triaged
Bug description:
Impact
==
Linking programs that need libungif ("-lungif") will fail.
Test Case
=
apt-get install build-essential libgif-dev
cat >>test.c EOF
int main(int argc, char **argv) {
return 0;
}
EOF
gcc -lungif test.c
GCC will fail with "/usr/bin/ld: cannot find -lungif" on affected
systems.
Regression Potential
None, just removing some dangling symlinks that couldn't work any way.
Original Bug Report
===
In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in
libgif-dev 4.1.6-11:
Symbol links for libungif.a, libungif.la, and libungif.so are created
in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6
respectively. However, these files are not in /usr/lib but in
/usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid.
I suggest fixing this by placing the symbol links in the same
directory as the target files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+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 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
The workaround suggested by Ikuya Awashiro (setting the gateway for the route to 0.0.0.0) does not work for me. The problem persits even after applying this workaround. The VPN connection is only established when all static routes are deleted from the configuration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Confirmed Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on a local network while using Wifi for basic internet. (Physical network locked down, no Internet access available) I've attached a screenshot showing the routes. These routes were working great in 14.04 (And prior releases of Ubuntu). However, upon upgrading to 16.04, I noticed this connection would no longer "connect". It would just silently fail. I noticed that if I deleted my custom routes, it would work, but I need those in order to connect to my required network services. When I try to connect with the routes in place, the connection silently fails in the NetworkManager UI (I get no error message in the UI) but I took a look at syslog and found these: Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 'config-failed') [70 120 4] Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7289] device (enp0s31f6): Activation: failed for connection 'Windstream' Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7309] device (enp0s31f6): state change: failed -> disconnected (reason 'none') [120 30 0] Now, if I remove the custom routes from the UI, then I can connect. I them manually add the routes using the "ip" command: sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6 sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6 This is able to add the routes successfully. So there has to be some problem in the new implementation of NetworkManager in 16.04, because these routes worked in 14.04 and they still work in 16.04 if I just manually add them from the command line. For now I can work around this issue by manually adding these routes from the command line every time I connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+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 1337898] Re: Invalid symlinks for libungif.so and libungif.a
@sds: Yes, they exist, but in /usr/lib, while they should be in /usr/lib/x86_64-linux-gnu (depending on the platform). As libgif.* is not in /usr/lib, the symbol links point to files that do not exist. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a Status in giflib package in Ubuntu: Fix Released Bug description: In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in libgif-dev 4.1.6-11: Symbol links for libungif.a, libungif.la, and libungif.so are created in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6 respectively. However, these files are not in /usr/lib but in /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid. I suggest fixing this by placing the symbol links in the same directory as the target files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+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 1337898] Re: Invalid symlinks for libungif.so and libungif.a
Are there any plans to backport this change to giflib-4.1.6-11 on trusty? Considering that trusty is still going to be supported for more than three years, it might make sense to backport this bugfix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a Status in giflib package in Ubuntu: Fix Released Bug description: In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in libgif-dev 4.1.6-11: Symbol links for libungif.a, libungif.la, and libungif.so are created in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6 respectively. However, these files are not in /usr/lib but in /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid. I suggest fixing this by placing the symbol links in the same directory as the target files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+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 1337898] [NEW] Invalid symlinks for libungif.so and libungif.a
Public bug reported: In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in libgif-dev 4.1.6-11: Symbol links for libungif.a, libungif.la, and libungif.so are created in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6 respectively. However, these files are not in /usr/lib but in /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid. I suggest fixing this by placing the symbol links in the same directory as the target files. ** Affects: giflib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to giflib in Ubuntu. https://bugs.launchpad.net/bugs/1337898 Title: Invalid symlinks for libungif.so and libungif.a Status in “giflib” package in Ubuntu: New Bug description: In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in libgif-dev 4.1.6-11: Symbol links for libungif.a, libungif.la, and libungif.so are created in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6 respectively. However, these files are not in /usr/lib but in /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid. I suggest fixing this by placing the symbol links in the same directory as the target files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+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
