[Desktop-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)
Fine, thanks for that. As I use Neo 2 exclusively – no other keyboard layouts – there should be no further problems once the choice has been made. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1783987 Title: German Neo2 Problem with Xubuntu 18.04 (try out mode) Status in xkeyboard-config: Confirmed Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: When trying Xubuntu 18.04 Bionic Beaver from a USB Stick, I am offered the Neo2 Keyboard Layout, but it does not work. What I get is apparently Neo2 Mod4, but not Mod 1, as it should be. I wonder if Neo2 does work if I install 18.04 properly? To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1783987/+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 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)
Gunnar: Can you please make sure that NumLock is turned off when switching to Neo 2 and let us know if that helps. *** I tried that, and as you predicted, with NumLock turned off, the Neo 2 keyboard behaves normally. Does that mean I can go ahead and install 18.04, and everything will be fine? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1783987 Title: German Neo2 Problem with Xubuntu 18.04 (try out mode) Status in xkeyboard-config: Confirmed Status in xkeyboard-config package in Ubuntu: Incomplete Bug description: When trying Xubuntu 18.04 Bionic Beaver from a USB Stick, I am offered the Neo2 Keyboard Layout, but it does not work. What I get is apparently Neo2 Mod4, but not Mod 1, as it should be. I wonder if Neo2 does work if I install 18.04 properly? To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1783987/+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 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)
Thanks Gunnar :-) I don't think my report was invalid. I've been using Neo 2 for many years, so I know what it looks like when it works. So here's what happens in some more detail: 1. I insert a USB Stick with xubuntu-18.04-desktop-amd64.iso into my computer. 2. I start the computer and, by pressing F10, use the USB as my booting device (live system). 3. I select Language Deutsch. 4. I select »Ubuntu ausprobieren« (try Ubuntu). 5. In the keyboard menu, I change from »Deutsch qwertz« to »Deutsch Neo 2«. >From here, the keyboard should respond in the Neo manner, meaning that asdf >yields uiae, jklö yields nrtd, etc. At least that's what it does when using >16.04. 6. I start Mousepad to test the keyboard layout. So jklö should yield nrtd, but in actual fact what I get is ›456,‹. Which is Neo 2 to be sure, however it's not Mod1, but Mod4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1783987 Title: German Neo2 Problem with Xubuntu 18.04 (try out mode) Status in xkeyboard-config package in Ubuntu: Invalid Bug description: When trying Xubuntu 18.04 Bionic Beaver from a USB Stick, I am offered the Neo2 Keyboard Layout, but it does not work. What I get is apparently Neo2 Mod4, but not Mod 1, as it should be. I wonder if Neo2 does work if I install 18.04 properly? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1783987/+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 1783987] [NEW] German Neo2 Problem with Xubuntu 18.04 (try out mode)
Public bug reported: When trying Xubuntu 18.04 Bionic Beaver from a USB Stick, I am offered the Neo2 Keyboard Layout, but it does not work. What I get is apparently Neo2 Mod4, but not Mod 1, as it should be. I wonder if Neo2 does work if I install 18.04 properly? ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1783987 Title: German Neo2 Problem with Xubuntu 18.04 (try out mode) Status in xkeyboard-config package in Ubuntu: New Bug description: When trying Xubuntu 18.04 Bionic Beaver from a USB Stick, I am offered the Neo2 Keyboard Layout, but it does not work. What I get is apparently Neo2 Mod4, but not Mod 1, as it should be. I wonder if Neo2 does work if I install 18.04 properly? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1783987/+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 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
Thanks for the fix! Problem appears to have been solved (0.10.1). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Committed Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cron if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+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 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
If I use sudo apt update && sudo apt full-upgrade the bug recurs: krino@krino-desktop:~$ sudo apt update && sudo apt full-upgrade [sudo] Passwort für krino: OK:1 http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu xenial InRelease Holen:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] OK:3 http://archive.ubuntu.com/ubuntu xenial InRelease Holen:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Holen:5 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Holen:6 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [19,4 kB] Holen:7 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [366 kB] Holen:8 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [25,6 kB] Holen:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 DEP-11 Metadata [212 B] Holen:10 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [68,1 kB] Holen:11 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [39,7 kB] Holen:12 http://archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [362 kB] Holen:13 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 DEP-11 Metadata [121 kB] Holen:14 http://archive.ubuntu.com/ubuntu xenial-updates/universe DEP-11 64x64 Icons [145 kB] Holen:15 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 DEP-11 Metadata [2.516 B] Holen:16 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [431 kB] Holen:17 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [425 kB] Holen:18 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [293 kB] Holen:19 http://archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [184 kB] Holen:20 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 DEP-11 Metadata [212 B] Holen:21 http://archive.ubuntu.com/ubuntu xenial-backports/multiverse amd64 DEP-11 Metadata [212 B] Holen:22 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 DEP-11 Metadata [208 B] Es wurden 2.789 kB in 4 s geholt (603 kB/s). AppStream cache update completed, but some metadata was ignored due to errors. Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Alle Pakete sind aktuell. Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. krino@krino-desktop:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Committed Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cron if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some met
[Desktop-packages] [Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"
Bug still persists after update: 20161128 18:00 GMT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" Status in AppStream: Invalid Status in Ubuntu GNOME: Invalid Status in appstream package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Fix Released Status in fwupd package in Debian: Fix Released Bug description: [Impact] * Checks for apt updates using apt or apt-get also update the appstream cache. Some of the appstream metadata installed locally isn't strictly valid as it's missing two fields. [Test Case] * fwupdmgr refresh * apt update * check for errors about metadata being ignored [Regression Potential] * This is just changing the XML metadata locally, I don't see any regression potential. [Other Info] * This fix has been applied upstream: https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96 [Original report] I have found that when there are new packages available which my machine doesn't know about yet, if I run "sudo apt-get update" this is the output: Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB] Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 kB] Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [28 B] Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease [82.2 kB] Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 Packages [28 B] Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [28 B] Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [28 B] Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 Packages [28 B] Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [28 B] Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB] Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages [1,196 kB] Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB [426 kB] Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB] Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata [733 kB] Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 kB] Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [8,344 B] Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 Packages [8,684 B] Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en_GB [2,556 B] Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en [2,908 B] Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 Metadata [186 B] Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7,532 kB] Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages [7,512 kB] Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en_GB [3,040 kB] Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en [4,354 kB] Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 Metadata [3,410 kB] Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 Icons [7,448 kB] Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB] Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 Packages [140 kB] Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en_GB [88.1 kB] Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB] Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 Metadata [63.8 kB] Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 Icons [230 kB] Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [28 B] Get:35 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [28 B] Get:36 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [28 B] Get:37 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [28 B] Get:38 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted i386 Packages [28 B] Get:39 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted Translation-en [28 B] Get:40 http://gb.archive.ubuntu.co
[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
Bug still persists after update: 20161128 18:00 GMT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Bug description: [Impact] * The recent update of the Ubuntu asgen instance yielded it to generate modern metadata. While we could tell asgen to generate old- style metadata, fixing appstream is the better idea, since we already applied similar patches to appstream-glib (and having this package hold back updates is a bad idea). Currently, the unknown metadata is considered to be broken by appstream and it displays a warning about that issue during an `apt update` * The attached patch includes a second change to make AppStream more robust against broken YAML data, ensuring LP #1579712 can not be triggered on purpose or due to broken disks creating damaged YAML structure. [Test Case 1] * apt update * Check for errors about metadata being ignored [Test Case 2] * appstreamcli refresh --force * Check for errors about metadata being ignored * Check if we ignored data that should be present (search for it via `appstreamcli search `) * Run `appstreamcli status` and see if we still have information on the same amount of components as prior to the update. [Regression Potential] * Medium; The works case would be KDE Discover and GNOME Software loosing information on available software, but this risk is very low and the patch to fix this bug is very simple and has almost no regression potential. The YAML parser fix patch is a bit more complex, but should have no sideeffects. [Original report] Periodically I get emails from a machine with the subject: Cron if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi And a body of: AppStream cache update completed, but some metadata was ignored due to errors. I have a machine monitored by Munin. One of the plugins used on that machine is /etc/munin/plugins/apt which periodically counts the number of packets that can be upgraded. This is achieved by a crontab entry installed from the package which looks like this: # # cron-jobs for munin-node # MAILTO=root # If the APT plugin is enabled, update packages databases approx. once # an hour (12 invokations an hour, 1 in 12 chance that the update will # happen), but ensure that there will never be more than two hour (7200 # seconds) interval between updates.. */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi For many months everything has been running smoothly. On the 23rd November 2016 I started getting the "AppStream cache update completed, but some metadata was ignored due to errors." messages at a rate of about ten a day. I did a quick Google search which turned up a handful of bugs from earlier this year, such as Bug1575248. That is marked as Fixed Released though, so I am raising this new bug. If there are any further diagnostic details I can provide, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 09:57:18 2016 InstallationDate: Installed on 2013-05-08 (1295 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) JournalErrors: -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 GMT. -- Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en SourcePackage: appstream UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+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 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"
same here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1575248 Title: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update" Status in AppStream: Invalid Status in Ubuntu GNOME: Confirmed Status in appstream package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Fix Released Status in fwupd package in Debian: Fix Released Bug description: [Impact] * Checks for apt updates using apt or apt-get also update the appstream cache. Some of the appstream metadata installed locally isn't strictly valid as it's missing two fields. [Test Case] * fwupdmgr refresh * apt update * check for errors about metadata being ignored [Regression Potential] * This is just changing the XML metadata locally, I don't see any regression potential. [Other Info] * This fix has been applied upstream: https://github.com/hughsie/fwupd/commit/f4e0e88f7cba833a4badc1a3d62f1a08dd1bfd96 [Original report] I have found that when there are new packages available which my machine doesn't know about yet, if I run "sudo apt-get update" this is the output: Get:1 http://gb.archive.ubuntu.com/ubuntu xenial InRelease [247 kB] Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Get:3 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [82.2 kB] Get:4 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [28 B] Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease [82.2 kB] Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 Packages [28 B] Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [28 B] Get:8 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [28 B] Get:9 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 Packages [28 B] Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [28 B] Get:11 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB] Get:12 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages [1,196 kB] Get:13 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en_GB [426 kB] Get:14 http://gb.archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB] Get:15 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata [733 kB] Get:16 http://gb.archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 kB] Get:17 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [8,344 B] Get:18 http://gb.archive.ubuntu.com/ubuntu xenial/restricted i386 Packages [8,684 B] Get:19 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en_GB [2,556 B] Get:20 http://gb.archive.ubuntu.com/ubuntu xenial/restricted Translation-en [2,908 B] Get:21 http://gb.archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 Metadata [186 B] Get:22 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7,532 kB] Get:23 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages [7,512 kB] Get:24 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en_GB [3,040 kB] Get:25 http://gb.archive.ubuntu.com/ubuntu xenial/universe Translation-en [4,354 kB] Get:26 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 Metadata [3,410 kB] Get:27 http://gb.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 Icons [7,448 kB] Get:28 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB] Get:29 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse i386 Packages [140 kB] Get:30 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en_GB [88.1 kB] Get:31 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB] Get:32 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 Metadata [63.8 kB] Get:33 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 Icons [230 kB] Get:34 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [28 B] Get:35 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [28 B] Get:36 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [28 B] Get:37 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages [28 B] Get:38 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted i386 Packages [28 B] Get:39 http://gb.archive.ubuntu.com/ubuntu xenial-updates/restricted Translation-en [28 B] Get:40 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64
[Desktop-packages] [Bug 984785] Re: .goutputstream files polluting $HOME
Same with me: Affects Thunar (Final Release – Xubuntu 12.04 LTS Precise Pangolin). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME Status in “nautilus” package in Ubuntu: Confirmed Bug description: .goutputstream files polluting $HOME. I can't realize by which software or operation are created. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 Date: Wed Apr 18 13:29:31 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+564+189' org.gnome.nautilus.window-state maximized true org.gnome.nautilus.window-state sidebar-width 163 org.gnome.nautilus.window-state start-with-status-bar true InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/984785/+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
