[Bug 1890332] Re: apt update fails on docker arm container 20.04
no, wait, that is a different error message. When I run unprivileged, I get Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease At least one invalid signature was encountered. Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease At least one invalid signature was encountered. Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease At least one invalid signature was encountered. Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease At least one invalid signature was encountered. Reading package lists... Done W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: At least one invalid signature was encountered. E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: At least one invalid signature was encountered. E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: At least one invalid signature was encountered. E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890332] Re: apt update fails on docker arm container 20.04
I have verified that the date is indeed the problem. When I run an ubuntu container privileged, the container has the correct date and apt update succeeds. But when I run the container privileged and set the date to 1971, then I get that same error message from apt update. Therefore, this bug is a duplicate of bug #1896443 pi@raspberrypi:~ $ docker run --privileged -it ubuntu bash root@ad897025c4b7:/# date "+%Y-%m-%d %H:%M:%S" -s "1971-01-01 00:00:00" 1971-01-01 00:00:00 root@ad897025c4b7:/# apt update Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [111 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [98.3 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [107 kB] Reading package lists... Done E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/focal/InRelease is not valid yet (invalid for another 18010d 17h 33min 0s). Updates for this repository will not be applied. E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/focal-updates/InRelease is not valid yet (invalid for another 18222d 10h 50min 54s). Updates for this repository will not be applied. E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/focal-backports/InRelease is not valid yet (invalid for another 18222d 10h 51min 16s). Updates for this repository will not be applied. E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/focal-security/InRelease is not valid yet (invalid for another 18222d 10h 50min 42s). Updates for this repository will not be applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890332] Re: apt update fails on docker arm container 20.04
So now I manually downloaded libseccomp2_2.5.0-3_armhf.deb, copied it into the container and tried to install it from there. This didn't work either: Step 7/27 : RUN dpkg --force-all -P libseccomp2 ---> Running in bf8c3eba1b94 dpkg: libseccomp2:armhf: dependency problems, but removing anyway as you requested: apt depends on libseccomp2 (>= 2.4.2). (Reading database ... 4115 files and directories currently installed.) Removing libseccomp2:armhf (2.4.3-1ubuntu3.20.04.3) ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Removing intermediate container bf8c3eba1b94 ---> 46d72c3e2384 Step 8/27 : RUN dpkg -i /libseccomp2_2.5.0-3_armhf.deb ---> Running in 2636514aa37f tar: ./control: Cannot utime: Operation not permitted tar: ./md5sums: Cannot utime: Operation not permitted tar: ./shlibs: Cannot utime: Operation not permitted tar: ./symbols: Cannot utime: Operation not permitted tar: ./triggers: Cannot utime: Operation not permitted tar: .: Cannot utime: Operation not permitted tar: Exiting with failure status due to previous errors dpkg-deb: error: tar subprocess returned error exit status 2 dpkg: error processing archive /libseccomp2_2.5.0-3_armhf.deb (--install): dpkg-deb --control subprocess returned error exit status 2 Errors were encountered while processing: /libseccomp2_2.5.0-3_armhf.deb The command '/bin/sh -c dpkg -i /libseccomp2_2.5.0-3_armhf.deb' returned a non-zero code: 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890332] Re: apt update fails on docker arm container 20.04
I have also tried this on ubuntu:20.10, ubuntu:20.04 and ubuntu:18.04 and it produces the same error there, too. I think it is an issue with the system clock reporting Jan 1st 1970. The system clock on the host system is correct though. I could only find two ways to change the system clock in the ubuntu docker image: "date -s" requires --privileged (which isn't available in docker build) hwclock, which doesn't work on raspberry pi: root@8f7355a71bca:/# hwclock --verbose hwclock from util-linux 2.34 System Time: 0.-1 Trying to open: /dev/rtc0 Trying to open: /dev/rtc Trying to open: /dev/misc/rtc No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. other means like ntp don't work because they aren't preinstalled and cannot be installed because apt-get doesn't work (which is the topic of this bugreport) I was also not able to update libseccomp2, because wget and curl aren't preinstalled and cannot be installed either, because apt-get doesn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on docker arm container 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455323] Re: Regression in KDE5 desktop session save / restore
I just saw that crash again on Plasma 5 (Linux Mint 18.2, which is based on Kubuntu 16.04) ** Attachment added: "stacktrace.txt" https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1455323/+attachment/4952751/+files/stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455323 Title: Regression in KDE5 desktop session save / restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1455323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455323] Re: Regression in KDE5 desktop session save / restore
Sorry, wrong bug. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1455323 Title: Regression in KDE5 desktop session save / restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1455323/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 882942] Re: NaCL is missing
*** This bug is a duplicate of bug 1462647 *** https://bugs.launchpad.net/bugs/1462647 Don't bother with NaCL, it is deprecated and will be removed from chrome/chromium in Q1 2018. Use WASM (that is already supported by chromium-browser) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882942 Title: NaCL is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/882942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1474449] Re: Cannot compile simple hello world program
I get the same error with emscripten 1.22.1 (which is the newest version in the repos) With a self compiled emscripten 1.37.13, it works. Emscripten 1.22.1 is seriously outdated, it doesn't even support WebAssembly as target format. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1474449 Title: Cannot compile simple hello world program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emscripten/+bug/1474449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700022] [NEW] Emscripten does not support WebAssembly
Public bug reported: The emscripten package delivers emscripten version 1.22.1 from 2014, which did not have support for WebAssembly. Compiling a newer version manually isn't that hard (see https://askubuntu.com/questions/891630/how-to-install-the-latest- emscripten-on-ubuntu-using-command-line ), but since WebAssembly has been agreed upon by all major browser manufacturers and seems to be the upcoming web-technology, ubuntu should definitely offer support for developers. ** Affects: emscripten (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700022 Title: Emscripten does not support WebAssembly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emscripten/+bug/1700022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux
In Qt WebEngine, we have added "/usr/lib/adobe- flashplugin/libpepflashplayer.so" to the locations where it looks for the plugin, so it is now also found when one installs the package "adobe-flashplugin". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632870 Title: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pepperflashplugin-nonfree/+bug/1632870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux
ah, I didn't know that libpepflashplayer.so is included in adobe- flashplugin. symlinking it works indeed - even in WebEngine programs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632870 Title: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freshplayerplugin/+bug/1632870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux
Using Stéphanes analysis, I wrote this little script to install pepper flash manually: #!/bin/bash TARGET=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so wget http://redirector.gvt1.com/edgedl/release2/rpofl8ynzf9r05ca7iim67wdwf3t0zpuehwy3aswydc9g91q5c4iydolh9lt5toluyuq2phjg168mcvxxhntm3n79e4nw3mrx1j/23.0.0.185_linux_PepperFlashPlayer.crx -O PepperFlash.zip sudo mkdir -p "$(dirname $TARGET)" sudo unzip PepperFlash.zip libpepflashplayer.so -d "$(dirname $TARGET)" rm PepperFlash.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632870 Title: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freshplayerplugin/+bug/1632870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux
How can the priority still be "undecided" after a week, when the package is 100% dysfunctional? You might be fine with using adobe flash, but the users of ANY Qt WebEngine based program are not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632870 Title: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freshplayerplugin/+bug/1632870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316981] Re: package qtcreator needs to be dependent on qttools5-dev
When someone wants to use Qt Creator, it is extremely counterintuitive, that the package qtcreator is the wrong choice. I'd say the package qtcreator should be renamed to qtcreator-base (or something similar) and then there should be a new meta package qtcreator which is dependent on qtcreator-base and qttools5-dev (and maybe others). It should provide everything that is necessary for typical usage of Qt Creator. On Linux Mints package manager, qt-sdk is quite far down the list when searching for qt and not even on the list when searching for qtcreator or qt creator (as a side note, the search for qt creator doesn't even list the package qtcreator) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qtcreator in Ubuntu. https://bugs.launchpad.net/bugs/1316981 Title: package qtcreator needs to be dependent on qttools5-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1316981/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
