I tested the packages, and bash history is now properly retained during
a reboot :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send
For me the package in vivid-proposed works! :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send SIGTERM first on shutdown
Status in
Public bug reported:
In Ubuntu Vivid, using the 'reboot' command directly reboots the system in such
a way that the bash_history is not retained.
This bug has also been reported in Red Hat:
https://bugzilla.redhat.com/show_bug.cgi?id=1170765
There it was found that the cause of this bug is to
*** This bug is a duplicate of bug 1440417 ***
https://bugs.launchpad.net/bugs/1440417
** This bug has been marked a duplicate of bug 1440417
Old package, please move to stable 5.2
** This bug is no longer a duplicate of bug 1440417
Old package, please move to stable 5.2
** This bug
I also experience this problem, often it is triggered when using Chrome
and opening a new tab or window.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1509846
Title:
Public bug reported:
Hi,
could you please enable python3 builds for the new protobuf3 version?
A patch for it is already floating around:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836821#10
I tested it in my PPA, just needed to add python3-six as an extra
explicit dependency (for some
I have the same issue on Ubuntu 16.10 and 17.04, also with Intel
hardware and displayport. Nothing weird in dmesg though :-/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
This also affects the installation of popular 3rd party application
Spotify: https://community.spotify.com/t5/Desktop-
Linux/libcurl4/m-p/4411011#M15902
I wonder, Debian still has libcurl3 versioned library/symbols in their
'unstable' repo, their libcurl4 is only in experimental yet. I
understand
Yes, but, it are symlinks that could trivially be changed:
ls -al /usr/lib/x86_64-linux-gnu/libcurl.so.*
lrwxrwxrwx 1 root root 12 jan 25 10:19
/usr/lib/x86_64-linux-gnu/libcurl.so.3 -> libcurl.so.4
lrwxrwxrwx 1 root root 16 jan 25 10:19
/usr/lib/x86_64-linux-gnu/libcurl.so.4 ->
The reason they conflict, is that both bundle libcurl.so.3 and
libcurl.so.4, which are in fact just symlinks to the actual library.
The best would be to release a new version of libcurl3 that does NOT have a
libcurl.so.4 symlink, ONLY the libcurl.so.3 one.
And then provide a version of libcurl4
If they were compiled against libcurl.so.4 I assume they would be compiled
against abi-4 of libcurl, right?
AFAIK the supplying of libcurl.so.4 by libcurl3 was a trick by Debian by
keeping the same exposed symbols, which kept abi-3 and abi-4 the same.
So I'd assume even though those packages
Ok, Igor you are right about them being linked to libcurl.so.4 while
assuming abi-3; this is a very unpleasant situation that indeed cannot
even be resolved with adjusting the symlinks :-/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
For spotify this trick doesn't work, it complains about the changed
CURLOPT_SSL_CTX_FUNCTION symbol when starting the application.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
Thanks for the hint, I use their snap-package as workaround, as hinted by their
developer:
https://community.spotify.com/t5/Desktop-Linux/libcurl4/m-p/4411011#M15902
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in
Public bug reported:
Woud it please be possible to upgrade Protobuf to 3.19.1 (which is
already in Debian) for upcoming Ubuntu LTS 22.04 ?
All packages that use protobuf as dependency (which are quite some) will
need a rebuild, so it is important to organize a transition on time.
** Affects:
** Changed in: protobuf (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1952899
Title:
Upgrade to 3.19.1 for LTS
Status in
16 matches
Mail list logo
